Capstone Project1 – Part -2

Stage	Quarter 2 Audit report
(Requirement analysis 
Phase)	
Completed	4 weeks (Week 6 to Week 10)	
Checklist	UML designing	
	GAP Analysis	
	Risk Analysis	
	Gannt Charts	
	SDLC Preparation	
	Email Communication - Meetings	
Question 1 – Audits 
Stage	Quarter 1 Audit report
(Requirement gathering 
Phase)	
Completed	5 weeks (Week 1 to Week 5)	
Checklist	Preparation of BRD template 	
	Elicitation technique result 	
	Assigning roles	
	Document requirements	
	Prioritize requirements	
	Email Communication - Meetings	
Answers: 

Stage	Quarter 3 Audit report
(Design and Development)	
Completed	5 weeks (Week 11 to Week 15)	
Checklist	Utilisation of tools	
	End user manual preparation	
	JAD sessions	
	Stakeholders MOM	
	SDLC development and inception	
	Email Communication - Meetings	
Stage	Quarter 4 Audit report
(Testing)	
Completed	4 weeks (Week 16 to Week 19)	
Checklist	Test Cases preparation 
	
	Test phase development
	
	Test Execution	
	Test Closure	
	Email Communication - Meeting	

Question 2 – BA Approach Strategy
Answers:
•	What elicitation techniques to use : BA needs to decide what technique to use to gather requirements. Technique that can be used are Brainstroming, Document analysis, Reverse engineering, Focus groups, Observations , e.t.c
•	RACI matrix : Identifying who is responsible, accountable, consulted and informed. This is basically identifying stakeholders roles and responsibilities.
•	What Documents to prepare : BRDs, FRDs, 	Use case documents, Activity diagram and etc.
•	How to handle change request
•	How to take approvals from clients and sign off documents.

Question 3 – 3-Tier Architecture
Answers: 
1. Application Layer: This layer is considered as the topmost layer of the 3- Tier architecture. This basically includes and handles user interfaces including screen, pages, etc. In our project the major focus would be to make it user friendly and easy to understand.
2. Business Logic Layer: It is the middle layer of architecture it act as intermediary between presentation layer and logic of the application or 3rd party application. 
3. Database layer: This is the bottommost layer in the architecture it basically is responsible for storing data and stuff. Majorly the data are stored in cloud based structure and retrieved using SQL and other tools.

Question 4 – BA Approach Strategy for Framing Questions
Answers:  
1.	5W1H : This approach basically talks about what are the question we will be asking stakeholder this includes :
i)	who : will be the stakeholders
ii)	what : kind of requirements will be there 
iii)	when : will this project gets completed 
iv)	where : will it be delivered or executed 
v)	why : are we doing this project
vi)	how : we will address or solve current problems
2)	SMART:
a)	Specific: Are the requirement s specific to the project goals are aligned.
b)	Measurable: Within the specific timeline this project could be completed or not.
c)	Attainable: Is this project achievable within the timeline given to us.
d)	Relevant: Is this project relevant, specific and exact to the environment.
e)	Time-bound : Within the given timeframe can this project can be completed.

3)	RACI : 
a)	Responsible 
b)	Accountable 
c)	Consulted  
d)	Informed 
This helps to define roles and responsibilities within the team for each task.
4) UML (Unified Modelling Language) :
  It helps bridge communication between team and other members by creating diagrams and other software systems. It helps for specifying, visualising, constructing and documenting software systems.
This includes static and dynamic diagrams like: Use-case, Sequence, Activity diagrams.

Question 5 – Elicitation Techniques
Answer:
1) Brainstorming: This technique is used to find solution for a current problem. In this method SME (Subject Matter Expert) and Domain expert come together and give ideas to solve the problem. Group activity to generate a wide range of ideas and solutions quickly.
2) Document Analysis: This document that you read and understand the process of the project and the functionalities. Documents are Process Document, Functional document, Features document, Requirements document, Mail exchanges and Minutes of Meetings (MOM).
3) Reverse Engineering: The process in which we play or browse through a project and understand the project. This is mainly used in Migration project.
4) Focus Groups: Discussions with selected users/experts to gather varied input and expectations. These groups would be using project in future. They come and discuss, give their views about the project & suggest solution or new features.
5) Observation: Watching users perform tasks to understand actual workflows and challenges. There are two types of passive and active observation.
6) Workshops: Interactive meetings to explore, prioritize, and validate requirements collectively. Each department come together to give their inputs, prototypes, ideas and process flow.
7) JAD (Joint Application Development) : In this technique in which we take technical experts to discuss requirements with the clients/stakeholders. This is held according to project type from Network project, DB project e.t.c.
8) Interview: One-on-one or small group discussions to extract detailed stakeholder needs. There are two approaches Structured and Unstructured approach.
9) Prototyping: Building sample models or mock-ups to help visualize and refine requirements. It includes creating of working models like Activity diagrams,flow charts etc.
10) Questionnaires/Survey forms: Surveys with structured questions to collect data from many stakeholders. It can be in form of rating, predefined values. It is analysed through statistical methods like Mean, Mode, Median,Skewness, etc.
11) Use Case Analysis: In-depth breakdown of how users perform tasks to identify improvement opportunities.
Question 6 – This project Elicitation Techniques
Answers: 
Recommended Techniques
a)	Brainstorming: Useful with Peter, Kevin, Ben to collect more ideas. Justification: The project involves remote farmers who may not express detailed requirements upfront; visual and collaborative techniques help bridge gaps.
b)	Prototyping: Helps stakeholders visualize the product interface.
c)	Use Case Specs: Captures functional behavior.
d)	Document Analysis: Review existing systems/process

Question 7 – 10 Business Requirements
Answer: 
BR001- Users should be able to search for seeds, fertilizers and pesticides through online websites or web applications.
BR002- Users should be able search from product catalog.
BR003- Users should be able to crate login and signup. 
BR004 – Users can create new login through both email and phone number and existing users can login through existing credentials.
BR005- Users can check the availability of products and get to know the estimated time of arrival.
BR006- Users can add desired products and select/add the quantity of items they require.
BR007- Users can add their address and select preferred delivery address
BR008- Users can select preferable payment methods i.e Cards, UPI, Cash on delivery options.
BR009- Users can complete their order after payment and Order successful message and email should be delivered.
BR010- Users can see the order number and can track the order.
Question 8 –Assumptions	
Answer: 
1.	All users have basic internet access.
2.	Farmers understand basic mobile usage.
3.	Products will be shipped via third-party logistics.
4.	Manufacturers have digital product catalogues ready.
5.	All stakeholders are available for feedback within deadlines.

Question 9 – This project Requirements Priority
Answer:
Req ID	Requirement Name	Description	Priority	
BR001	Search engine website and web applications	Search products in catalog	8	
BR002	Product catalogs	Upload/display products	8	
BR003	Login page creation	Login and signup page	10	
BR004	Safe and secure login through credentials	Login through emails and phone number	7	
BR005	Stock availability and ETA	Users can check availability and Estimated time of arrival.	9	
BR006	Shopping cart creation	Users can add products/items to their carts.	6	
BR007	Delivery Address 	Add and select delivery address	9	
BR008	Payment Gateway	Multiple paymets options	5	
BR009	Order successful email	Order confirmation will be sent to registered email and phone number	8	
BR010	Order tracking	Users will get tracking ID and can check order status	6	

Question 10 – Use Case Diagram 
Answer: 

Question 11 –Use Case Specs
Answer:
1) Use case Name: Login page 
Actors: Farmer, Manufacturer
Use Case ID: UC 0001
Use case Name: Create Login page for website
Pre- conditions: Login page should be created with login credentials
Post- conditions : Successful login with registered credentials

Question 12 – Activity Diagram
Answer :

  Link to access :
https://app.diagrams.net/#G1lZnro9jGjShIyEW8BcQ8ED_YrNQxJ8Ku#%7B%22pageId%22%3A%22nDgE6KIMSilgwDPeGffQ%22%7D