Q.1 - Functional Requirements.

REQ ID REQ NAME REQ DESCRIPTION PRIORITY

FR0001 Farmer Farmers should be able 9
Registration to register with the
application

FR0002 Farmer Farmers should be able 9

Search for to search for available
Products products in fertilizers,
seeds, pesticides

FR0003 Printer print the When an order is 8

package slip fulfilled, the local
printer shall print a
packing slip
FR0004 Adding the product to Farmer should be able 7
the cart to add to cart once they
select the product

FR0006 Product tracking Farmers should be able 7

to track the ordered
items
FR0007 New user email For a new customer he 8
verification has should do the email
verification for the
doing login
FR0008 Payment option for the The farmers should 8
customer have the payment
options either upi cod
or through cards
FR0009 After Cancellation After cancellation is 8
refund option initiated the refund to
be followed.
FR0010 Manufacture tracking Manufacture should be 9
facility able to track the stock

FR0011 OTP initiation for When item is in the 9

payment payment the OTP is
send to registered
mobile number.
FR0012 Address update option the farmer should be 9
able to update his
address every time of
checkouts.
NFR0013 Page Each Page should load 7
Loading within 2 seconds time
Time
NFR0014 Payment receipt The farmer should get 8
the receipt with in a
hour of order.
NFR0015 Page timeout After 15minute of 7
activity the page will
logout
NFR0016 Fascinating Home page The home page should 8
not contain much
information and should
look good.
NFR0017 Quick Payment option Payment options should 10
be quick and fast

FR0018 Review option After every order 9

customers should be
able to give review.
NFR0019 Security of data Information of farmers 8
should not be shared
NFR0020 WCAG 2.1. The system must meet 8
Web Content
Accessibility Guidelines
WCAG 2.1
Q.2 - Minimum 5page designs.
Q.3 Tools (Visio, Balsamiq).

Microsoft Visio.
Microsoft Visio is a diagramming and vector graphics application used to create a wide variety of
diagrams, such as flowcharts, organizational charts, network diagrams, floor plans, and more. It is
part of the Microsoft Office family, though it is sold separately from the core Office suite.

Visio allows users to represent complex ideas visually, making it easier to communicate processes,
systems, and structures. Visio is commonly used in business environments, engineering, IT, and
design to communicate technical information or represent processes visually.

Balsamiq.
Balsamiq is a software tool used for wireframing and prototyping. It allows users to create low-
fidelity mockups of websites or applications, which helps in planning the layout and user interface
(UI) design before development begins. The tool is known for its simple, sketch-like design that
encourages quick iteration and focus on structure, rather than detailed visuals.

Balsamiq is commonly used by UX/UI designers, product managers, and developers in the early
stages of design to communicate ideas and gather feedback. The interface is intuitive and features
drag-and-drop components that make it easy to design and adjust the wireframes. Balsamiq is
available as both a web app and a desktop app, and it is often used for brainstorming, design
reviews, and user testing.

Q.4 RTM.

Ans:

REQ ID REQ NAME REQ DESIG D1 D2 D3 D4 T1 T2 T T4 UAT

DESCRIPTIO N 3
N
FR0001 Farmer Farmers Y Y Y Y Y Y Y Y Y N
Registration should be
able to
register with
the
 application
FR0002 Farmer Farmers Y Y Y Y Y Y Y Y Y N
Search for should be
Products able to
search for
available
products in
fertilizers,
seeds,
pesticides
FR0003 Printer print When an Y Y Y Y Y Y Y N N N
the package order is
slip fulfilled, the
local printer
shall print a
packing slip
FR0004 Adding the Farmer Y Y Y Y Y N N N N
product to should be Y
the cart able to add
to cart once
they select
the product
FR0006 Product Farmers Y Y Y N N N N N N
tracking should be Y
able to track
the ordered
items
FR0007 New user For a new Y Y Y Y N N N N
email customer he Y Y
verification has should
do the email
verification
for the doing
login
FR0008 Payment The farmers Y Y Y Y Y Y N N N N
option for should have
 the the payment
customer options
either upi
cod or
through
cards
FR0009 After After Y Y Y Y N N N N N
Cancellation cancellation Y
refund is initiated
option the refund to
be followed.
FR0010 Manufacture Manufacture Y Y Y Y Y N N N N N
tracking should be
facility able to track
the stock
FR0011 OTP When item is Y Y Y Y Y Y Y N N N
initiation for in the
payment payment the
OTP is send
to registered
mobile
number.
FR0012 Address the farmer Y Y Y Y N N N N N
update
should be
option
Y
able to
update his
address
every time of
checkouts.
NFR0013 Page Each Page Y Y Y Y N N N N N N
Loading
should load
Time
within 2
seconds time
NFR0014 Payment The farmer Y Y Y Y Y Y N N N N
receipt
 should get
the receipt
with in a
hour of
order.
NFR0015 Page After Y Y Y Y Y Y N N N N
timeout
15minute of
activity the
page will
logout
NFR0016 Fascinating The home Y Y Y Y Y Y N N N N
Home page
page should
not contain
much
information
and should
look good.
NFR0017 Quick Payment Y Y Y Y Y Y N N N N
Payment
options
option
should be
quick and
fast
FR0018 Review After every Y Y Y N N N N N
option
order Y Y
customers
should be
able to give
review.
NFR0019 Security of Information Y Y Y Y Y N N N N
data
of farmers Y
shouldnot be
shared
NFR0020 WCAG 2.1. The system Y Y Y Y Y N N N
must meet Y Y
 Web Content
Accessibility
Guidelines
WCAG 2.1

Q.5 10 Test case documents.

Ans:

Test Case ID PQ9437 Test Case Name login

Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test

Scenario: website for online shopping of farm products, in that we have login we have 4inputs
3compulsory 1 optional and after that results are being shown
Link to that page

Set 1
Inputdata 1.Userid
2.password
3.capcha
4.otp

Expected Home page

behavior /error page
pops up
Actual Home page
behavior /error page
pops up
comments Test was good
Pass/fail Pass

2.
 Test Case ID PQ9437 Test Case Name New user
Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test

Scenario: website for online shopping of farm products, in that we have new user we have 1
4compulsory 1 optional and after that results are being shown
Link to that page:

Inputdata 1.username
2.setpassword
3.mail
verification
4.capcha
5.mobile otp
Expected Registered
behavior done and
home page
shows
Actual Homepage
behavior comes
comments Test was good
Pass/fail Pass

3.

Test Case ID PQ9437 Test Case Name Online purchasing

Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test

Scenario: :website for online shopping of farm products, in that we perform online purchasing
we have 1 compulsory 1 optional and after that results are being shown
Link to that page:

Inputdata 1.product
name
 2.filters
Expected Product
behavior options
Actual Different
behavior product pops
comments Test was good
Pass/fail pass

4.

Test Case ID PQ9437 Test Case Name Product availability

Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test

Scenario: :website for online shopping of farm products, in that we should have product
available in which we have 3 inputs 3 compulsory and after that results are being shown
Link to that page

Inputdata 1.manufacturin
g code
2.capcha
4.password
Expected stock
behavior information
Actual Same as
behavior expected
comments Test was good
Pass/fail Pass

5.

Test Case ID PQ9437 Test Case Name Payment gateway

Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test

Scenario: website for online shopping of farm products, in that we have payment gateway in
which we have4 inputs 4 compulsory and after that results are being shown
Link to that page
 Inputdata 1.expiry
2.cvv
3.otp
4name

Expected Transaction
behavior page
Actual Same as
behavior expected
comments Test was good
Pass/fail pass

6.

Test Case ID PQ9437 Test Case Name Browse product

Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test

Scenario: website for online shopping of farm products, in that we have browse product option
in which we have4 inputs 4 compulsory and after that results are being shown
Link to that page

Inputdata 1.category
2.size
3.availabilty
4.price range
Expected Different
behavior product
options
Actual Same as
behavior expected
comments Test was good
Pass/fail Pass

7.

Test Case ID PQ9437 Test Case Name Experience rating

Project ID 1234 Project Name Farmers website

PM ID 786 PM Name Mr Vandanam

Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test
 Scenario: website for online shopping of farm products, in that we have experience option in
which we have4 inputs 3 compulsory and after that results are being shown
Link to that page

Inputdata 1.experience
2.names
3.phone
number
Expected Review done
behavior
Actual Same as
behavior expected
comments Test was good
Pass/fail Pass

8.

Test Case ID PQ9437 Test Case Name Product cancel

Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test
Scenario: website for online shopping of farm products, in that we have product cancel option in
which we have2 inputs and click ok and after that results are being shown.
Link to that page

Inputdata Order id
Capcha
Expected Order
behavior cancellation
page
Actual Yes same a
behavior expected
comments Test was good
Pass/fail Pass

9.

Test Case ID PQ9437 Test Case Name Helpline

Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test
 Scenario: website for online shopping of farm products, in that we helpline option in which we
have4 inputs and click ok and after that results are being shown.
Link to that page

Inputdata Name
Number
Query
Expected Call person
behavior calls you
Actual Same as
behavior expected
comments Test was good
Pass/fail Pass

10.

Test Case ID PQ9437 Test Case Name Download Payment

receipt
Project ID 1234 Project Name Farmers website
PM ID 786 PM Name Mr Vandanam
Test strategy ID PQ9437 Tester ID
Test plan ID PQ9437 Tester name
Test schedule ID PQ9437 Date of test

Scenario: website for online shopping of farm products, in that we have payment receipt option
in which we have3 inputs and click ok and after that results are being shown.
Link to that page

Input data Order id

captcha
password

Expected Shows
behavior Payment
receipt
Actual Same as
behavior expected
comments Test was good
Pass/fail Pass
Q. 6 – DB Design.
After the requirements are thoroughly explained to the entire project team by business analyst, the
Database architects have decided to do the database design and also to represent the in-flow
andout-flow of data
Q. 7 – Data Flow Diagram.
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
Q. 8 - Change Request.
Ans - 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 are in agreement 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
Q. 9 – Change Request Vs an Enhancement.
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 Auction system for their Crop yields. As a BA, what will be your response?

Ans - 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 would 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 accordiangly. I 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.
Q 10 – Estimations.
Come up with estimations – How many Manhours required.

Ans - Estimating the number of man-hours required for the requested enhancements (adding crop
yields, displaying them to the public, and implementing an auction system) would depend on various
factors, including the complexity of the features, the size of the existing system, the development
team's expertise, and the development methodology used. Without specific details about the
project, it's challenging to provide an accurate estimation. However, I can offer a general guideline
based on industry standards and experience:

1. Requirement Gathering and Analysis: 10-20 man-hours

2. This includes meetings with stakeholders, gathering detailed requirements, analyzing the impact,
and documenting the enhancements.
3. Design and Architecture: 20-40 man-hours
4. This involves designing the system components, database structure, and user interface for the new
features. It also includes identifying the necessary changes to accommodate the enhancements.
5. Development and Coding: 40-80 man-hours
6. The actual development of the new features, including backend and frontend coding, integration
with existing modules, and implementation of the auction system.
7. Testing and Quality Assurance: 20-40 man-hours
8. This phase involves writing test cases, performing unit testing, integration testing, and ensuring
the proper functioning and stability of the added features
9. Deployment and User Acceptance Testing (UAT): 10-20 man-hours
10.Deploying the updated system to a testing environment, conducting user acceptance testing, and
resolving any issues identified during UAT.
11. Documentation and Training: 10-20 man-hours
12.Documenting the new features, updating user manuals or guides, and providing training or
support materials for farmers and users.

It's important to note that these estimations are rough figures and can vary significantly depending
on the complexity and scale of the enhancements, the team's productivity, and other project-specific
factors. It's recommended to involve the development team in the estimation process to get a more
accurate assessment based on their expertise and knowledge of the project.
Q.11 UAT process.
Ans:

1. Planning

Planning is all about outlining your strategy for the UAT test that has to be performed on your
product. There is no one strategy used here; in fact, people have different approaches to outlining
the strategy, but you should always go for the one that aligns with your business requirements in the
best possible way. For example, what part of the app should you perform the tests on? Which end-
user will test which part of the app?

2. Test Scenarios

Once you have planned the UAT test, it is time to think of the different test scenarios. Here we are
referring to all the situations that can arise while using the product and what needs to happen in
each situation. These scenarios help with the creation of test cases. Let us assume that you have
asked a web development agency for an e-commerce website. One test case would be to test the
website during the sales season. As there would be many customers, testing the web site's
functionality, load speed, and overall user experience is a must-have test scenario.

3. Execution

Once the previous steps are complete, it is time to begin the UAT testing. It is best to record and
document the entire process. While the developers are not a part of the UAT team, ensure that they
witness the entire UAT session. The reason for this is because the end-users might not explain the
problems in a way that developers expect or need. So, by having them witness the entire test, they
will understand potential issues better. Furthermore, there may be times when end-users don’t
report a problem, but developers see it themselves when watching the UAT session. So it is well
worth the time of your developers to witness the UAT session.

4. Final Decision

The UAT test is there to analyze if the product is per the business requirements or not. If the answer
comes in positive, the product is ready for launch into the market. If the answer is negative, you'll
have to go through another round of UAT testing after fixing all the bugs and glitches.
Q.12 Explain Project closure document.
Ans. A project closure document is a comprehensive report that summarizes the entire project's
lifecycle, outcomes, and lessons learned. It serves as a formal record of the project's completion and
provides important information for future reference. The 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's 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.