CAPSTONE PROJECT  PART 2/3

Question No 1: Audits:
•	   An Audit is a report which evalutes software development process , to check the efficient flow of the project, regulations.I would provide the relavent information and documentation related to the project requirement, design, development, testing and deployment. Any potential risks.
              
Stage	Quarter 1 Audit Report(Requirement gathering phase)	
Completed	10 weeks 	
Checklist	Identify the stakeholders	
	BRD template	
	Elicitation Result report	
	Functional Features- Sign off	
	Mail Communication	
		
Stage	Quarter 1 Audit Report(Requirement Analysis phase)	
Completed	6 weeks	
Checklist	validate the requirements 	
	Client sign off documents 	
	UML Diagrams	
	RTM Document 	
	Mail Communication	
		
Stage	Quarter 2 Audit Report(Design phase)	
Completed	6 weeks	
Checklist	Tools utilization	
	Stakeholder Minutes of Meeting 	
	JAD sessions reports	
	Mail Communication	

Stage	Quarter 3 Audit Report(Development phase)	
Completed	25 weeks	
Checklist	JAD sessions reports	
	Preparation of end user manual document	
	BA and developer MOM	
	Mail Communication	

		
Stage	Quarter 4 Audit Report(testing phase)	
Completed	20 Weeks	
Checklist	Test Case Summary	
	BA and developer and Tester MOM	
	Change requests are Updated	
	Mail Communication	

Question no 2 : BA Approach Stratagy-
It s a outline of the activities,duration and resources required to conduct business analysis sucessfully. It  is a plan how they wil bridge the gap between the business needs and technical solutions.   
•	What Elicitation Techniques to apply-- Conduct the seessions with stakeholders to undertand the requirements(henry, pandu, Dooku, peter, Kevin, ben). Organize the fcous group discussion to understand the needs of farmers. Check on the existing system, conduct surveys, questionaries. Another approach will be brain storming sessions would be productive too. 
•	Stake holder analysis- conducting RACI matrix(Responsible,accountable, Consulted, Informed) to check the roles and responsbilities of stakeholders.keeping the updates of the progress of the project. Identfying the key stakeholders and requirements are priortized. 
•	Documents-  BRD document wil be prepared by the BA after interacting with the client . this document gives the details of the scope, objectives and what need to be delivered. Prepare the Timesheet, Ganntt Chart and the budget chart. Make Use case document to describe the flow and process of the project. Functional requirement Specifications(FRS), stakeholder requirement document(SRD), user stories are all part of the documents. 
•	Take Sign off- Obtaining the final verdit on the Requirement document, BRD document, Use case document from the client end by making them understand the objectives of the project.  Obtain the approval from client on the budget, timesheets to obtain the obejctives of the project life cycle. 
•	How to take a approval from client - A formal meeting from the client side to establish the approval on the project. Here all the detals will be wlkthrouhg to client and relavent stakeholders, detailed discussion on the scope and relavent draft a document to take a approval for the same.
•	Communication Channels- Different commnunication channels are available to communicate: Face to face communication, E-mail and Text messages, Virtual meeting or vedio conferance meets, through Teams,zoom calls. 
•	Handle Change Requests-  As a BA the change requests are part of a project, he has to perform the feasabilty study for accepting changes, documents the changes and discuss the same with the PM for approval. BA wil try to discuss with the client whether this change is minor or major based on that time comsumption will take place. BA has to dcoument in Change request log for all the proposed changes to a project requirement. 
•	 Progress of the project to the Stakeholders- BA generally updates the progress of the project by preparing progress reports, conducting meetings with stakeholders on the updates. Used visual ads- Dashboards, charts, graphs to present the data. 
•	Signoff on the UAT- User acceptance testing is the act of testing performed by the client to check and accept the software developed before it gets in to the production cycle. UAT is performed lastly once the test data, UAT cases, updating end user manual. Than BA takes a sign off from client on the client acceptance form. Once done than the software goes into the production stage. 

Question No 3 -  3-Tier Architecture - 
•	3 tier Architecture is software design pattern basicslly divided into 3 layers which is used in present day scenario
1. Application layer which is front end layer:
•	 This layer is front end layer for the customer user interface suc as apps, Web pages, desktop applications, 
•	It displays the login page for the user and sends the request for the business logic layer for process. 
2. Business logic  layer which is middel layer:
•	This layer deals the rules and regulations(logic) and function of the application.
•	It communicates with the data layer for the data base inputs like formulas and mathametical figures. 
3. Data Layer which is backend layer:
•	This layer has the data base and the data storage and retrival of the data. 
•	It consists of SQL, Oracle and other data base stored backend. 
•	It ensures the data security. 

___________Application Layer_______________
___________Business logic Layer_____________
_________________Data layer_______________________

Question 4 -  BA question to ask to the Stakeholder--
 5W-1H: 
•	It is considered as a BA tool for extracting consistant requirements as What, When, Who, Why, Where and How.
SMART: 
•	Specific: To set a goal which is specific
•	Measurable:  At each phase measure and move the process accordingly. 
•	Attainable: Concept where the goal can be attain or not
•	Relavent: similar to the business goals
•	Time bound: taking specific period for acheiving th goals.
RACI: Responsible, Accountable. Consulted and Informed. 
•	Responsible – BA is responsible for the project.
•	Accountable-- Mr. Vandanam is the project manager is accountable.
•	Consulted-- Ms. Juhi is Senior Java Developer, Mr Teyson, Ms Lucie, Mr Tucker, Mr Bravo are Java Developers. Network Admin is Mr Mike and DB Admin is John. Mr Jason and Ms Alekya as Tester. Kevin, Ben, Peter.
•	Informed- Mr. Henry, Mr. Pandu, Mr. Dooku, Kevin, Ben, Peter.
3 TIER ARCHITECTURE:
•	Understanding the architecture with the help of 3 layers, Application later, Business Logic layer, Data layer. Ex;
•	What is the information need on Application layer, which concept/ language is required to be on the logic layer to develp the software and from where the data being retrived and stored.
USE CASES:  This helps in developing the understanding the users who are involveds in the application usage. Static representation of the daigram to understand who are the actors and what r they performing. 
USE CASES SPECS: It describes the specifications about the flow of the use cases. 
•	Brief description, Actors involved, basic flow of events, alternate flow, post conditions, 
ACTIVITY DIAGRAMS: It is visual representation of diffrernt activities and processess wil flow in the application. It wil be system perspective. It derives the flow chart to reprent the flow of activity one after the other. It is a type of UML diagram.
MODELS: Data models and sequence diagrams wil be useful to understand the stakeholder in a better n good way. It is all used in front end layer. 
PAGE DESIGNS:  Mockups for the presenting the design on how it should look to the user, it also gives color schemes, layouts. 
  
Question 5 – Elicitation Techniques--  These are the techniques being used by the BA to gather the information particularly when the client or an individual is hestitating to provide the details directly. These helps to get the hidden or uncovered needs by engaging with the stakeholders. There are 11 Elicitation techniques which are useful for gathering the information as follows: 
•	Brainstorming: It is used to gather good amount of information and ideas on how to identify the problems and simplfy the issues. BA wil develop the a clear picture of Brainstorming and conduct the session for addressing the new ideas and evaluate and than wrap up the session. Distribute them amoung the stakeholders.
•	Document Analysis: Its a important gathering technique where evaluating the exisitng system and analysze the document. if the existing doucment is old or expired. Prearing the new one with AS-IS method.  
•	Reverse Engineering: There are two types of reverse engineering, White box and Black box. this techqniue is used when the system is legacy. When there is little documentation this technique is used. 
•	Focus Group: Engaging  a small group of stakeholders to discuss their needs and prespective on a particular topic or product. Open discussions happen and feeback is taken and implemented. Focus group is team of 10-12 members. 
•	Observation: Technique where there is watching and recording how users or stakeholders interact with the system.  Helps to indentify the how the work being done by methods of surveys or interviews. 
•	Workshop: It facilitate group of stakeholders, developers, and other departments to have sesssion and interact each other to acheive the goals. It consists of 6-8 users or stakeholders to identify the requirement. It s kind of structured way to capture the requirements. 
•	JAD: Joint Application Development is an extended version of Workshops, it focus on the collaboration between the Stakeholders and System analyst. It helps in gathering of large amount of information. Keeps on the high quality information on short time. Steps include Defining the session, Reaserch on the product, prepare the agenda and meeting, Conduct the sessions, Drafting the documents. 
•	Interview: Understanding the other person view on a particular point. An interview is a systamatic approach to get information  from a person. If there is large gathering it would be difficult to use this technique.
•	Prototyping: It is a type of technique which tests the functionality , gather the feedback and refine the design before it gets developed finally. Risk will be reduced here. It improves the communication between the stakeholders and developers which provide the clear vision.  This technique hence will be cost effective and management will be good. 
•	Questionaire: It is mostly used in Sofware development . It is a set of writtten questions that are distributed to the stakeholders and in written they provide the answers Its low cost method and can send to many users. 
•	Use case:  This decribes the interactions between the Actor and system to capture the functional requirements.

Question 6 – This project Elicitation Techniques -
•	Brain storming :  These sessions can be conducted with stakeholders and facilitate the ideas and requiremens which gives good solutions to the stakeholers.  Here i would with this technique with stakeholders: Henry, peter, kevin, and Ben to gather informatio about the project. Here discussion wil be on the challenges faced by farmers on how to provide the requirements for them to grow and maintain the crops. here brain storming can give us innovative and fresh ideas on how to go about the product. Everyone can participate and give there ideas and lastly can take feedback and prepare a document for the same. 
•	Prototyping: It is also a good Technique where the stakeholders can interact with the system and clarify the issues, here feedback is taken and again redefines the process. It gives clarity to the stakeholders. (Henry,Pandu, Dooku, Kevin, Ben, Peter).
•	Use cases: It shows the visual representation of functional flow of the user interacting with the system. it depicts the structural behaviour of the flow to understand for the stakeholders. 

As per my jurdgement , business requirements which include stakeholder requirements is: 
BR001- Farmer should be able to search for available products in fertilizers, seeds, pesticides.

Question 7 – 10 Business Requirements-
•	 BR001- Farmers shoud be able to login and search avaiable products by name and category and brand.
•	BR002- Manufactures should be able to upload and display their products in site
•	BR003- If the application is accessible in desktop and mobile with login (user ID and passwrod) for Farmers, Manufactures and vendors.
•	BR004- Application should be accessable to farmers to select and add to cart and order facility in smoother and user friendly. 
•	BR005-Application shoud fasilitate with payment gateway options to oder the product. Ex; CC details, Discounts, UPI options, no Cost EMI option.
•	BR006- Application should give feasility to check and check the order done by the farmer in real time.
•	BR007- Application shoud have update on the showing upgraded products and timely availabilty of stock from manufacture side.
•	BR008- Application should be able to handle large number of users and orders. 
•	BR009- Application should have database storage facility and security for the users Credentials. 
•	BR0010- Application should be able to give notitifications on the top like: Error in system, maintainance of application, update the Tracking column, Out of stock and avaiable stock details, data of the stocks before sales & after sales.

Question 8 –Assumptions--
•	Application is well basesd available to use on deskotp and laptop
•	Product catalog contains the products like fertilizers, seeds and pesticides.
•	The application should not store the financial details of the user , should be Auntentic and security based. 
•	The platform should send text message/ email regarding the order status and delivery tracker calls
•	Customer should be able to share the products to other customers through messages/links.
•	Cusotmer queries should be handled with proper platform and timely update with a separate page.
•	Once the customer purchase a product, feedback option to be provided and also customer can read other feedbacks/reviews of other products.

Question 9 – This project Requirements Priority table- 

S no 	Req name 	Requirement Description	Priority	
1	Farmers Search products	Farmers should be able to search for available products Catalog	3	
2	Manufacture Upload products	Manufacturers should be able to upload and display their products 	2	
3	Login functionality	Application should have user password authetication for farmers, manfcts, Vendors	1	
4	Add to cart 	Application should have proper access to select and add to cart features for farmers	3	
5	payment processing 	Application should have proper gateway to payment mode options	1	
6	availability of stocks	should show and update the availability of stocks to farmers 	2	
7	Order Confirmation	Customer or user should get the confirmation and track the product.	5	
8	Data secure storage	Application should have proper database and security of the customers credentials not to store	4	
9	Review and Feedback	Application should have review option to check the product and also feedback to give the purchased product	7	
10	Notifications	Products notification, system errors notify, and discounts notification and sharing products link to other customers	6	

Question 10 – Use Case Diagrams -- 
Use case Diagram is UML(unified modelling language)  is a high- level diagram which shows how the the user interacts with the system or application page.It shows the relationships between user and system functionality. 
Components:  There are 4 main components of the Use case diagram-
Actors: primary and secondry actors who interact with the system. actors are always outside the system boundary. 
Use cases : Essential use case and Supporting use cases. Define specific actions in sequence.
System Boundary: A rectangular box which encloses the use cases representing the system scope.
Relationships: These relates to the relation ship between the use cases and use cases and actors.  Include, Extend and Generalization. 
Associates: These are the lines connecting the actors indicating that actor is participating a use case. 

Question no-11 - Use case specifiations:

 Use case Specificiation for "LOGIN" in agriculture online store
Use Case Id	UC001		
Use Case Name	User Login		
Created By	Mr. Shivdeep	Last updated	
Created Data	17th Aug 2025	last Revised Date	
Actor	Farmer, Manufacturer 	 	
Description	This use case describes how the users can login		
Pre condition	The User should have internet Facility                                 		
	The user should have credentials to login the account		
Post Condition	The user successfully login and re directs to the application home page		
Normal Flow	The user goes to the login page of the online store		
	The page asks for username/password/phone no and password		
	The user login the page with Credentials		
	The system will verify the credentials and redirects to the home page		
Alternate Flow	If the Creds are incorrect than the system display invalid credentials		
	The system wil provideoption for “ forgot userid/ password”		
	The user asked for Re enter the credentials 		
Exception Flow	If the system is down , than the user will be notified and cannot login the page		
	If the user forgets the password		
Frequency of use	High		
Assumptions	The user has created the account		

Use case Specificiation for "SEARCH PRODUCT" in agriculture online store
Use Case Id	UC002		
Use Case Name	Search product		
Created By	Mr. Shivdeep	Last updated	
Created Data	17th Aug 2025	last Revised Date	
Actor	farmer	 	
Description	This use case describes on how farmer will search a product		
Pre condition	user  must be login		
	The manufacturer should upload the products		
Post Condition	The farmer is able to search the desired product		
Normal Flow	The farmer should login the site		
	the farmer will navigate through the products and specifications		
	The system should show the products specified like seeds . Pesticides 		
	The user should be able to check the price, Variety,brand, quantity.		
Alternate Flow	If the product is not available than system wil show Empty 		
	if the user is unable to find the keyword to product than can diferent way		
Exception Flow	If the system is slow or low network / system internet not working 		
Frequency of use	High		
Assumptions	the user should have knowledge to check products through filter		
	products should be listed to be navigated		

Use case Specificiation for "Add and Purchase Product" in agriculture online store
Use Case Id	UC003		
Use Case Name	Add and Purchase payment online		
Created By	Mr. Shivdeep	Last updated	
Created Data	17th Aug 2025	last Revised Date	
Actor	farmer	 	
Description	This use case describes how the users can browse and selecting  and online purchase 		
Pre condition	The user should login and browse products		
	The farmer should add the required product and make payment through gateway securely		
Post Condition	The user successfully order the product with online payment and system send confirmation		
Normal Flow	The farmer add the desired product		
	the system checks for the desired product availability		
	Farmer check the total cost and quantity and place a order with credentials		
	The system send confirmation and take the order placement with Succesfull payment message		
	The user will get a SMS to mobile about order and payment details		
Alternate Flow	If the product is out of stock, system prompts for alternate 		
	If user want to change payment mode , system wil redirect to previous page		
Exception Flow	If the system is down , than the user will be notified to retry		
	If the payment is interrupted due to balance or internet		
Frequency of use	High		
Assumptions	products are available		
	User should have payment gateway methods 		

Use case Specificiation for "Manufacture Upload Products" in agriculture online store
Use Case Id	UC004		
Use Case Name	Upload  Products details		
Created By	Mr. Shivdeep	Last updated	
Created Data	17th Aug 2025	last Revised Date	
Actor	Manufacturer	 	
Description	This use case describes how the Manufacturers upload the products and pricing		
Pre condition	The manufacturer should login and upload the products with name description and price		
	The farmer should add the required product and make payment through gateway securely		
Post Condition	The product details are visible to farmer on the online site		
Normal Flow	The manufacturer should login with credentials		
	The manufacturer navigates  to products section 		
	the system prompts for manufacture to upload the products with details		
	The system will confirm the details uploaded		
	Once uploaded, site will show the product in the list		
Alternate Flow	If the product details are invalid, system will notify the manufacture to rectify		
	If the manufacture want to change the product/ alter than system wil redirect previous page		
Exception Flow	If the system is down, manufacture cannot upload the products in quick pace		
Frequency of use	Medium		
Assumptions	Manufacture should have products to upload which are valid		
	Manufacture have variety		

Use case Specificiation for "Product delivery" in agriculture online store

Use Case Id	UC005		
Use Case Name	Product Delivery		
Created By	Mr. Shivdeep	Last updated	
Created Data	17th Aug 2025	last Revised Date	
Actor	Farmer, Manufacturer , vendor	 	
Description	This use case describes how the delivery of the product happens to the user location		
Pre condition	valid address provided by the User		
	Products are available with stocks in the site 		
Post Condition	Products are available and reaches user destination securely from Vendors with Delivered message to user		
Normal Flow	Once the user orders the product, an order Id is generated 		
	The system will send order id to vendor for placement of product		
	The vendor receives the order with address and product info		
	The warehouse will ship the order after packing 		
	The delivery partner will collect the product labeled and update the shipment details		
	The system will update the status and gives order tracking to the user 		
	The delivery guy will update the status once delivered to customer place and status is notified as delivered 		
Alternate Flow	If the product is delayed due to some reason		
	if the product should be delivered to different address by user himself		
Exception Flow	if the address is incorrect or user not available, system will notify for re schedule or cancel		
	If the user received the damage product , user can report the issue for exchange/cancel and system will initiate the process		
Frequency of use	High		
Assumptions	Customer provided correct communication address		
	Delivery partner send the product in time after the product is placed order		

Question no 12:  Activity Diagrams--
Activity diagram is visual representation tool used in Business Analysis re present the flow of activities within the system.  
•	It provides the dynamic view of flow of sequences in the system. 
•	It is a systems perspective flow of activities. 
•	Uses elements like Forks and Joints, Branch and merge, Swimlanes, control flow ,action state to show the different aspects of the flow of the works. 
•	Intial node and Final nodes are used to start the activity and end the activity.
•	Guard conditon is used to at decision nodes with [] to evaluate the condition of the flow.

Here are the below Activity diagrams for the above use case specifications mentioned. 

1. Acvitiy diagram: user login 

2. Acvitiy diagram: search product 

3. Acvitiy diagram:  Add product and Payment online

4. Acvitiy diagram:  Manufacturer Upload products

5. Acvitiy diagram: Product delivery-