Capstone Project -1 Part – 3/3

Online Agriculture Product Store

by Tarun Kumar Deshmukh

Question -1 Identify minimum 20 functional requirements?

Answer – Functional Requirements - Functional Requirements refer to the specific
behaviours, features, and functions that a system, product, or solution must perform
in order to meet the needs of stakeholders. These requirements describe how the
system should behave and what it should do in terms of its operations, processes,
and interactions. They provide detailed guidance for developers, designers, and
testers to build and evaluate the system.
Non-Functional Requirements - Non-Functional Requirements (NFRs) define the
quality attributes, performance standards, and constraints that a system or solution
must meet. Unlike Functional Requirements which specify what the system should
do, non-functional requirements describe how the system should perform under
certain conditions. It ensures that the system operates efficiently, securely, and
reliably, and that it meets various stakeholder expectations related to user
experience and operational needs.
List of Functional Requirements are below:

Req ID Req Name Req Description Priority

Farmer Farmers should be able to 9
FR0001 Registration register with the application
Farmer search for Farmers should be able to 8
products search for available products
FR0002 in fertilizers, seeds, pesticides
Manufacturer’s Manufacturers should be able 8
FR0003 Registration to register with the application
Manufacture Manufacturers should be able 7
product listing to list their products in the
FR0004 catalogue
Product Details Display The application 9
should display detailed
information about each
product, including
descriptions, specifications,
FR0005 and pricing
Add to Cart Users should be able to add 8
products to their shopping
FR0006 cart for purchase
FR0007 Cart Management Users should be able to view 8
and manage the contents of
their shopping cart, including
 adding or removing products
Wishlist Users should be able to 7
manage their wishlist or buy-
Management later list, including adding or
FR0008 removing products
Multiple Payment The platform should integrate 9
Gateways with multiple payment
gateways to facilitate secure
FR0009 and convenient transactions
Order Placement Users should be able to place 9
orders for selected products,
specifying quantity and
FR0010 delivery address
Order Users should receive an 9
Confirmation order confirmation with details
such as order number,
products, quantities, total
amount, and estimated
FR0011 delivery date
Order Tracking Users should be able to track 9
the status and location of
FR0012 their orders in real-time
Order History Users should be able to view 7
their order history, including
past orders, order details, and
FR0013 statuses
Customer Support Users should have access to 8
customer support, either
through live chat, email, or
phone, for assistance with
FR0014 their orders or inquiries
User Ratings and Users should be able to 7
Reviews provide ratings and reviews
for products they have
FR0015 purchased
Product The platform should provide 8
Recommendation personalized product
s recommendations based on
user preferences and
FR0016 browsing history
Social Sharing Users should have the option 7
to share products or their
purchase experience on
FR0017 social media platforms
Secure The platform should ensure 9
Transactions secure transactions by
implementing appropriate
encryption and security
FR0018 measures
FR0019 Product Filtering Users should be able to filter 8
 products based on various
criteria such as price range,
brand, or product type
Account Users should be able to 7
manage their account
Management settings, including profile
information, password
changes, and email
FR0020 preferences

List of Non - Functional Requirements are below:

Req ID Req Name Req Description Priority

NFR001 Usability The application should have 9
intuitive and user friendly
NFR002 Performance The application must load 8
pages in 3 seconds
NFR003 Security The application must ensure 8
secure user authentication
NFR004 Compatibility The application should be 8
compatible with major web
browser
NFR005 Response Time The application should 9
respond to user input withing 2
seconds
NFR006 Representation Visual representation of the 7
pages must be detailed
NFR007 Auto readable OTPs must be auto readable 7
by the application
NFR008 Session time out Session time out must be up to 6
2 mins
NFR009 Accuracy Location must be accurate up 8
to 50 meters
NFR010 Refresh Pages must be refreshed after 6
every 30 seconds.

Question- 2 Make wireframes and prototypes.

Answer – Wireframes - Wireframes are visual representations or blueprints of a user
interface (UI) that outline the structure and layout of a web page, application, or
system without focusing on detailed design elements like colours, fonts, or graphics.
Wireframes are typically used to represent the basic framework of a product’s
interface, showing how different elements will be arranged and how users will
interact with the system.
Prototypes - Prototypes are early, simplified models or representations of a system
or product that simulate the functionality, user interface (UI), or processes of the final
solution. Prototypes allow stakeholders, including business users, clients, and the
development team, to explore and evaluate the proposed system’s features before
the final product is developed. They help gather feedback, validate requirements,
and refine system design by providing a tangible representation of the software or
product early in the project lifecycle.
Some examples are:
Application dashboard –

Category page –
Login page –
Registration page –
Payment page –
Question- 3 Make a note of the Tools, which you are using for above concepts
(Visio, Balsamic)?
Answer – Business Analysis Tools – Business Analysis tools are the techniques to
prepare a raw design, process flow diagram and prototype of an end product which
will be covering all the aspects of the project requirements and represents the
activity of how the process flows inside the project. In Business Analysis there are
tools like MS Visio, Balsamic, Axure RP which helps a Business Analyst to prepare
Use case diagram, Activity Diagram, Wireframes and Prototype.
MS Visio - In Business Analysis, Microsoft Visio is a powerful tool used to visually
represent and communicate complex business processes, systems, workflows, and
organizational structures. It plays a crucial role in helping business analysts’ model
and analyse various aspects of business operations, enabling stakeholders to better
understand, evaluate, and optimize processes. We can prepare flowcharts, org
charts, building plans, floor plans, data flow diagrams, process flow diagrams,
business process modelling, swim lane diagrams, 3D maps etc.
Balsamiq - Balsamiq is a rapid wireframing tool. It creates mock-ups and wireframes
for websites, web apps, and desktop software. It allows us to picture ideas and
concepts through a simple drag-and- drop interface. The wireframes created using
Balsamiq have a hand-drawn style. It's designed to help business analysts,
designers, product managers, and developers quickly sketch out the basic structure
and layout of a user interface without focusing on visual design details.
Axure RP – Axure RP stands for Axure Rapid Prototyping which is a prototyping and
wireframing tool used by business analysts, UX/UI designers, product managers,
and developers to create interactive, high-fidelity prototypes and wireframes for
websites, applications, and digital products. Unlike low-fidelity tools like Balsamiq,
Axure RP allows users to build more detailed and interactive prototypes that closely
mimic the final user experience (UX) and behaviour of a product.
Question – 4 Prepare Requirement Traceability Matrix?
Answer – Requirement Traceability Matrix (RTM) - A Requirement Traceability
Matrix (RTM) is a document used in business analysis, project management, and
software development to ensure that all project requirements are being met
throughout the project lifecycle. It helps track the relationship between requirements
and various project elements, ensuring that each requirement is linked to
corresponding deliverables, test cases, and design specifications.
RTM is prepared for the Online Agriculture Project is below:
Note- 1. Completed status is represented by “Comp.”
2. Work in Progress status is represented by “WIP”
Req Req Desi- D1 T1 D2 T2 D3 T3 D4 T4 UAT
Req Name Descripti- gn
ID on
Farmer Farmers Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
Registra should be
tion able to
register
FR000 with the
1 application
Farmer Farmers Comp. Comp. Comp. WIP Comp. Comp. Comp. Comp. Comp. WIP.
search should be
for able to
products search for
available
products
in
fertilizers,
FR000 seeds,
2 pesticides
Manufac Manufactu Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
turer’s rers
Registra should be
tion able to
register
FR000 with the
3 application
Manufac Manufactu Comp. WIP. Comp. Comp. Comp. Comp. Comp. Comp. Comp. WIP.
ture rers
product should be
listing able to list
their produ
FR000 cts in the
4 catalogue
FR000 Product Display Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
5 Details The
application
should
display
detailed
informatio
n about
each
 product,
including
description
s,
specificati
ons, and
pricing
Add to Users Comp. Comp. Comp. Comp. WIP. Comp. Comp. Comp. Comp. WIP.
Cart should be
able to
add
products
to their
shopping
FR000 cart for
6 purchase
Cart Users Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
Manage should be
ment able to
view and
manage
the
contents
of their
shopping
cart,
including
adding or
FR000 removing
7 products
Wishlist Users Comp. Comp. Comp. WIP. Comp. Comp. Comp. Comp. Comp. WIP.
should be
Manage able to
ment manage
their
wishlist or
buy-later
list,
including
adding or
FR000 removing
8 products
Multiple The Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
Payment platform
Gateway should
s integrate
with
multiple
payment
gateways
to facilitate
secure
and
convenient
FR000 transactio
9 ns
Order Users Comp. Comp. Comp. Comp. Comp. WIP. Comp. Comp. Comp. WIP.
Placeme should be
nt able to
place
orders for
selected
products,
specifying
quantity
and
FR001 delivery
0 address
FR001 Order Users Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
1 Confirm should
ation receive an
order
confirmati
on with
details
 such as
order
number,
products,
quantities,
total
amount,
and
estimated
delivery
date
Order Users Comp. WIP. Comp. Comp. Comp. Comp. Comp. Comp. Comp. WIP.
Tracking should be
able to
track the
status and
location of
their
FR001 orders in
2 real-time
Order Users Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
History should be
able to
view their
order
history,
including
past
orders,
order
details,
FR001 and
3 statuses
Custom Users Comp. Comp. Comp. Comp. WIP. Comp. Comp. Comp. Comp. WIP.
er should
Support have
access to
customer
support,
either
through
live chat,
email, or
phone, for
assistance
with their
FR001 orders or
4 inquiries
User Users Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
Ratings should be
and able to
Reviews provide
ratings
and
reviews for
products
FR001 they have
5 purchased
Product The Comp. WIP. Comp. Comp. Comp. Comp. Comp. Comp. Comp. WIP.
Recom platform
mendati should
ons provide
personaliz
ed product
recommen
dations
based on
user
preference
s and
FR001 browsing
6 history
FR001 Social Users Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
7 Sharing should
have the
 option to
share
products
or their
purchase
experienc
e on social
media
platforms
Secure The Comp. Comp. Comp. Comp. Comp. Comp. WIP. Comp. Comp. WIP.
Transact platform
ions should
ensure
secure
transactio
ns by
implementi
ng
appropriat
e
encryption
and
FR001 security
8 measures
Product Users Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp. Comp.
Filtering should be
able to
filter
products
based on
various
criteria
such as
price
range,
brand, or
FR001 product
9 type
Account Users Comp. Comp. Comp. Comp. WIP. Comp. Comp. Comp. Comp. WIP.
should be
Manage able to
ment manage
their
account
settings,
including
profile
informatio
n,
password
changes,
and email
FR002 preference
0 s

Approach to tackle query of Mr. Henry and Peter- When Mr. Henry and Peter
approaches to me regarding the status of project then I will explain them the status
with the help of Requirement Traceability Matrix which is prepared by each
requirement and the development stages of the requirements are logged inside the
matrix which will give overall picture of the project, how many requirements are
completed, how many are in ‘in progress’ stage and how much more time it will take
to complete all the cycle. Using this information, I can prepare a summary report to
present in front of Mr. Henry and Peter covey them about development status,
testing status, completion dates, critical areas, risk and dependencies.
Question – 5 Prepare 10 Test Case Documents
Answer – Test Case Documents - Test Case Documents are structured documents
used in software testing to define and outline the specific conditions, steps, and
expected results for verifying a particular feature or functionality of a software
application. They are essential for ensuring that software meets its requirements and
behaves as expected in different scenarios.
10 different Test Case Scenarios and their respective documents are below:

Test case TC0001 Test Case User Registration

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Mr. Jason
ID
Test XXXX Date of Test 10-OCT-2024
Schedule
ID
Scenario To register new user inside web application using e mail id
and creating password
Link to that www.onlineagristore.com
page
Pre Internet connectivity should be stronger enough, Website
Conditions URL is working
Post Registration successful, User able to login into system with
Condition username and password
Input Data Email Id, Mobile Number, Name of the user
Expected Once user register using name, mail id / mobile number
Behaviour and create password, System should show user created
successfully.
Actual After entering mandatory fields, if user clicks on Register
Behaviour button, then system shows pop up saying ‘User created
successfully’
Comments NA
Results Pass
(Pass/Fail)

Test case TC0002 Test Case User Login

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
 Test Plan TOAS01 Tester Name Miss Alekya
ID
Test XXXX Date of Test 12-OCT-2024
Schedule
ID
Scenario To login registered user using username and password
Link to that www.onlineagristore.com
page
Pre User is already registered
Conditions
Post Login successful, User is able to search for the required
Condition products
Input Data Username, Password, Captcha
Expected User enter Username and Password along with captcha to
Behaviour login and system shows login successfully
Actual After entering username, password and captcha, if user
Behaviour clicks on ‘Login’ button, then system shows pop up saying
‘Login successfully’
Comments NA
Results Pass
(Pass/Fail)

Test case TC0003 Test Case Add to cart

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Mr. Jason
ID
Test XXXX Date of Test 15-OCT-2024
Schedule
ID
Scenario User should be able to add selected products to cart
Link to that www.onlineagristore.com
page
Pre Products are available in inventory and add to cart is
Conditions enabled
Post Total prices will be shown, Payment option would be shown
Condition
Input Data Product Id, Product pictures, Product prices
Expected Once login, User will search products on the basis of
Behaviour requirements, and he must be able to add products in the
 cart for purchase.
Actual After selecting required products, User clicks on Add to Cart
Behaviour option to add products in the cart for purchase
Comments NA
Results Pass
(Pass/Fail)

Test case TC0004 Test Case Coupon code apply

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Miss Alekya
ID
Test XXXX Date of Test 17-OCT-2024
Schedule
ID
Scenario User should be able to add coupon code at the checkout
time to avail discount
Link to that www.onlineagristore.com
page
Pre Coupon code must be valid
Conditions
Post Total price will be adjusted as per coupon code
Condition
Input Data Coupon codes, Discount codes
Expected At the time of checkout, User must be able to enter coupon
Behaviour code to get the discount on total bill
Actual After adding to cart, User puts coupon code and gets
Behaviour discount on total prices of the product
Comments NA
Results Pass
(Pass/Fail)

Test case TC0005 Test Case Payment

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Mr. Jason
ID
Test XXXX Date of Test 19-OCT-2024
Schedule
 ID
Scenario User must be able to choose payments option and do the
payment
Link to that www.onlineagristore.com
page
Pre Products added to cart and Total price is calculated
Conditions
Post Redirected to 3rd party apps or COD option
Condition
Input Data Card details, UPI details, Payment method
Expected User should be able to choose payment option from Net
Behaviour Banking, UPI or Cash on Delivery
Actual At the payments stage user is able to select options from
Behaviour Net Banking, Card payments, UPI or cash od delivery
Comments NA
Results Pass
(Pass/Fail)

Test case TC0006 Test Case Payment confirmation

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Miss Alekya
ID
Test XXXX Date of Test 21-OCT-2024
Schedule
ID
Scenario User should be get payment confirmation message in
phone or mail
Link to that www.onlineagristore.com
page
Pre Payments is successful
Conditions
Post Redirected to order confirmation page and expected
Condition delivery date
Input Data Payment Id, Total price
Expected Once payments are done and amount deducted from the
Behaviour user’s account, user should get text or mail confirmation for
payment
Actual After payment, User gets payments successful confirmation
Behaviour message or mail that payment has been successfully
processed
Comments NA
 Results Pass
(Pass/Fail)

Test case TC0007 Test Case Order Confirmation

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Mr. Jason
ID
Test XXXX Date of Test 24-OCT-2024
Schedule
ID
Scenario User should get text or mail for order confirmation
Link to that www.onlineagristore.com
page
Pre Payment is successful
Conditions
Post Tracking of order is enabled
Condition
Input Data Product Id, Product pictures, Product prices
Expected Once payments are done, User should get order
Behaviour confirmation containing Order Id, and expected delivery
date
Actual After payments done, User should get order confirmation
Behaviour containing Order Id and expected delivery date
Comments NA
Results Pass
(Pass/Fail)

Test case TC0008 Test Case Cancel order

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Miss Alekya
ID
Test XXXX Date of Test 27-OCT-2024
Schedule
ID
Scenario User should be able to cancel wrong order
Link to that www.onlineagristore.com
page
 Pre Product already ordered, Cancel window is open
Conditions
Post Order status is updated, Refund initiated
Condition
Input Data User account details, Order Id, Product Id
Expected User should be able to cancel the order or orders done by
Behaviour mistake from cancel order page
Actual User is able to cancel the order from cancel order page
Behaviour from the menu
Comments NA
Results Pass
(Pass/Fail)

Test case TC0009 Test Case Return of the order

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Mr. Jason
ID
Test XXXX Date of Test 31-OCT-2024
Schedule
ID
Scenario User should be able to return any order which they did not
like
Link to that www.onlineagristore.com
page
Pre Product already ordered, Return window is open
Conditions
Post Order status is updated, Refund initiated
Condition
Input Data Product Id, Order id, User details
Expected User must be able to return the order from Return order
Behaviour page
Actual User can return the order from the Return order page with
Behaviour the help of order id and product id
Comments NA
Results Pass
(Pass/Fail)

Test case TC0010 Test Case Session Out timing

ID Name
Project ID Agri0213 Project Name Online Agriculture Store
Project
PM ID 98562 PM Name Mr. Vandanam
 Test OAS001 Tester ID 67542
Strategy ID
Test Plan TOAS01 Tester Name Miss Alekya
ID
Test XXXX Date of Test 03-NOV-2024
Schedule
ID
Scenario Application must be automatically session out after staying
idle
Link to that www.onlineagristore.com
page
Pre User is logged in and inactive
Conditions
Post System should ask for re-login
Condition
Input Data Product Id, Order id, User details
Expected Application must be session out after being idle for 30
Behaviour seconds and should ask for login again
Actual Application gets session out after being idle for 30 seconds
Behaviour and asks for login again
Comments NA
Results Pass
(Pass/Fail)

Question – 6 Draw database schema and ER diagram.

Answer – DB Schema – DB Schema is a blueprint that outlines the structure of the
database, including its tables, fields, relationships, constraints and other
characteristics.
Entity Relationship Diagram – An Entity Relationship Diagram is a visual
representation of the relationships between entities in a database. It depicts the
entities (tables), attributes (properties/fields) and relationship between them.
Question- 7 What is a data flow diagram? Draw a data flow diagram to represent the
in-flow and out-flow of data when a Farmer is placing an order for the product
Answer – Data Flow Diagram - A Data Flow Diagram (DFD) is a graphical
representation of the flow of data within a system. It shows how data moves from
one part of the system to another and how data is transformed, stored, and utilized
within the system. DFDs are widely used in systems analysis and design to visualize
data processes and the way information is handled, stored, and transmitted between
different system components.
Question- 8 Due to change in the Government Taxation structure. we should change
the Tax structure. How do you handle change requests in a project?
Answer- Handling change requests in a project involves a systematic process to
ensure that changes are effectively managed while minimizing disruption to the
project's scope, timeline, and resources. Here are the steps typically followed to
handle change requests.
1. Change Request Identification: Identify and document the change request,
including the specific details of the requested change, the reason for the change,
and its potential impact on the project.
2. Change Impact Analysis: Assess the impact of the change on various aspects
of the project, such as scope, timeline, cost, resources, and risks. Evaluate the
feasibility and implications of implementing the change.
3. Change Evaluation: Review the change request with key stakeholders, including
project sponsors, clients, and relevant team members. Discuss the potential benefits,
risks, and trade-offs associated with the change. Consider the project’s objectives,
constraints, and priorities in the evaluation process.
4. Change Prioritization: Prioritize the change request based on its urgency, impact,
and alignment with project goals. Determine whether the change is critical and must
be implemented immediately or can be scheduled for a future phase or release.
5. Change Approval: Obtain formal approval from the appropriate stakeholders, such
as project sponsors or change control boards. Ensure that all stakeholders agree
regarding the change and its implications.
6. Change Implementation: Incorporate the approved change into the project plan,
including any necessary adjustments to the scope, schedule, budget, or resources.
Communicate the change to the project team and other relevant stakeholders.
Update project documentation, such as requirements, design, and test plans, to
reflect the approved change.
7. Change Communication: Communicate the approved change to all relevant
parties, including team members, clients, and other stakeholders. Clearly explain the
reasons for the change, its impact on the project, and any adjustments to
expectations or deliverables.
8. Change Tracking and Documentation: Track and document all approved changes,
including the rationale, approvals, and implemented modifications. Maintain a
change log or change register to ensure transparency and accountability throughout
the project.
9. Change Control and Monitoring: Continuously monitor the impact of implemented
changes on the project's progress, risks, and quality. Maintain open lines
of communication with stakeholders to address any concerns or issues related to the
approved changes. Monitor the project's overall alignment with the revised scope,
timeline, and objectives.
By following these steps, a project can effectively manage change requests,
ensuring that changes are evaluated, approved, and implemented in a controlled
manner, while minimizing disruptions and maintaining project success
Question – 9 As the project is in process, Ben and Kevin have contacted you. The
reason is to inform you that they want the Farmers to sell their crop yields through
this application i.e. Farmers should be able to add their crop yields or products and
display to general public and should be able to sell them. They also want to
introduce an Auction system for their Crop yields.
As a BA, what will be your response? Is this a change request or an enhancement?
Answer – Change Requests - A Change Request (CR) is a formal proposal to
modify a project, product, process, or system. It is typically used in project
management, software development, and various industries to handle modifications
and improvements. A Change Request can arise at any point during a project's
lifecycle, whether it's due to new requirements, unforeseen issues, or the need for
enhancements.
Enhancement - Enhancements refer to improvements or additions made to the
software after its initial release. These changes are aimed at increasing the
software’s value, performance, or functionality based on evolving business needs,
user feedback, or technological advances. Enhancements can be part of the regular
software maintenance cycle or occur as part of a new version or update.
As a Business Analyst, my response to Ben and Kevin's request would be to classify
it as an enhancement rather than a change request. A change request typically
involves modifications to existing functionality or requirements, while an
enhancement introduces new features or capabilities that were not initially specified.
In this case, the request to allow farmers to add their crop yields, display them to the
general public, and enable selling through the application represents an
enhancement because it introduces new functionality that goes beyond the initial
scope of the project. Additionally, the introduction of an auction system for crop
yields adds another layer of functionality to the application.
To address this enhancement request, I would follow the standard process for
handling new requirements:
1. Requirement Gathering: I will meet with Ben and Kevin to gather detailed
requirements for the new functionality. This would involve understanding the specific
features they envision, such as the process for farmers to add and manage their
crop yields, the display of products to the public, and the implementation of the
auction system.
2. Impact Analysis: I would analyze the impact of these enhancements on the
existing project scope, timeline, budget, and resources. This assessment would help
determine the feasibility and potential implications of incorporating the requested
features.
3. Stakeholder Analysis: I would identify and involve relevant stakeholders, such as
the project sponsor, development team, and other key personnel, to assess their
perspectives and gather their inputs on the potential enhancements.
4. Documentation and Communication: I would document the detailed requirements
and changes in the project scope, and communicate them to the project team,
stakeholders, and any other parties involved. This would ensure everyone is aware
of the proposed enhancements and their implications.
5. Evaluation and Prioritization: I would work with the project team and stakeholders
to evaluate the value and priority of the requested enhancements. This evaluation
would consider factors such as the potential benefits, impact on project goals,
alignment with business objectives, and available resources.
6. Planning and Execution: If the enhancements are deemed feasible and approved,
I would update the project plan, schedule, and resources accordingly would
collaborate with the development team and other stakeholders to incorporate the
new features into the application, ensuring proper testing and quality assurance.
By treating this request as an enhancement, the project can effectively manage the
additional requirements and deliver the desired functionality while considering the
impact on the ongoing project.
Question – 10 Come up with estimations – How many Manhours required?
Answer – Estimation - Estimation in Software Development Life Cycle refers to the
process of predicting the resources (time, cost, effort) required to complete a
software development project or specific tasks within that project. Estimation is a
critical part of the planning phase of SDLC, as it helps in setting realistic
expectations, managing resources efficiently, and determining the project's feasibility.
Man-hours estimation in software development refers to
the process of estimating the total amount of human effort required to complete a
software development task, project, or feature. It is typically expressed in terms of
the number of hours that a team or individual will spend working on the project. This
estimation is crucial for planning, budgeting, and scheduling the project. It helps
determine resource requirements, assess project timelines, and evaluate project
feasibility.
Types of projects on the basis of Man-Hours:
1. Small project – Upto 500 Man-Hours
2. Medium project – Upto 1000 Man-Hours
3. Large project – Upto 1500 Man-Hours
Manhours Required = Total hours working per day x Total number of members x
Total numbers of days worked over the specific period.
Number of Working Hours a day = 8 hours
Number of Resources = 12
Time period provided = 18 months = 547 days = 78 weeks (Including Weekends and
Public Holidays)
Assuming Weekends = 156
Assuming Public Holidays = 10
Total = 166
Total working days = 547-166 = 381 working days
Hence, Estimated Manhours = 8 hours * 12 resources * 381 days = 36,576 Man
hours required.
Question – 11 Project has finally completed all the stages i.e., design, development,
testing etc. Now, it is the role of a business analyst to contact the client for testing of
the final product and have to successfully complete it. How are you going to handle
this situation? And once it is done, what will be the process to close the project?
Explain UAT Acceptance process.
Answer- User Acceptance Testing (UAT) - UAT (User Acceptance Testing) is a
crucial phase in the software development life cycle where the intended users of the
system validate the software by testing it in a real-world or production-like
environment. The primary goal of UAT is to ensure that the software meets the
business requirements, functions as expected and is ready for deployment to the
end users.
To handle the situation of testing the final product and successfully completing it, the
business analyst can follow these steps:
1. UAT Planning: Prepare a plan for User Acceptance Testing (UAT) in consultation
with the client. This plan should include the scope of testing, test scenarios, test
data, and timelines.
2. Test Environment Setup: Ensure that the required test environment is set up and
available for the client to perform testing. This may include providing access to the
testing environment, necessary test accounts, and any additional resources needed
for testing.
3. Test Execution: Coordinate with the client to execute the planned test scenarios.
Monitor the testing progress, provide support for any questions or issues that arise,
and track the test results.
4. Defect Management: If any defects are identified during UAT, work closely with the
client to understand the issues, document them, and track their resolution.
Collaborate with the development team to address the reported defects and verify
their fixes.
5. UAT Sign-off: Once the client has completed testing and is satisfied with the
product’s functionality, obtain their formal sign-off or approval which includes RTM
and closure documents. This indicates that the client has accepted the final product
and is ready to move forward with its deployment.
Regarding the process to close the project, it typically involves the following steps:
1. Final Documentation: Ensure that all project-related documentation is complete,
including requirements, design documents, test cases, and user manuals. Review
and update these documents to reflect the final product.
2. Project Review: Conduct a project review meeting with key stakeholders, including
the client, to discuss the overall project performance, achievements, and lessons
learned. Gather feedback and suggestions for improvement.
3. Project Closure Report: Prepare a project closure report summarizing the project’s
objectives, deliverables, timeline, budget, and overall success. Include any important
metrics or performance indicators.
4. Handover or Deployment: Coordinate with the necessary teams, such as
deployment or operations, to ensure a smooth transition of the final product to the
production environment. Provide any necessary training or documentation to support
the deployment process.
5. Post-Project Evaluation: After the product is deployed and operational, conduct a
post-project evaluation to assess its performance, gather user feedback, and identify
any areas for further improvement.
UAT Acceptance Process: The UAT (User Acceptance Testing) Acceptance Process
is the formal procedure through which stakeholders (typically business users or
clients) validate and approve the software application to ensure it meets business
requirements and is ready for deployment. It is a critical phase in the SDLC that
involves testing the system in a real-world environment to ensure it works as
intended before going live.
The User Acceptance Testing (UAT) Acceptance process involves the following
steps:
1. Test Planning: Define the scope of UAT and identify the key features or
functionalities to be tested. Prepare test scenarios and test cases based on user
requirements.
2. Test Execution: Perform the planned test scenarios, following the test cases
provided. Validate the system's behaviour against the expected outcomes and verify
that it meets the user's acceptance criteria.
3. Defect Reporting: If any issues or defects are identified during UAT, document
them in a structured manner, including detailed steps to reproduce the problem.
Communicate the issues to the development team for resolution.
4. Defect Resolution: Collaborate with the development team to address the reported
defects. Verify the fixes provided by the development team and retest the affected
areas.
5. Sign-off: Once all test scenarios have been executed, defects have been resolved,
and the system meets the user's acceptance criteria, provide formal sign-off or
approval. This signifies that the client accepts the product as meeting their
requirements.
6. UAT Closure: Document the UAT results, including the test execution summary,
any outstanding issues, and the overall assessment of the product.
Question – 12 Explain Project closure document.
Answer – Project Closure Document - A Project Closure Document is a formal
document that signifies the conclusion of a project. It provides a detailed summary of
the project’s performance, achievements, lessons learned, and any remaining tasks
or issues. The purpose of this document is to ensure that the project is officially
closed and that all stakeholders have agreed that the project has met its objectives.
The Project Closure Document is typically prepared by the project manager or the
project team and is presented to stakeholders, including the client, team members,
and management.
The project closure document typically includes the following sections:
1. Project Overview: This section provides an overview of the project, including its
objectives, scope, and stakeholders involved. It summarizes the project’s purpose
and sets the context for the closure report.
2. Project Achievements: Here, the document highlights the key achievements and
deliverables of the project. It outlines the successful completion of milestones, tasks,
and any significant accomplishments that were achieved.
3. Project Timeline and Budget: This section provides an overview of the project
timeline, highlighting the start and end dates, major phases, and milestones. It also
includes information on the project's budget, including any significant deviations or
changes.
4. Lessons Learned: The lessons learned section reflects on the project successes
and challenges. It includes a comprehensive analysis of what worked well and what
could have been improved. It highlights valuable insights and recommendations for
future projects.
5. Stakeholder Feedback: This section gathers feedback from key stakeholders
involved in the project. It includes their opinions, suggestions, and any concerns they
may have expressed. The feedback helps in assessing the overall satisfaction and
identifying areas for improvement.
6. Risks and Issues: The closure document discusses the risks and issues
encountered throughout the project. It outlines the actions taken to mitigate these
risks and resolve any issues that arose during the project's lifecycle.
7. Project Performance: This section evaluates the project's performance against the
defined objectives and success criteria. It assesses factors such as scope
adherence, timeline adherence, budget performance, quality of deliverables, and
customer satisfaction.
8. Project Sign-off: The closure document includes formal sign-off or approval from
key stakeholders, indicating their acceptance and satisfaction with the project’s
outcomes. This signifies the official closure of the project.
9. Project Documentation: This section provides an overview of the project
documentation, including the list of documents produced, their location, and
accessibility for future reference.
10.Next Steps and Recommendations: The closure document outlines any
recommended actions or next steps following the project's closure. It may include
suggestions for further improvements, additional tasks, or follow-up activities.
The project closure document serves as a final report that captures the project's
journey, outcomes, and key learnings. It provides a reference for future projects,
helps in evaluating project success, and facilitates knowledge transfer to
stakeholders involved in the project.
For Example:

S/N Points to Include Details Reference Link1

1 Did the client sign
off on the
UAT testing
Date of Signoff 12-MAR-2026 Business_Scope.do
Name of the resource Mr. Tarun cx
2 Objectives of the
project
User friendliness Achieved
Customer satisfaction ROI (Return of
Investment) in 6 to
12 months
More Categories Achieved
3 Functionalities
worked on
Secured payment Achieved FRD.docx
process
Categories Achieved
4 Infrastructure
Software installed Achieved Procurement.docx
Laptops purchased Achieved
5 Funding
Amount approved 2 Crores Financialdetails.xls
Amount used 2 Crores x
6 Overall project
information
Escalations 30
Customer satisfaction High
7 Value to the
company
Positive/Negative Company has
gained
successful
integration of
 processes,
increased
turnover by 25%,
increased
efficiency by 20%