Question 1 - – Functional Requirements

Answer -

Req ID	Req Name	Req description
FR001	Farmer Registration	Farmers should be able to register with the application.
FR002	Farmer Login	Farmers should be able to login using their credentials.
FR003	Manufacturer Registration	Manufacturers should be able to register to sell products.
FR004	Manufacturer Login	Manufacturers should be able to login using their credentials.
FR005	Product Catalog	System should display categorized products (fertilizers, seeds, pesticides).
FR006	Search Functionality	Users should be able to search for products using keywords and filters.
FR007	Add to Cart	Farmers should be able to add selected products to cart for purchase.
FR008	Place Orde	Farmers should be able to place orders for selected products.
FR009	Payment Gateway	Integration System should support UPI, Credit/Debit Card, and COD.
FR010	Email Confirmation	After successful order placement, farmers should get a confirmation email.
FR011	Delivery Tracking	Farmers should be able to track their orders through the system.
FR012	Upload Product Details	Manufacturers should be able to upload product images, prices, and descriptions.
FR013	View Product Details	Farmers should be able to view detailed product information.
FR014	Order History	Farmers should be able to view their past orders.
FR015	Logout Functionality	Users should be able to log out securely from the system.
FR016	Feedback and Rating	Farmers can leave ratings and feedback for the products they purchased.
NFR001	Page Loading Time	Each Page should load within 2 seconds
NFR002	WCAG 2.1 Compliance	Compliance The system must meet Web Content Accessibility Guidelines WCAG 2.1.
NFR003	Data Security	All user data must be encrypted and stored securely.
NFR004	Mobile Responsiveness	The system must work on mobile, tablet, and desktop screens.
NFR005	Uptime	The application must be available 99.5% of the time.

Question 2 - wireframe and prototypes -

Answer -

Question 3 - – Tools (Visio, Balsamiq)

Answer -1 - MS Visio - What it is: A diagram-making tool from Microsoft.

Used for: Creating professional diagrams like:

Use Case Diagrams

Flowcharts

ER Diagrams (Entity Relationship)

System Architecture

Why it’s useful: It helps visualize systems and processes clearly so that all team members understand the flow and structure.

2. Balsamiq - What it is: A wireframing tool used to create simple screen mockups (UI design).

Used for: Designing how a website or app screen will look before actual development.

Why it’s useful: Helps stakeholders and developers understand the layout and navigation of an app or website early in the project.

Question 4 - RTM

Answer -

Req ID	Req Name	Req Description	Design	D1	T1	T2	T3	T4	UAT
FR0001	Farmer Registration	Farmers should be able to register with the application	✅	✅	✅	✅
FR0002	Farmer Search for Products	Farmers should be able to search for products in fertilizers, seeds, pesticides	✅	✅	✅	✅	✅
NFR0101	Page Loading Time	Each page should load within 2 seconds	✅	✅	✅	✅	✅
NFR0102	WCAG 2.1 Compliance	The system must meet Web Content Accessibility Guidelines WCAG 2.1	✅	✅	✅	✅

Question 5 – 10 Test Case Documents-

Answer -

Test Case ID	Test Case Description	Pre-conditions	Test Steps	Expected Result	Actual Result	Status (Pass/Fail)
TC001	Farmer Registration with Valid Data	User is on Registration page	Enter valid name, email, mobile, password and click Register	Farmer is successfully registered and redirected to dashboard
TC002	Farmer Registration with Missing Fields	User is on Registration page	Leave Email field blank and click Register	Error message displayed: 'Email is required'
TC003	Product Search with Keyword	User is logged in	Enter 'pesticide' in search box and click Search	All pesticide-related products are displayed
TC004	Product Search with No Results	User is logged in	Enter 'XYZ123' in search and click Search	Message displayed: 'No products found'
TC005	Page Loading Time	System is running under standard network	Navigate to any product page	Page loads within 2 seconds
TC006	Accessibility Compliance (WCAG 2.1)	Accessibility tools available	Use screen reader on homepage	All key elements are readable and navigable
TC007	Login with Invalid Credentials	Login page is open	Enter wrong email/password and click Login	Message: 'Invalid username or password'
TC008	Add Product to Cart	User is logged in	Click on a product and click 'Add to Cart'	Product appears in the cart
TC009	View Cart and Place Order	Cart has at least 1 item	Go to Cart and click 'Place Order'	Order is placed and confirmation shown
TC010	Logout	User is logged in	Click on profile and click Logout	User is logged out and redirected to login page

Question 6 – DB Design

Answer -

Question 7 - Data Flow Diagram -

Answer - A Data Flow Diagram (DFD) is a graphical representation used to visualize how data flows through a system. It shows:

Where data comes from (external entities),

Where it goes (processes and data stores),

How it is transformed (through processes).

Question 8 – Change Request -

Answer - 1. Receive & Log the Change Request

•	The request is formally logged using a Change Request Form (CRF).

•	Details documented:

•	Nature of change (Government tax regulation update)

•	Impacted modules (Product pricing, Checkout, Invoice, Reports)

•	Requested by (e.g., Mr. Henry or Finance Head – Mr. Pandu)

2. Analyze the Change

•	Perform Impact Analysis:

•	Which business processes and system components are affected?

•	Is the change backward compatible?

•	Impact on pricing logic, cart totals, invoice generation, and GST

3. Discuss with Stakeholders

•	Schedule a change review meeting with:

•	Mr. Henry (Project Owner)

•	Mr. Pandu (Finance Head)

•	Development Team (Project Manager, Developers, Testers)

•	Evaluate:

•	Need vs. effort

•	Business justification

•	Risks and compliance issues

4. Update Requirements Documents

•	Modify the Business Requirement Document (BRD) and Functional Requirement Specification (FRS) to include:

•	New tax percentages

•	Tax calculation rules (e.g., CGST, SGST, IGST logic updates)

•	UI changes if applicable

5. Estimation & Approval

•	Development team provides:

•	Effort estimation (time, cost, and resources)

•	Timeline for deployment

•	Business owners (Mr. Henry or Committee) review and approve or reject based on cost-benefit analysis

6. Implementation & Testing

•	Once approved:

•	Developers implement the changes

•	QA team performs regression testing for:

•	Correct tax calculation

•	Impact on pricing and invoices

•	Display on frontend

•	Update test cases and test UAT scenarios

7. UAT & Deployment

•	Stakeholders perform User Acceptance Testing (UAT)

•	Upon successful testing, changes are:

•	Deployed to production

•	Communicated to all users.

8. Maintain a Change Log

•	Change is recorded in a Change Log Register with:

•	Change ID

•	Description

•	Status (e.g., “Completed – Deployed on June 15th, 2025”)

Question 9 – Change Request Vs an Enhancement

Answer - Ben and Kevin have approached with two new features:

1.	Allow Farmers to sell their crop yields through the platform (like a marketplace).

2.	Introduce an Auction system for crop yields so they can get the best price.

This is an Enhancement, not a simple change request.

Feature	Change Request	Enhancement
Definition	Modification to an existing functionality	Addition of new functionality/features
Purpose	To align system with new rules or corrections	To extend capabilities or improve user experience
Impact	Minor to moderate (affects current modules)	Major (impacts design, data model, user flow, architecture)
Example	Change in tax calculation method	Adding crop-selling and auction features

Question 10 – Estimations -

Answer - Project Inputs

Duration: 18 months

Working Days/Month: 20

Working Hours/Day: 8

Team Size (given):

BA: 1 (You)

Developers: 5

Tester: 2

PM: 1

DB Admin: 1

Network Admin: 1

Total: 11 members

Project Phases:

Requirements

Design

Development

Testing

Deployment

UAT

Total Working Hours per Person

18 months × 20 days/month × 8 hours/day = 2,880 hours per person

So, for 11 team members:

📌 2,880 hrs × 11 = 31,680 total manhours

Question 11 – UAT -

Answer - UAT Acceptance Process – Step-by-Step

1. Plan UAT - Create a UAT plan that includes timelines, environments, responsible stakeholders (Peter, Kevin, Ben, Mr. Henry), and scope of testing.

2. Prepare UAT Test Scenarios - Review all business requirements and prepare UAT scenarios and test cases aligned to them. These scenarios are written in business language and represent how end users will use the system.

3. Setup UAT Environment - Coordinate with the technical team to provide a stable UAT environment that mirrors production as closely as possible.

4. Conduct UAT Kick-off Meeting - Meet with the stakeholders (Mr. Henry, Peter, Kevin, Ben) to explain the scope of UAT, how to execute test cases, how to log issues, and the timeline.

5. Execute UAT - Stakeholders perform UAT by going through the real-life use cases. The BA monitors the progress, collects feedback, and records any bugs or change requests.

6. Log Issues and Fixes - Any issues reported during UAT are logged. Developers fix them and testers retest them. The BA validates the fixes with the users.

7. UAT Sign-off - Once all UAT test cases are passed and stakeholders are satisfied, a formal UAT sign-off document is collected from Mr. Henry and key stakeholders. This indicates the client approves the system for production deployment.

Question 12 – Project Closure Document -

Answer - A Project Closure Document is an official document prepared and submitted at the end of a project. It summarizes the overall project performance, confirms that all deliverables were completed, and serves as a formal record of project completion and sign-off by stakeholders. This document is essential for knowledge transfer, compliance, and lessons learned.

Key Components of a Project Closure Document

Section	Description
1. Project Overview	Summary of the project, objectives, duration, budget, and outcome
2. Deliverables Summary	List of all major deliverables completed and handed over
3. UAT & Client Acceptance	Confirmation that User Acceptance Testing was successful and accepted
4. Outstanding Issues	Any open items, unresolved bugs, or future enhancements noted
5. Lessons Learned	What went well, challenges faced, and how they were handled
6. Team Performance Summary	Summary of team efforts, recognition, and contributions
7. Final Budget Report	Actual budget vs planned budget comparison
8. Knowledge Transfer	Confirmation that handover and user training (if applicable) was done
9. Sign-Offs	Final sign-offs from stakeholders (Mr. Henry, SOONY Committee, PM, etc.)