Online Agriculture Products Store

1. Business Process Model

1. Goal: To build an application/online store which can facilitate farmers to buy Agriculture goods from
anywhere
2. Inputs: Farming products and companies manufacturing them.
3. Resources: Mobile phone, Computer, Internet connectivity, Farming companies, Agricultural
products like Fertilizers, Seeds, and Pesticides.
4. Activities:
i. Farmer should Register with Name and Address
ii. Then enter the online store with Login details.
iii. Select the product they want to purchase.
iv. Farmer should either pay by Card/Online banking.
v. Order confirmation.
vi. Delivery of Agricultural goods.

5. Output: Application where farmers can buy seeds and agriculture products.
6. End Value: Satisfied farmer will be able to use the product in their Farm. User friendly application
which is understood by all kinds of Farmers.

2. SWOT

Strengths Weakness

1. Company is available with Talented 1. Company do not have enough

individuals. resources to work on the project.
2. They are already trained individuals. 2. Team handling this kind of project for
3. Project Budget is INR 2 Cr. the first time.
4. Good IT Experience 3. Time duration is 18 months, which
seems less.

Opportunities Threats

1. The project is the first kind of project 1) While developing a project, they must keep
being done by any company. the CSR initiative in mind.
2. To provide Solution for the farmers 2) How to deliver agricultural product at rural
Problem. and poor part of country.
3) Are farmers educated about the Online
store?

3. Feasibility Study
Cont. to Next page
 1. Budget - INR 2 crores
2. Time Frame – 18 months
3. Trained Resources – 12 Resources
a. Delivery Head – 1 – Mr. Karthik
b. Project Manager – 1 – Mr. Vandanam
c. Senior Java Developer – 1 – Ms. Juhi
d. Java Developers – 4 – Mr. Teyson, Ms. Lucie, Mr. Tucker & Mr. Bravo
e. Network Admin – 1 – Mr. Mike
f. Database Admin – 1 – Mr. John
g. Testers – 2 – Ms. Alekya and Mr. Jason
h. BA – 1 – Me
4. Hardware –
a. Laptops – 12
b. Desks and Chairs – 12 each
5. Software –
a. Licenses – 12

Technical Feasibility:

 Hardware – 12 Laptops for all the 12 resources in the organization

 Software –
o Java license – there are 7 JAVA users. 4 Developers and 1 Sr. Developer and 2 Testers are
going to use the software
 Network – Network admin will make sure that there isn’t any issue with the network, while the
development team works on developing the codes.
 Database admin – They will ensure that all the data of the customers and sellers data is updated and
stored at the right place.

Operational Feasibility: Time – 18 months

1. 2 months - Requirement gathering and design by BA.

2. 1 month – Project planning - The Project manager and Sr. Developer will discuss with the team and
specify the Roadmap of the project and they will then decide, how the project will be completed.
3. 12 months – Project Development - Being a waterfall model, the project will be developed and
tested in 3 phases.
1. For customers:
i. Registration and Login phase – 2 months: In this phase, the development team will
work on the Registration page and Login page, so that the customer can login with
password and also update their addresses for delivering the product on time. It will
take approximately 2 months, as the Development team will write the code and
then Testing team will test the code. Hence there will approx. 3 times development
and testing (D1-T1, D2-T2 and D3-T3)
ii. Product Selection phase – 3 months: In this phase, development team will start the
coding on how to search the product (including filters with category), select the
product and add them to the cart. This phase will take approx. 3 months and will
take approx. 4 times development and testing (D1-T1, D2-T2, D3-T3 and D4-T4)
iii. Billing and Payment phase – 3 months: In this phase, the development team will
develop the codes for payment section, where the customers can make the payment
adding their Banking details for their selected items. This phase will also include
their Banks as well. The payment modes should be via Credit card, Debit card, Net
banking, Digital payments and Pay on Delivery. This phase will take approx. 4 -5
times Development and testing, as they also need to make sure that the payments
Cont. to Next page
 gets cleared from the customer’s bank and payment is also received correctly. (D1-
T1, D2-T2, D3-T3, D4-T4 and D5-T5)
iv. Delivery phase – 2 months – In this phase, development team will develop codes to
make that the product is delivered within the time specified. They also have to make
sure that if the product is not available at the nearby warehouse, the delivery date
should get updated, as the product will now be delivered from the 2nd nearby
warehouse. This phase will also include the 3rd party sellers as well.

2. For Sellers:
i. Registration and Login phase – While developing the codes for customer, the team
will also develop the codes for Sellers to register themselves, so that they can sell
their product.
ii. Product Updating phase – 2 months – Development team will develop codes for
Seller to update their product on the online store and also keep updating new
products. Hence this phase should take approximately 2 months including
Development and Testing both.
iii. Billing and Payment phase – Development team and manage developing codes, as
in this phase, the payment should be reached to the seller as well under the same
timeline, when developing codes for customers.
iv. Delivery phase – This phase will also comes under the phase when developing codes
about delivering the products by coordinating with sellers to ship under same time
line.

4. 1 months - Final Testing: Once the coding is completed, the Testers will test the project as final
testing to make the product delivery ready

5. 1 months – Project delivery and Training – The delivery head, Mr. Karthik will lead this phase with
the help of the development team and BA to make sure the training is completed and product is
delivered as per customer’s satisfaction.

6. 1 month – UAT – Customer will use the software and confirm, if there is any issue with the product
or not.

Financial feasibility – INR 2 crores

4. GAP Analysis:

Cont. to Next page

 5. Risk Analysis:
1. BA Risks:
i. BA missing seller details.
ii. Due to lack of time, BA didn’t plan the meetings with the Stakeholders.
iii. Stakeholders rushing through the details while sharing the requirements.
iv. Being a new kind of project, BA might have lack of domain knowledge.
v. BA missing the CSR (Corporate Social Responsibility) initiative point.

2. Process/Project Risks:
i. Cost Risk: Project may get stalled due to lack of budget. Being a new kind of project in the
market, sponsors may be unaware of the budget the project need
ii. Market Risk: Being a new kind of project in the Market, stakeholders may miss
requirements to share with the BA
iii. Governance Risk: Agriculture is always related to Govt any new Govt policy may change
the whole process or stall the whole project completely.
iv. Strategic Risk: Sellers may not like this process of giving options to the farmers, as they
might loose on their profit. Hence, they may go on strike.

6. Stakeholder Analysis (RACI Matrix)

RACI - Responsible (R) - Accountable (A) - Consulted (C)- Informed (I)- Authorize (*) Not Available (NA)
Ms. Teyson,
Mr Peter, Kevin, Mr. Jason
Mr. Mr. Juhi Lucie, Sourabh
Henry - Ben - & Ms.
Tasks Karthik Vandanam Sr Bravo & Bhattacharya
Project Key Alekya -
– DH - PM Java Tucker - - BA
Sponsor Stakeholders Testers
Dev Java Dev
Requirement
* C NA A/I NA A NA R
Gathering
Requirement
NA NA NA I NA NA NA R
Analysis
Development * NA NA R/A C/A R NA C
Testing NA NA NA R/A I NA R I
Implementation NA NA R I I NA NA R
UAT I NA NA R/A NA NA NA C

7. Business Case Document – Excel Sheet updated.

Project Name Project Manager

Online Agriculture Product Store Mr. Vandanam
Client Duration
Soony Ltd. 18 Months

To build the online store for farmers to buy agriculture

Executive Summary products online with just an
internet connectivity.

Cont. to Next page

 To build an application/online store which can facilitate
Mission Statement farmers to buy Agriculture goods from anywhere

An Online store which will facilitate all remote area farmers

to purchase agriculture products, like seeds, pesticides and
Product/Service fertilizers from anywhere through internet connectivity.

This project is going to be built upon an online platform

which will be developed by our developers and will be
delivered to the client. This project will be completed in 4
phases i.e Registration/Login phase, Product selection
phase, Billing/Payment phase and Delivery phase. The
Project Definition developers will write the codes and test those codes twice
or thrice at the end of every phase. Once the coding is
completed, Testers will finally test the codes to confirm, the
product working perfectly. Once tested, the product will be
delivered to the client with product manuals and trainings
will also be provided to use the product.

1. Farmers are facing problems in procuring fertilizers. They

are buying fertilizers from their nearby places, which may be
far from their places.
2. Certain crops are also not available with those places,
where they are buying seeds.
Existing Problems 3. Due to lack of options in pesticides, farmers have to buy
the low quality pesticides every year.
4. Farmers also have to buy these products with higher costs
every time.
5. Lack of information on Seeds, Pesticides and Fertilizers

With this project farmers can solve several problems like.

1. They can procure fertilizers from their nearby places.
2. Good Quality fertilizers can be procured.
3. Farmers can buy high quality pesticides.
4. They can buy crops which were not available in their
previous store.
Benefits of this project 5. They will have multiple options to buy all these products.
6. Farmers will have multiple options to select based on their
budget.
7. All these products can be delivered to their homes
without any delay.
8. Farmers will have information on Seeds, Pesticides and
Fertilizers select the quality product.

1. Information to Feed: Information on Product, Suppliers,

Bankers and Delivery companies
2. Hardware - Laptops with good configuration, i.e RAM,
Resources Required for the Project Hard drive and good processor.
3. Software - JAVA and other applications required.

Cont. to Next page

 1. There has to a team to manage the existing Suppliers,
Customers and Bankers and Delivery orgs
Organizational Change required 2. New team to maitiain new Supppliers, Customer, Bankers
etc.

Current Finance - INR 2 Crores

Assuming profit - INR 10 lakhs
ROI ROI - 10,00,000/2,00,00,000 = 5% ROI

1. Direct Stakeholders - Mr. Henry, Mr. Pandu and Mr.

Stakeholders Dooku
2. Farmers

8. 4 SDLC Methodologies

1. Waterfall (Sequential): Waterfall methodology is a development process where all the phases flow
like a waterfall. Each phases need to be completed before the next phase begins. There are 5 stages
in waterfall methodology.
i. Requirement – Waterfall model depends on all the requirements gathered and
understood upfront.
ii. Design – Once the requirement is gathered, the technical team designs the requirement
into layouts, data models, prototypes etc.
iii. Implementation – One the design is completed; the technical team starts coding as per
the design or prototypes.
iv. Testing – before the product is delivered to the customer, the product/software needs to
be tested.
v. Deployment/Maintenance – Once the software is tested, it gets released to the customer
and with that maintenance phase begins.

Cont. to Next page

 2. Iterative: In this development process, each phase builds on the previous one. The development
takes place in iterations and in small parts at a time. It’s a process of gradual improvement and
learning from previous iterations, as how to improve the next. There are 4 phases in this
methodology:
i. Requirement: The Goal needs to set accordingly, as every iteration is different from later
ones and there is no previous iterations to work from.
ii. Design: In this phase, design needs to be created to solve the requirements, which
includes technical designs, process flow diagrams etc.
iii. Implementation or Development: The technical team will create the first iteration which
will be informed by analysis and design.
iv. Testing: after the iteration, it will be tested to find out the improvement. It can also be
checked with project stakeholders.
v. Review: Team will evaluate the success of the iteration and align on anything that need to
be changed.

Cont. to Next page

 3. Spiral Model: Spiral model is an SDLC methodology which combines Iterative development and
Waterfall model. It is used for Risk management. This SDLC model is mostly used for large and
complicated projects. The spiral model enables gradual releases and refinement of a product
through each phase of the spiral as well as the ability to build prototypes at each phase. It can
manage unknown risks once the project is started.

The radius of the Spiral model represents the cost of the project, and the angular degree represents
the progress made in the current phase. Every phase can be broken into four quadrants:

i. Identifying and understanding requirements - Every phase can be broken into four
quadrants: identifying and understanding requirements, performing risk analysis, building
the prototype and evaluation of the software's performance.
ii. Performing risk analysis: risk analysis should be performed on all possible solutions to find
any faults or vulnerabilities, such as, running over the budget or areas within the software.
iii. Building the prototype: Prototype is built and tested. This step includes architectural
design, design of modules, physical product design and the final design.
iv. Evaluation of the software's performance: In the final quadrant, test results of the newest
version are evaluated. This analysis allows programmers to stop and understand what
worked and didn’t work before progressing with a new build. At the end of this quadrant,
planning for the next phase begins and the cycle repeats. At the end of the whole spiral,
the software is finally deployed in its respective market.

Steps: While the phases are broken down into quadrants, each quadrant can be further broken
down into the steps that occur within each one. The steps in the spiral model can be generalized as
follows:

 The new system requirements are defined in as much detail as possible. This usually involves
interviewing a number of users representing all the external or internal users and other
aspects of the existing system.
 A preliminary design is created for the new system.

Cont. to Next page

  The first prototype of the new system is constructed from the preliminary design. This is
usually a scaled-down system and represents an approximation of the characteristics of the
final product.
 A second prototype is evolved by a fourfold procedure: (1) evaluating the first prototype in
terms of its strengths, weaknesses, and risks; (2) defining the requirements of the second
prototype; (3) planning and designing the second prototype; (4) constructing and testing the
second prototype.
 The entire project can be aborted if the risk is deemed too great. Risk factors might involve
development cost overruns, operating-cost miscalculation and other factors that could
result in a less-than-satisfactory final product.
 The existing prototype is evaluated in the same manner as was the previous prototype, and,
if necessary, another prototype is developed from it according to the fourfold procedure
outlined above.
 The preceding steps are iterated until the customer is satisfied that the refined prototype
represents the final product desired.
 The final system is constructed, based on the refined prototype.
 The final system is thoroughly evaluated and tested. Routine maintenance is carried out on a
continuing basis to prevent large-scale failures and to minimize downtime.

4. Agile (Scrum): The Agile methodology is a way to manage a project by breaking it up into several
phases. It’s a process for managing a project that involves constant collaboration and working in
iterations. Agile project management works off the basis that a project can be continuously
improved upon throughout its life cycle, with changes being made quickly and responsively.

Agile's four main values are:

 Individuals and interactions over processes and tools

 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan

Frameworks of Agile:

 Scrum
Cont. to Next page
  Kanban
 Extreme Programming (XP)
 Adaptive Project Framework (AFP)

SCRUM: Scrum is an Agile development methodology used in the development of Software based on
an iterative and incremental processes.

Scrum Methodology and Process: Scrum is executed in temporary blocks that are short and
periodic, called Sprints, which usually range from 2 to 4 weeks. Each Sprint is an entity in itself, that
is, it provides a complete result, a variation of the final product that must be able to be delivered to
the client with the least possible effort when requested.

The process has as a starting point, a list of objectives/ requirements that make up the project plan.
It is the client of the project that prioritizes these objectives considering a balance of the value and
the cost thereof, that is how the iterations and consequent deliveries are determined.

Events in Scrum

Each of the Scrum events facilitates the adaptation of some of the aspects of the process, the
product, progress or relationships.

1. Sprint: Sprint is the basic unit of work for a Scrum team. This is the main feature that marks the
difference between Scrum and other models for agile development.
2. Sprint Planning: The goal of the Sprint Planning is to define what is going to be done in the
Sprint and how it is going to be done. This meeting is held at the beginning of each Sprint and is
defined how it will approach the project coming from the Product Backlog stages and deadlines.
Each Sprint is composed of different features.
3. Daily Scrum: The objective of the Daily Scrum is to evaluate the progress and trend until the end
of the Sprint, synchronizing the activities and creating a plan for the next 24 hours. It is a brief
meeting that takes place daily during the Sprint period. Three questions are answered
individually: What did I do yesterday? What am I going to do today? What help do I need? The
Scrum Master should try to solve problems or obstacles that arise.
4. Sprint Review: The goal of the sprint review is to show what work has been completed with
regards to the product backlog for future deliveries. The finished sprint is reviewed, and there
should already be a clear and tangible advancement in the product to present to the client.
5. Sprint Retrospective: The team reviews the completed goals of the finished sprint, write down
the good and the bad, so as not to repeat the mistakes again. This stage serves to implement
improvements from the point of view of the development process. The goal of the sprint
retrospective is to identify possible process improvements and generate a plan to implement
them in the next Sprint.

Cont. to Next page

 9. SDLC methodologies

1. Waterfall: Waterfall model is the oldest and most structured method. In this model, each phase depends
on the outcome of the previous phase and all the phases runs sequentially. This model provides
discipline and gives a tangible output at the end of each phase. However, this model doesn’t work well
when flexibility is a requirement. There is little room for change once a phase is deemed complete, as
changes can affect the cost, delivery time, and quality of the software.

2. Iterative: In the iterative process, each development cycle produces an incomplete but deployable
version of the software. The first iteration implements a small set of the software requirements, and
each subsequent version adds more requirements. The last iteration contains the complete requirement
set.

3. Spiral: Spiral model is an SDLC methodology which combines Iterative development and Waterfall
model. It is used for Risk management. This SDLC model is mostly used for large and complicated
projects. The spiral model enables gradual releases and refinement of a product through each phase of
the spiral as well as the ability to build prototypes at each phase. It can manage unknown risks, once the
project is started.

4. Agile: The agile methodology produces ongoing release cycles, each featuring small, incremental
changes from the previous release. At each iteration, the product is tested. The agile model helps teams
identify and address small issues in projects before they evolve into more significant problems. Teams
can also engage business stakeholders and get their feedback throughout the development process.

5. V shaped: In the V-shaped model, verification phases and validation phases are run in parallel. Each
verification phase is associated with a validation phase, and the model is run in a V-shape, where each
phase of development has an associated phase of testing.
Cont. to Next page
 10. Waterfall vs V model

Difference between V-Model and Waterfall Model

Parameter V Model Waterfall Model

V-Model is the development model in which the

entire model is divided into various sub- In the Waterfall model, an application is
development phases where the corresponding developed first, after which it is tested using
testing phase for each development phase is different testing techniques.
Definition practiced. The complete process is divided into several
For every stage in the development cycle, there is phases among which one phase should be
an associated testing phase and the corresponding completed in order to reach the next phase and
testing phase of the development phase is planned testing is almost at end phase of the development.
in parallel.

In the V-Model, the execution of the phases i.e., Waterfall Model is a relatively linear sequential
development and testing happens in a sequential design approach as each phase should be
Type/Nature
manner so type of V-Model is Sequential/Parallel in completed in order to reach the next phase. So
nature. type of this model is Continuous in nature.

In the Waterfall Model, the testing occurs after

In the V-Model, each development phase get tested
development is completed and thus if any missing
at its own level and hence no pending testing occurs
Testing and validation is identified to be implemented then
in this model also if any validation requires to be
Validation first that phase of development needs to be
implemented then it could be implemented at that
recognized and then that validation get
phase.
implemented.

As sequential phases need to be functional in case In the Waterfall Model, due to linear
Cost and of V-Model hence the cost is higher as compared to development, only one phase of development is
Complexity that of WaterFall Model also the complexity is more operational and hence cost and complexity is low
than WaterFall. as compared to that of V-Model.

In the Waterfall Model, the probability of total

In the V-Model, the probability of total number of
number of defects in the development of
Defects defects in the development of application is low as
application is high as testing is done post
testing is done in parallel to the development.
development.

11. V Model

Reason for selecting V model:

 As this project works on different phases, every phases has to go through development phase with
complicated coding. Hence every phase runs with testing also helps parallelly.
 This model saves lot of time. Hence a higher chance of success over the waterfall model.
 This model avoids the downward flow of the defects.

12. Gantt Chart:

Cont. to Next page

 13. Fixed Bid model Vs Billing model:
1. Fixed Bid project is a project in which the time and scope is fixed within a budget and has a deadline
associate with it. In fixed bid model, the client will give all the details, specs and mockups and all the
requirements upfront, so that vendor can provide a Bid showing the project cost. In this model,
vendor should be good in estimating the time and budget, as they need to explain the client, as how
much time it would take for them to finish the project and how much it would cost . This model has
less financial risk, however it has no flexibility or room for adjustments, as the budget and time is
fixed. This model usually works with smaller projects with limited features and clear requirements.

2. Billing Model (Time and Material) is a project where the project is billed in hourly basis. Vendor will
set up a team and presented to the client to bill them for their time spent on development. This
model is flexible in nature, as changes can be added in the middle of the project. This model allows
client to monitor the progress as developers present reports on work completed.

14. RG Timesheet of a BA:

Employee Name Sourabh Bhattacharya

Department Business Analysis
Activity Requirement Gathering
Supervisor Mr. Vandanam
Hourly Rate $ 70 per hour

Day 1 Date Task Logging In Logging Out Hours

Monday 13-02-23 Stakeholder Analysis 8:00 AM 10:00 AM 2:00
Eliciting Req. from Stakeholders 10:00 AM 12:00 PM 2:00
Eliciting Req. from Stakeholders 1:00 PM 5:00 PM 4:00
Tuesday 14-02-23 Eliciting Req. from Stakeholders 8:00 AM 12:00 PM 4:00
Eliciting Req. from Stakeholders 1:00 PM 5:00 PM 4:00
Wednesday 15-02-23 Documenting Requirements 8:00 AM 10:00 AM 2:00
Confirming Requirements 10:00 AM 12:00 PM 2:00
Sorting Requirements 1:00 PM 2:00 PM 1:00
Prioritizing Requirement 2:00 PM 3:00 PM 1:00
Assess Requirement Changes 3:00 PM 4:00 PM 1:00
Getting Req. Approval 4:00 PM 5:00 PM 1:00
Total Hours 24:00
Total Pay $ 1,680

Cont. to Next page

 15. RA Timesheet of a BA:

Employee Name Sourabh Bhattacharya

Department Business Analysis
Activity Requirement Analysis
Supervisor Mr. Vandanam
Hourly Rate $ 70 per hour

Day 1 Date Task Logging In Logging Out Hours

Thursday 16-02-23 Specify the Requirements 8:00 AM 9:00 AM 1:00
Model the Req. using Use case Diagrams & Matrices 10:00 AM 12:00 PM 2:00
Verify the Requirements 1:00 PM 2:00 PM 1:00
Validate the Requirement 2:00 PM 3:00 PM 1:00
Defining Business Requirements 3:00 PM 5:00 PM 2:00
Total Hours 7:00
Total Pay $ 490

16. Design Timesheet of a BA: Sheet updated.

Employee Name Sourabh Bhattacharya

Department Business Analysis
Activity Design Timesheet
Supervisor Mr. Vandanam
Hourly Rate $ 70 per hour

Day 1 Date Task Logging In Logging Out Hours

Friday 17-02-23 Preparing Test cases 8:00 AM 9:00 AM 1:00
Allocating the requirements 9:00 AM 10:00 AM 1:00
Identifying improvement opportunities 10:00 AM 11:00 AM 1:00
Assessing Design options 11:00 AM 12:00 PM 1:00
Assessing Design options 1:00 PM 2:00 PM 1:00
Estimating Benefits and Costs 2:00 PM 3:00 PM 1:00
Communicate with client about Designs & Solutions 3:00 PM 5:00 PM 2:00
Recommending Solutions 5:00 PM 6:00 PM 1:00
Total Hours 9:00
Overtime 1:00
Total Pay $ 630

17. Development Timesheet of a BA

Employee Name Sourabh Bhattacharya

Cont. to Next page

 Department Business Analysis
Activity Development Timesheet
Supervisor Mr. Vandanam
Hourly Rate $ 70 per hour

Logging Logging Hour

Day 1 Date Task
In Out s
Monda 20-02-
Coordinate meetings with the Team 8:00 AM 9:00 AM 1:00
y 23
Checking on the approvals after each Development phase 9:00 AM 11:00 AM 2:00
Clarifies all queries of technical team at the End of each Phases 11:00 AM 1:00 PM 2:00
Outlining Business Requirements 1:00 PM 2:00 PM 1:00
Working on Change in requirements in development stage from
2:00 PM 4:00 PM 2:00
clients
Total Hours 8:00
$
Total Pay
560

18. Testing Timesheet of a BA

Employee Name Sourabh Bhattacharya

Department Business Analysis
Activity Testing Timesheet
Supervisor Mr. Vandanam
Hourly Rate $ 70 per hour

Logging Logging
Day 1 Date Task Hours
In Out
Tuesda 21-02-
Work with Testing team to create system test plans 8:00 AM 9:00 AM 1:00
y 23
Create and execute the system test cases 9:00 AM 11:00 AM 2:00
Review system cases prepared by Testing team 11:00 AM 1:00 PM 2:00
Provide requirements clarifications when required by Testing
1:00 PM 2:00 PM 1:00
Team.
Take signoff from client on client project acceptance form. 2:00 PM 4:00 PM 2:00
Total Hours 8:00
$
Total Pay
560

19. UAT Timesheet of a BA

Employee Name Sourabh Bhattacharya

Department Business Analysis
Activity UAT Timesheet
Supervisor Mr. Vandanam
Hourly Rate $ 70 per hour

Cont. to Next page

 Day 1 Date Task Logging In Logging Out Hours
Wednesday 22-02-23 Develop the detailed UAT test Plan 8:00 AM 9:00 AM 1:00
Develop the test case scenario 9:00 AM 11:00 AM 2:00
Create UAT test cases 11:00 AM 1:00 PM 2:00
Test case data preparation 1:00 PM 2:00 PM 1:00
Run the test cases 2:00 PM 3:00 PM 1:00
Total Hours 7:00
Total Pay $ 490

20. Deployment n Implementation Timesheet of a BA

Employee Name Sourabh Bhattacharya

Department Business Analysis
Activity Deployment and Implementation Timesheet
Supervisor Mr. Vandanam
Hourly Rate $ 70 per hour

Day 1 Date Task Logging In Logging Out Hours

Thursday 23-02-23 Design RTM and forward to client 8:00 AM 9:00 AM 1:00
Coordinate to complete manual 9:00 AM 11:00 AM 2:00
Training sessions for end user 11:00 AM 3:00 PM 4:00
Prepare a lesson learning from project 3:00 PM 4:00 PM 1:00
Total Hours 8:00
Total Pay $ 560

21. Audits:
What is an Audit: Audit is the inspection of various books of different departments by an auditor followed
by physical checking of inventory, financial statement and several other documents to make sure that all
departments are following documented system of recording transactions.

What is a Project Audit: A project management audit is a formal review that seeks to evaluate a given
project based on specific criteria. Examples of these can include project quality, performance, and
adherence to the statement of work.

While doing the Audit of a BA, the auditor needs to check the following details.

In Q1 Auditor will check the following details:

1. Understanding of company goals does the BA has.
2. Work is Planned and Tracked.
3. Understood the Current as is process.
4. BA’s understanding of Business Requirements
5. BA conducted the Stakeholder Analysis

Cont. to Next page

 6. Requirement gathering and analysis was done correctly.
7. What Elicitation techniques has been used to gather requirements.

In Q2 Auditor will check the following details:

1. Documents have been prepared by the BA.

2. Has the BA prepared all the required documents like RTM, BPM to understand the requirement
correctly.
3. How is BA prepared the Use case and Activity diagram.
4. Was all these documents signed and agreed by the Stakeholders, before the start of the development
stage.

In Q3 Auditor will check the following details:

1. Requirements were correctly explained to the development team.

2. BA tracking the status of the project.
3. JAD session organized by the BA.
4. Timesheets sent to the reporting manager.
5. BA keeping the Stakeholders updated on the status of the project.

In Q4 Auditor will check the following details:

1. BA tracking the Testing of the product.

2. BA assisting the Testing team for Testing the product.
3. BA sending the Test data to the client.
4. BA preparing the End user manual.
5. BA preparing the client for UAT.

In Q5 Auditor will check the following details:

1. BA assisting the Delivery manager to implement the product.

2. BA helping the client to do the UAT.
3. BA organizing the training sessions for the users.
4. BA taking signoff document from the client.
5. BA sending the complete timesheet to the reporting manager.

22. BA Approach Strategy: The Business Analysis Approach is the plan that the senior or lead business analyst on
a project would create describing the way that all the Business Analysis activities will be executed.
This could include:
1. Business Analysis resources and their Roles & Responsibilities,
2. Requirements Gathering Approach for the project (techniques to be used, high level planning),
3. Stakeholder Engagement,
4. Requirements Review Process and Approval Cycles,
5. Change Management approach to requirements and agreed deliverables.
6. Other elements such as team structure, assumptions and constraints could also be included.

As a Business Analyst, following are the steps which needs to be followed to complete a Project.

 Elicitation Techniques to apply – There are several Elicitation techniques to be used to elicit the
requirement, however for this project, we are going to use the below Elicitation techniques.
a) Brainstorming – We are going to arrange sessions, where participants are allowed to
provide inputs without criticism, discussion, or evaluation. The goal is to be creative and
gather as many ideas as possible in a short period of time.

Cont. to Next page

 b) Interviews – We will be interviewing every Stakeholder to elicit the requirements
needed to complete the project.
c) Workshops – We are going to arrange workshops, which will be a focused event and will
be attended by Key Stakeholders and SMEs. The purpose of these workshops will be for
Planning, Analysis, Design, Scoping, Requirements elicitation, Modelling, or combination
of any of these. This elicitation technique will also be used for generating ideas for new
features of the products, to reach consensus on a topic and to review requirements and
design.
d) Surveys or Questionnaire – There will be Surveys or Questionnaires sent to all the
Stakeholders and SMEs, which will include multiple range of open and closed ended
questions, which will extract the information about the desired product, work practices
and behavioral attitudes etc.

 Stakeholder Analysis – Stakeholder Analysis involves Identifying the Stakeholders who will be
directly or indirectly impacted by the change and analyzing the information once collected.
a) Identifying Stakeholders:
 Internal Stakeholders –
 Project Manager – Mr. Vandanam
 Senior Java Developer - Ms. Juhi
 Java Developers – Mr. Teyson, Ms Lucie, Mr Tucker, Mr Bravo
 Network Admin – Mr. Mike
 DB Admin – Mr. John
 Testers – Mr. Jason and Ms. Alekya
 BA – Mr. Sourabh Bhattacharya

 External Stakeholders –
 Sponsor - Mr. Henry
 Financial Head – Mr. Pandu
 Project Coordinator – Mr. Dooku
 Key stakeholders - Peter, Kevin and Ben

b) Prioritizing Stakeholders: RACI Matrix -

RACI - Responsible (R) - Accountable (A) - Consulted (C)- Informed (I)- Authorize (A*) – Not Available (NA)
Ms. Teyson,
Mr Peter, Kevin, Mr. Jason
Mr. Mr. Juhi Lucie, Sourabh
Henry - Ben - & Ms.
Tasks Karthik Vandanam Sr Bravo & Bhattacharya
Project Key Alekya -
- DH – PM Java Tucker - - BA
Sponsor Stakeholders Testers
Dev Java Dev
Requirement
A* C NA A/I NA A NA R
Gathering
Requirement
NA NA NA I NA NA NA R
Analysis
Development A* NA NA R/A C/A R NA C
Testing NA NA NA R/A I NA R I
Implementation NA NA R I I NA NA A
UAT I NA NA R/A NA NA NA C

Cont. to Next page

  Documents to Write –
a) Project vision Document
b) Business Analysis Plan – Stakeholder Analysis Document (RACI)
c) Business Requirements Document.
d) Functional requirement specification (FRS)/ Functional Specification Document (FSD)
e) System requirement specification (SRS)/ System Requirement Document (SRD)

 Signing off on the Documents – Once the above-mentioned documents are prepared, as a BA, I
will take the sign off on the above documents via Emails and Physical sign off as well from the
respective Stakeholders.
a) Project Vision Document – Email to – Project Sponsor and CC – Financial Head,
Project Coordinator and Project Manager.
b) Business Requirement Document – Project Sponsor (Email and Physical)
c) FRS/FSD & SRS/SRD – Email to - Project Sponsor and CC - Financial Head, Project
Coordinator and Project Manager.

 Taking Approvals – While taking approval for all the above documents, I will call the respective
Stakeholders and send them an Email with the details.

 Communication Channels to establish and implement – As a BA, I would prefer the below
communication channels:

a) Face to Face communication – for Requirement Gathering stage. For example,

Interviews with Stakeholders.
b) Video conferencing - This communication is also used when the Stakeholder is at a
different location.
c) Phone calls – This communication is used for setting up meetings with Stakeholders
and for taking approvals.
d) Emails - This communication is used for setting up meetings with Stakeholders and
for taking approvals.

 How to handle Change request -

As a BA I would handle the Change request by understanding the below steps.
(a) Understanding the Scope of Change.
(b) Determining the Scope of Incorporating the Change request.
(c) Understanding the Feasibility of the Change request.
(d) Taking the approval for the Change.
(e) Communicating and Implementing the Change.

 Updating the progress of the project – As a BA, before we update the Project status, we need
understand few key areas –
o Understand Stakeholder needs – We need to know the stakeholders who we are
working with. Stakeholders sometimes prefer to review the date
everyday/weekly/biweekly/monthly. Other stakeholders may like to only read
descriptive text.
o Proactively listen to your stakeholders’ concerns - Stakeholders may want to share
specific concerns with us in confidence and will rely on us to address potential
issues/risks. As a BA, we need to know how we provide status to our stakeholders. This
includes making sure that the project progress status reports or dashboards provide
enough detail. Finally, it should also address their concerns without having them ask
about it.
Cont. to Next page
 o Develop and execute a communication plan – Which means, we need to do Stakeholder
analysis, an analysis on stakeholders that provides details on who the stakeholder is and
the division are they aligned to. This analysis will contain details on how the project will
impact them and interest level of the stakeholders. The analysis will also contain details
on stakeholder’s ability to influence others, and their stance on the overall project.

Once we understand these key areas, we will now have to focus on sharing the project
status with the Stakeholders.

o Utilize online collaboration tools to share regular progress.

o Send out weekly or bi-weekly status reports.
o Develop a follow up meeting with actively involved Stakeholders.

 Signing off on the UAT- Client Project Acceptance Form -

Project Sign-off Sheet

Version Date: **/**/****
Project Name: Online Agriculture Product Store
Project Goals:
1. To provide online agriculture facility to farmers, to help farmer with online product store.
2. New application should be able to accept the product (fertilizers, seeds, pesticides) details from the
manufacturers and should be able to display them to the Farmers.
3. to build this online store is to facilitate farmers to buy seeds, pesticides, and fertilizers from anywhere
through internet connectivity.
Project Manager - Mr. Vandanam Sponsor - Mr. Henry
Start Date: 13th Feb 2023 Planned Budget: INR 2 Crores
Planned Completion Date: 14th Aug 2023 Actual Budget:
Actual Completion Date: Variance:
Variance:
Duration: 18 months
Days Past the Planned Completion Date: 14th Aug
2023
Project Deliverables:

By signing this document, I acknowledge that I have By signing this document, I acknowledge that I have
delivered all the stated deliverables at the agreed to received all the stated deliverables at the agreed to
quality levels. quality levels.

Project Manager Signature: Sponsor Signature:

Date: **/**/**** Date: **/**/****

Remarks:

23. 3-Tier Architecture

Three-tier architecture is a hierarchical software architecture with three distinct, independent tiers or layers.
Three-tier architecture is comprised of the following tiers: Presentation Tier (Client layer), Business (Business
Logic Layer) and Data access (Data layer). The main job of the architecture is to enable software applications
to efficiently and quickly respond to user requests or inputs.

Cont. to Next page

 Presentation Tier: This layer is also called Client layer and is responsible for accepting inputs or requests
from the user and displaying data for the user in a user-friendly format. It accepts inputs and sends the
inputs or request to the business logic layer.

Business Tier: This layer is also called Business Logic Layer and helps define solutions to complex business
problems. It acts as a middle layer between the client and the database server which are used to exchange
partially processed data.

Database layer: In this layer the data or information is stored. This layer performs operations like insert,
update and delete to connect with the database.

All user interface will be visible on the screen in the Client

layer, Ex: Application Name, Login username and
Presentation Layer password, Product list, New user registration, New arrivals
etc.
Reusable components or changing rules and regulations
Business Logic
are included in the Business Logic layer, Ex: GST, Multiple
Layer
payment options etc.
Storage place for all the information related to Products,
Database layer Client credentials etc. Ex: Product price, Quality, Quantity,
Client details etc.

24. BA Approach Strategy for Framing Questions

 5W1H – As a BA, the followings points should be kept in mind before framing questions to ask a
Stakeholder.
o What is the Project and what are the objectives?
o What is the Timeline for the project?
o Who is the Client and Who are the users?
o Who will benefit from this project?
o Where will the product be deployed?
o How much is the Budget?
o Why are the clients developing this product?

Cont. to Next page

  SMART - Confirm the requirement is SMART before accepting it for development.

o Specific - Narrowing the questions, so let every signal question only include one element you can
get.
o Measurable – The questions are better to be quantified and countable. Ex. Multiple Choice
questions.
o Action Oriented – Does the question influence creation of different or new feature packages.
o Relevant – Does the question identify which features are most required from the customer.
o Timebound - It can let you or your customer decide priority in a specific time frame.

 RACI Matrix
o Responsible – The person who does the work to achieve the task. They have responsibility for
getting the work done or decision made. The persons responsible are typically working-level
project team members, such as the project manager, business analyst and developers.
o Accountable – The person who is responsible for the correct and through completion of the task.
They are responsible for ensuring the work is complete and suitable.
o Consulted – People from whom feedback and input should be solicited. They are going to
provide information for the project and with whom there can be two-way communication.
o Informed – People kept informed of progress by keeping them in loop. These individuals do not
have to be consulted or be a part of the decision making.

 3 Tier Architecture
o Presentation layer - This layer display screens, pages, validation on page, company specific logic,
functionally.
o Business logic layer - In a business logic layer all reusable components, frequently changing
components, governing body rules, regulation, compliance.
o Data layer - In this layer the data or information is stored. This layer performs operations like
insert, update and delete to connect with the database.

 Use Cases
o What type of product we will deliver?
o Where is the location we will deliver the application?
o When should be the process be completed?
o Who all are responsible for doing this?
o Why this product will be used?
o How will we deliver this project?

 Use Case Specs

o Who are the Primary and Secondary actors?
o What are the Actor Goals?
o What are the main Tasks or functions that are performed by the Actor?
o What information does the actor desire from the system?

 Activity Diagrams – Activity diagrams are visual representations of a series of actions or flow of control in
a System similar to a Data flow diagram. It is basically a flowchart to represent the flow from one activity
to another activity. The activity can be described as an operation of the system.

Purpose of an activity diagram can be described as –

o Draw the activity flow of a system.
o Describe the sequence from one activity to another.
o Describe the parallel, branched, and concurrent flow of the system.

Cont. to Next page

  Models
o Conceptual Model
o Data Model
o Physical Model

25. Elicitation Techniques (BDRFOWJIPQU):

1. Brainstorming: This technique is used to generate new ideas and find a solution for a specific issue.
The members included for brainstorming can be domain experts, subject matter experts. Multiple
ideas and information give us a repository of knowledge and we can choose from different ideas.
2. Document Analysis: During this step of the requirements elicitation process, business analysts
review existing documentation at hand, with the intent of identifying requirements for changes or
improvements. Examples of document analysis sources include pre-existing project plans, system
specifications, process documentation, market research dossiers, customer feedback, meeting
minutes, and user manuals. Document analysis is performed before scheduling more in-depth
requirements elicitation sessions or interviews with stakeholders.
3. Reverse engineering: In this Technique, any outdated documentation in an existing system, can be
reversed to understand what the system does. his is an elicitation technique that can extract
implemented requirements from the system. There are two types of reverse engineering techniques.
i. Black box reverse engineering: The system is studied without examining its internal
structure (function and composition of software).
ii. White box reverse engineering: The inner workings of the system are studied (analyzing
and understanding of software code).
4. Focus Group: By using a focus group, you can get information about a product, service from a group.
The Focus group includes subject matter experts. The objective of this group is to discuss the topic
and provide information. A moderator manages this session.
5. Observations: Observation is an excellent elicitation technique that helps understand requirements
based on observations related to process flows and work environments of stakeholders. Observation
requires a business analyst to go and look at the work – for example, observing the business
processes in scope of the project. The elicitation technique observation is an effective means of
understanding how a user does their job by assessing their work environment.
6. Workshops: Workshops comprise a group of users or stakeholders working together to identify
requirements. A requirement workshop is a structured way to capture requirements. Workshops are
used to scope, discover, define, and prioritize requirements for the proposed system.
7. JAD (Joint Application Development): This technique is more process-oriented and formal as
compared to other techniques. These are structured meetings involving end-users, PMs, SMEs. This
is used to define, clarify, and complete requirements.
8. Interviews: An interview is a systematic approach to elicit information from a person or group of
people. This is the most common technique used for requirement elicitation. Interview techniques
should be used for building strong relationships between business analysts and stakeholders. In this
technique, the interviewer directs the question to stakeholders to obtain information. One to one
interview is the most commonly used technique.
9. Prototyping: Prototyping is used to identify missing or unspecified requirements. In this technique,
frequent demos are given to the client by creating the prototypes so that client can get an idea of
how the product will look like. Prototypes can be used to create a mock-up of sites, and describe the
process using diagrams.
10. Questionnaire & Surveys: For Survey/Questionnaire, a set of questions is given to stakeholders to
quantify their thoughts. After collecting the responses from stakeholders, data is analyzed to identify
the area of interest of stakeholders. Questions should be based on high priority risks. Questions

Cont. to Next page

 should be direct and unambiguous. Once the survey is ready, notify the participants and remind
them to participate.
11. Use case specs: Use cases are an effective and widely used technique for eliciting software
requirements. The use-case approach focuses on the goals that users have with a system, rather
than emphasizing system functionality. This technique combines text and pictures to provide a
better understanding of the requirements. The use cases describe the ‘what’, of a system and not
‘how’. Hence, they only give a functional view of the system. The components of the use case design
include three major things – Actor, Use cases, use case diagram.

26. This project Elicitation Techniques: For this Project, I would prefer to use the below Elicitation techniques.
 Brainstorming: By using this Technique, we can extract several ideas to make the Online store more useful
for farmers and other users. Once we have these ideas, we can analyze and select the best ideas to
implement. Brainstorming is effective with group of 8 to 12 people it helps to get the good number of ideas
from user and stakeholders.
 Prototype: Prototyping is a visual technique, where we can create a representation of any ideas and allow
us to test our ideas directly with the users before developing into a fully-fledged product. For this project, I
would draw down the idea in a paper and share it with the stakeholders. Being a completely new project in
the market, for which there are no details or documents available, I would use this technique to find the
feasibility of the project, before spending money on the project.
 Use case specs: This technique is a combination of text and pictures which will provide me a better
understanding of the requirements. This technique shows the behavior of the system and help to capture
the requirement of the system. These diagrams also identify the interactions between the system and its
actors.

27. 10 Business Requirements

Identify Business Requirements (which includes Stakeholder Requirements)

 BR001 – Farmers should be able to search for available products in fertilizers, seeds, pesticides.
 BR002 – Manufacturers should be able to upload and display their products.
 BR003 – All users should have Login details with Username and Password.
 BR004 - Once the user’s login to the portal, they should also update their address details, to make sure the
delivery happens to their requested address only.
 BR005 - A fresh user should be able to create a new account by submitting their email ID and creating a
secure password.
 BR006 – Users should be able to browse through the Product catalogues once they visit the website.
 BR007 – User should have the Buy Now option if they want to purchase the product immediately.
 BR008 - Users can have a Save for Later or Wishlist option, if they want to buy any product later.
 BR009 – Farmers needs to have an easy-to-use payment gateway which should include cash-on delivery
(COD), Credit/Debit card and UPI options so that the user’s experience should be better.
 BR010 – User should get an email confirmation regarding their order status.
 BR011 – Users should be able to track their order, once placed.
 BR012 – User should be able to cancel or return the product, if not happy with it.
 BR013 – Users should have an option to rate the Product, Delivery and Overall experience.

28. Assumptions:
 Users should either have Laptop or Desktop or Mobile.
 They should have an active Email address.
 They should have an active Bank account with active payment modes, like Credit/Debit card, UPI
payments or mobile banking facility etc.

Cont. to Next page

  They also should have an active registered mobile number to receive OTPs to pay for the product
and accept delivery.
 Does the application have price comparison option for multiple products.
 How much competitive the price of the products is going to be.
 The application should have the Product stock notification.
 The application should have Chat facility to speak to any customer service querying for any product,
they want to buy.
 The application should have a delivery tracking facility.

29. This project Requirements Priority

Req.
Requirement Name Requirement Description Priority
ID

Farmer Search for

BR001 Farmers should be able to search for available products in fertilizers, seeds, pesticides 8
Products

Manufacturers
BR002 Manufacturers should be able to upload and display their products. 8
upload their Products

Username &
BR003 All users should have Login details with Username and Password 9
Password

Once the user’s login to the portal, they should also update their address details, to make
BR004 User Details 9
sure the delivery happens to their requested address only.

A fresh user should be able to create a new account by submitting their email ID and
BR005 User Details 8
creating a secure password.

Browsing through Users should be able to browse through the Product catalogues once they visit the
BR006 7
Product catalogues website.

BR007 Purchase Options User should have the Buy Now option if they want to purchase the product immediately. 6

BR008 Wishlist Users can have a Save for Later or Wishlist option, if they want to buy any product later. 6

Farmers needs to have an easy-to-use payment gateway which should include cash-on
BR009 Payment Gateway delivery (COD), Credit/Debit card and UPI options so that the user’s experience should be 9
better.

BR010 Notifications User should get an email confirmation regarding their order status. 7

BR011 Order Tracking Users should be able to track their order, once placed. 7

BR012 Cancel/Return User should be able to cancel or return the product, if not happy with it. 9

BR013 Feedback Users should have an option to rate the Product, Delivery and Overall experience. 7

Cont. to Next page

 30. Use Case Diagram

31. (Minimum 5) Use Case Specs:

 Use case spec – User buying fertilizers.

USE CASE SPEC – BUYING FERTILIZER

Document Title Buying fertilizers from an Online Agriculture Store.
Document Owner Sourabh Bhattacharya
Version
Status In Progress
Date 7th Mar 2023

Cont. to Next page

 This Use case explains how a Farmer uses the Online Agriculture Product Store to buy
BRIEF DESCRIPTION
Fertilizers.
1. Farmers
ACTORS
2. Database/Admin
• There should be an active Internet connection.
Pre-Conditions
• Farmer should have Laptop/Mobile.

• Use case Begins with User logs in.

• User validation is performed.
• Customer begins to search for the Agriculture Product.
• Application displays multiple products for the Searched product.
Basic Flow • User selects the product and add it to cart.
• User selects the Delivery location for product delivery.
• User selects the Payment mode to pay.
• Order placed and user receives an SMS for Order confirmation.
• Use case Ends successfully.

• Invalid User – This happens when the user validation fails.

App display message: User validation not completed Successfully. Use case ends with
failure condition.
• Product Out of Stock – If the user selects the product which is out of stock.
App display message: Product out of stock. Select from similar product available.
• Product Out of Stock for selected location: If the product is not available for the
Alternate Flow
Selected location.
App display message: Product out of stock for selected location. Please try after few days
when the product is available / Try selecting from similar products.
• No response from Payment server: While making payment, if the server disconnects or
there is no response from the server.
• Use Case Ends

• Successful Completion – User bought the fertilizer successfully.

Post Conditions • Failure Condition – User couldn’t purchase the product due to some Technical/Financial
reason

• The price of all the agriculture product should be as per the Govt. policy.
SUPPLEMENTAL REQUIREMENTS
• The application shall keep a usage detail of all complete and incomplete transactions.

 Use case spec – User registering in the application.

USE CASE SPEC – User Registration

Document Title User Registering with User details
Document Owner Sourabh Bhattacharya
Version
Status In Progress
Date 7th Mar 2023

BRIEF DESCRIPTION This Use case describes, how a user registers himself in an Online Agriculture Store

• Farmer
ACTORS
• Admin

Cont. to Next page

 • There should be an active Internet connection.
• Farmer should have Laptop/Mobile.
Pre-Conditions
• The user should have active Email address.
• The user should have active mobile number.

Use case Begins – When a new user starts register himself with the user details.
1. User enters user details: Name, Address, Mobile number, and Email ID.
2. Application displays option to send OTP to mobile for mobile verification.
3. User sends OTP to the mobile number.
Basic Flow 4. User enters OTP received.
5. Application displays OTP verified.
6. User validation performed.
7. Application displays User created successfully.
Use case Ends.

1. Invalid OTP: If the user enters the incorrect OTP.

Display Msg: Please enter the correct OTP.
2. Mobile number already used: In this case, if the user enters the mobile number which
is already in use, which means that the user is already a registered user.
Display Msg: Mobile number is already in use. Please enter the correct mobile number.
3. Email address is already used: If the user enters the email address which is already
Alternate Flow used to register, which means that the user has already a registered user.
Display Msg: Email address is already in use. Please enter the correct Email address.
4. User ID not available: If the user enters the User ID which is already used, then the
application gives the below message.
Display Msg: User ID already used. Please enter another user id.
5. Server issue: If the user not able to create the user id, when the server breakdown.
Display Msg: Server busy. Please try again later.

• Successful completion: The user id has been successfully created.

Post Conditions
• The details updated in the log accordingly.

• The application shall keep a log, Including date and time, of all complete and
SUPPLEMENTAL REQUIREMENTS
incomplete transactions.

 Use case spec – User making payment for the order placed.

USE CASE SPEC – Processing Payment

Document Title Payment process for the purchased product
Document Owner Sourabh Bhattacharya
Version
Status In Progress
Date 8th Mar 2023

This use case describes, how the user goes through a Payment process after the product
BRIEF DESCRIPTION
selection

• Farmer
ACTORS • Admin
• Bank

Cont. to Next page

 • There should be an active Internet connection.
• Farmer should have Laptop/Mobile.
Pre-Conditions
• User should have an active Bank account.
• User should have active mobile number to receive the Bank OTP.

Use case Begins – when the user initiates the payment after the selection of the product.
1. User validation performed.
2. Application displays multiple options to Pay by Credit card, Debit card, Net Banking,
and UPI.
Basic Flow 3. User has option to pay by Credit card, Debit card, Net Banking, UPI
4. User selects the Payment mode and fill the details.
5. Application displays Payment completed.
6. User receives email and SMS with the Order completion.
Use case Ends

1. Incorrect Card details: If the user enters incorrect Card details. User receives SMS from
Bank about Payment failure due to incorrect card details entered.
Display Msg: Payment not completed.
2. Incorrect OTP: If the user enters incorrect OTP.
Display Msg: Payment declined. Incorrect OTP entered.
Alternate Flow
3. Insufficient Funds: Payment got declined due to insufficient funds.
Display Msg: Payment declined. User receive SMS from Bank confirming the Payment
declined due to insufficient funds.
4. Server Busy: Payment didn’t complete due to Server busy.
Display Msg: Payment not completed. Server Busy. Please try again

Post Conditions • Successful Completion: Payment is completed, and the Order is placed successfully

• The application shall keep a log, Including date and time, of all complete and
SUPPLEMENTAL REQUIREMENTS
incomplete transactions

 Use case spec – Seller adding and updating the products in the portal.

USE CASE SPEC – Seller Adding/Updating Products

Document Title Seller Adding/Updating Products
Document Owner Sourabh Bhattacharya
Version
Status In Progress
Date 8th Mar 2023

BRIEF DESCRIPTION • This Use case describes how a Seller/Manufacturer adds this product on the portal.

• Seller / Manufacturer
ACTORS
• Database/Admin

• There should be an active Internet connection.

Pre-Conditions
• Seller should have Laptop/Mobile

Cont. to Next page

 Use case Begins – When the Seller wants to Add/update any New Agricultural product
at Agricultural Product store.
1. Seller selects the Sale option before Login.
2. User validation performed.
3. Application displays different Product selling alternatives. In this case the Seller
selects Agricultural product option.
Basic Flow
4. Seller chooses product categories.
5. The Seller enters product details i.e., Product Name, Type of the product, Price and
Offers on product and Approximate Delivery date.
6. Application displays the new Product detail updated successfully.
7. Seller also receives a receipt by SMS or email.
Use case Ends.

• Region wise product price display to customer: Seller tries to update the Price as
per the region, however the application throws an error.
Alternate Flow Display Msg: Price not matching as per the region. Please enter the correct price.
• Incorrect product categories: Seller selects the wrong product category.
Display Msg: Incorrect Product category. Please select the correct category

Post Conditions • Successful completion - The product has been successfully updated

• The application shall keep a log, Including date and time, of all complete and
SUPPLEMENTAL REQUIREMENTS
incomplete transactions with the admin

 Use case spec – User cancelling the product.

USE CASE SPEC – Product cancellation/Return/Refund

Document Title Product cancellation/Return/Refund
Document Owner Sourabh Bhattacharya
Version
Status In Progress
Date 8th Mar 2023

• This use case describes how user cancel/return the product at online agricultural
BRIEF DESCRIPTION
product store

• Farmer
ACTORS • Database/Admin
• Seller

• There should be an active Internet connection.

Pre-Conditions
• Seller should have Laptop/Mobile.

Cont. to Next page

 Use case Begins – When the User wants to cancel/return agriculture product at
agricultural product store.
1. User validation performed.
2. Application displays multiple order, which has already been placed.
3. User selects the Order/Product for cancellation/return.
4. Application displays Reason for cancellation/return.
5. User provides reason for cancellation/return.
Basic Flow
6. Application displays Product cancellation/return requested. Product will be
picked up at certain time and date.
7. Seller receives message or product cancellation/return.
8. Seller arranges the product pick up.
9. Admin issues Refund to User.
10. User receives the Refund.
Use case Ends.

• Cancel Period over: Application displays this message when the user tried to
Alternate Flow cancel after the cancellation/return period is over.
Display Msg: Product cannot be returned.

• Successful cancellation/Return: The product has been successfully cancelled and

Post Conditions the internal logs have been updated.
• Refund Initiated: Refund has been initiated.

• The application shall keep a log, Including date and time, of all complete and
SUPPLEMENTAL REQUIREMENTS
incomplete transactions with the admin

32. (Minimum 5) Activity Diagrams

1. Login Page

Cont. to Next page

  Registration Page

Cont. to Next page

  Buying fertilizer

Cont. to Next page

  Order Cancellation

 Adding or Updating product

Cont. to Next page

 33. Functional Requirements

Req ID Req Name Req Description Priority

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

Farmer should be able to search for available products in

FR0002 Farmer Search for Products 8
fertilizers, seeds, pesticides

FR0003 No matching Product Farmer should be notified if the searched product not found 5

FR0004 Product Selection Farmer should be able to select the product 7

FR0005 Out of Stock Farmer should be notified, if the product is out of stock 7
Farmer should be able to filter and select the product as per
FR0006 Filter 7
Brands and Price
Farmer should be able to select similar products, if the searched
FR0007 Similar products 6
product is out of stock
Once the product is finalized, farmer should be suggested with
FR0008 Bought together 6
related products as a package with the price
Farmer should be able to Add the product to the Cart for
FR0009 Add to Cart 8
purchase

FR0010 Wishlist Farmer should have an option to Add the product into Wishlist 6

Farmer should be able to see the option for Save it Later, to

FR0011 Save it Later 7
purchase later
Farmer should be able to select the Delivery address to deliver
FR0012 Delivery Address 8
the product

Once the delivery address is selected, Application should show

FR0013 Payment options 8
the Payment options to the Farmer for purchasing the product.

FR0014 Payment Confirmation Farmer should receive the Payment confirmation email and SMS 10

FR0015 Order Confirmation Farmer should receive the Order confirmation email and SMS 9
Farmer should also see the Expected Delivery date of the
FR0016 Expected Delivery date 9
product.
Farmer should have the option to Track the delivery on the
FR0017 Track Delivery 8
application
Farmer should be able to Cancel/Return/Replacement the
FR0018 Cancel/Return/Replacement 9
product

FR0019 Return Pick up Farmer should be given Pick up date and time for cancel/return 7

Farmer should receive SMS and Email confirmation for

FR0020 Return Confirmation 7
cancellation/return
Req ID Req Name Req Description Priority
NFR001 Page Loading Time Each Page should load within 2 seconds time 9

Cont. to Next page

 Technical
NFR002 Application can be used on any OS (Android/IOS) 9
supported system
OTP time limit should be given maximum of 5 minutes for Login
NFR003 Time limit for OTP 4
and Registration process
If the page is not accessed for more for 5 minutes, the page
NFR004 Logout System 4
should log out automatically.
NFR005 Stock Availability Stock availability should be updated on a real time basis 8
SMS & Mail
NFR006 Automated Email and SMS notification should be sent to Users 8
confirmation
NFR007 Back up All data should get backup automatically 9
NFR008 Connectivity System should be connected with Internet 10
Seller should receive Stock alert notifications when Stock is
NFR009 Stock alerts 8
reduced, every week.
Bank account should be active in nature for smooth payment
NFR010 Net Banking 9
process
Once the Product is sold, the stock of the product should be
NFR011 Check Stock 7
reduced.

NFR012 Email Address Email Address should be a active to receive Email notifications 3

NFR013 Taxation system All products should be included with additional Tax 8
NFR014 Password User should receive Password change alert every 30 day 5

Cont. to Next page

 34. Minimum 5-page designs – Wireframes and Prototype

https://app.moqups.com/J10njjMkjTk3I7jmKbUoj4DbO54t2kby/view/page/a3afcac31

35. Tools (Visio, Balsamiq)

 Microsoft Office Visio

Microsoft Visio is a diagramming and vector graphics application and is part of the Microsoft Office
family. It is used to create diagram types such as Flowcharts, Org Charts, Floor Plans, Network
Diagrams, UML Diagrams, Mind maps and more. It is also commonly used for scenarios such as
Process Mapping and Visual Collaboration. The latest version of Visio also has data visualization that
allows users to create diagrams from Excel data and also embed Visio diagrams in Power BI
dashboards.
Microsoft Office Visio is a tool that eases the process of making complex diagrams. Especially for
business purposes. It can help in the making of presentations, floor plans, org charts, etc. Listed
below are some uses of Visio:
Followings things can draw BA by using MS Office Visio.

o Flowchart: A flowchart is helps to show the steps in sequential order. These are steps that
need to be taken to complete a certain process. It is effective in conveying information.
Thus, it can be used in various other fields too
Cont. to Next page
 o Organization Chart: An org chart displays the roles and reporting relationships in a business
organization. It can be used in also any other organization. It depicts the names and
positions of employees in a company. In short, we can say it shows the structure of an
organization.
o Floor Plan: A floor plan is the structure of a room or a floor. Architects use floor plans to
place doors, windows, and other objects. Visio also offers a floor plan template.
o Business Process Modelling Notation: BPMN is a flowchart method of displaying all the
processes in a business that is to be taken. In other words, it is helps in give a clear
understanding of the processes in a particular business through visual representation.

 Balsamiq
Balsamiq Mockups is an effective tool for presenting the software requirements in the form of
wireframes. This helps the software development team to visualize how the software project will
look like in the very early stages of development. This is a small tutorial where we will cover all the
basic steps needed to start with Balsamiq Mockups.

36. RTM

Req ID Req Name Req Description Design D1 T1 D2 T2 D3 T3 D4 T4 UAT

Farmer should be able to
FR0001 Farmer Registration Y Y Y Y Y Y Y Y Y N
register with the application
Farmer should be able to
search for available
FR0002 Farmer Search for Products Y Y Y Y Y Y Y Y Y N
products in fertilizers, seeds,
pesticides
Farmer should be notified if
FR0003 No matching Product the searched product not Y Y Y Y Y Y Y N N N
found
Farmer should be able to
FR0004 Product Selection Y Y Y Y Y Y N N N N
select the product
Farmer should be notified, if
FR0005 Out of Stock Y Y Y N N N N N N N
the product is out of stock
Farmer should be able to
FR0006 Filter filter and select the product Y Y Y N N N N N N N
as per Brands and Price
Farmer should be able to
select similar products, if
FR0007 Similar products Y Y Y N N N N N N N
the searched product is out
of stock
Once the product is
finalized, farmer should be
FR0008 Bought together suggested with related Y Y Y Y Y N N N N N
products as a package with
the price
Farmer should be able to
FR0009 Add to Cart Add the product to the Cart Y Y Y Y N N N N N N
for purchase
Farmer should have an
FR0010 Wishlist option to Add the product Y Y Y N N N N N N N
into Wishlist
Farmer should be able to
FR0011 Save it Later see the option for Save it Y Y Y N N N N N N N
Later, to purchase later
Farmer should be able to
FR0012 Delivery Address select the Delivery address Y Y Y N N N N N N N
to deliver the product

Cont. to Next page

 Once the delivery address is
selected, Application should
FR0013 Payment options show the Payment options Y Y Y N N N N N N N
to the Farmer for
purchasing the product.
Farmer should receive the
FR0014 Payment Confirmation Payment confirmation email Y Y Y Y Y N N N N N
and SMS
Farmer should receive the
FR0015 Order Confirmation Order confirmation email Y Y Y N N N N N N N
and SMS
Farmer should also see the
FR0016 Expected Delivery date Expected Delivery date of Y Y Y N N N N N N N
the product.
Farmer should have the
FR0017 Track Delivery option to Track the delivery Y Y Y N N N N N N N
on the application
Farmer should be able to
FR0018 Cancel/Return/Replacement Cancel/Return/Replacement Y Y Y Y Y N N N N N
the product
Farmer should be given Pick
FR0019 Return Pick up up date and time for Y Y Y N N N N N N N
cancel/return
Farmer should receive SMS
FR0020 Return Confirmation and Email confirmation for Y Y Y N N N N N N N
cancellation/return

Req ID Req Name Req Description Design D1 T1 D2 T2 D3 T3 D4 T4 UAT

Page Loading Each Page should load within 2 seconds
NFR001 Y Y Y Y Y Y Y Y Y N
Time time
Technical
Application can be used on any OS
NFR002 supported Y Y Y Y Y N N N N N
(Android/IOS)
system
OTP time limit should be given maximum
Time limit for
NFR003 of 5 minutes for Login and Registration Y Y Y N N N N N N N
OTP
process
If the page is not accessed for more for 5
Logout
NFR004 minutes, the page should log out Y Y Y N N N N N N N
System
automatically.
Stock Stock availability should be updated on a
NFR005 Y Y Y N N N N N N N
Availability real time basis
SMS & Mail Automated Email and SMS notification
NFR006 Y Y Y Y Y N N N N N
confirmation should be sent to Users
NFR007 Back up All data should get backup automatically Y Y Y Y N N N N N N

System should be connected with

NFR008 Connectivity Y Y Y Y Y N N N N N
Internet
Seller should receive Stock alert
NFR009 Stock alerts notifications when Stock is reduced, Y Y Y N N N N N N N
every week.
Bank account should be active in nature
NFR010 Net Banking Y Y Y N N N N N N N
for smooth payment process
Once the Product is sold, the stock of the
NFR011 Check Stock Y Y Y Y Y N N N N N
product should be reduced.
Email Email Address should be a active to
NFR012 Y Y Y N N N N N N N
Address receive Email notifications

Cont. to Next page

 Taxation All products should be included with
NFR013 Y Y Y N N N N N N N
system additional Tax
User should receive Password change
NFR014 Password Y Y Y N N N N N N N
alert every 30 day

37. 10 Test Case Documents

i) Test Case for User Login details

Online
Agriculture Test Sourabh
Project Name:
product Designed by: Bhattacharya
store
Test
Module Login with 15th Mar
Designed
Name: User details 2023
date:
Release Test Sourabh
Version: Executed by: Bhattacharya
Test
15th Mar
Execution
2023
date:

User need a valid User name and Password

Pre-condition
for Login to the Online store
Dependencies: User should have an active internet
Test Priority

Expected Post-
Test Scenario Test Case Test Steps Test Data Actual Result Status
Result condition
Enter <valid
Entered
Verify the Username Username>
valid
login of Online Enter <valid Successful Home Successfully
Username Pass
agriculture Password password> Login Page Logged in
and valid
product store Click Login
Password
button
Enter <valid The
Username Username> Username or
Entered
Verify the Enter <invalid Pwd is not Invalid Pop up
valid
login of Online Password password> correct. Username banner shows
Username Fail
agriculture Please enter or "Invalid
and Invalid
product store Click Login correct Password Password"
Password
button Username or
Pwd

Cont. to Next page

 Enter <invalid The
Username Username> Username or
Entered
Verify the Enter <valid Pwd is not Invalid Pop up
Invalid
login of Online Password password> correct. Username banner shows
Username Fail
agriculture Please enter or "Invalid
and valid
product store Click Login correct Password Password"
Password
button Username or
Pwd
Enter <invalid The
Username Username> Username or
Entered
Verify the Enter <invalid Pwd is not Invalid Pop up
Invalid
login of Online Password password> correct. Username banner shows
Username Fail
agriculture Please enter or "Invalid User
and Invalid
product store Click Login correct Password details"
Password
button Username or
Pwd

ii) Test Cases for Cash on Delivery/Pay on Delivery

Online
Agriculture Sourabh
Project Name: Test Designed by:
product Bhattacharya
store
Cash On
Module Test Designed
Delivery/Pay 15th Mar 2023
Name: date:
on Delivery
Release Sourabh
Test Executed by:
Version: Bhattacharya
Test Execution
15th Mar 2023
date:

User should have a Bank account for any Payment

Pre-condition
Gateway to select
Dependencies: User should have an active internet
Test Priority

Post- Actual
Test Scenario Test Case Test Steps Test Data Expected Result Status
condition Result
Verify the Select COD <Cash,UPI,
Home Order
availability of payment COD Cards also Order Placed Pass
Page Placed
COD gateway accepted>

Verify the <COD available

COD Not Choose another Payment COD Not
availability of COD Not available on Selected Fail
Available payment method Page Available
COD Items>

iii) Test Cases for Debit card

Cont. to Next page

 Online Agriculture Test Designed Sourabh
Project Name:
product store by: Bhattacharya
Module Test Designed
Using Debit Card 15th Mar 2023
Name: date:
Release Test Executed Sourabh
Version: by: Bhattacharya
Test Execution
15th Mar 2023
date:

User should have a Debit card and Bank account for this
Pre-condition
Payment Method
Dependencies: User should have an active internet
Test Priority

Expected Post- Actual

Test Scenario Test Case Test Steps Test Data Status
Result condition Result
Enter Card <valid card
Verifying the Number number>
selection of Enter Expiry Order
Entered Card Details <valid expiry> Payment Order
Debit card as Date Placed Pass
and OTP correctly Successful Page
Payment Enter CVV Successfully
Method
Enter OTP <valid OTP>
Enter Card <valid card
Verifying the Number number> Enter
selection of Entered Card number Enter Expiry <Incorrect Expiry Incorrect Enter
Correct
Debit card as correctly, but Date Date> Expiry correct Fail
Expiry
Payment Incorrect Expiry date Enter CVV Date Expiry date
date
Method
Enter OTP
Enter Card <valid card
Verifying the Number number>
selection of Entered Card details Enter Expiry Enter Incorrect
<valid expiry> Enter
Debit card as correctly, but Date correct OTP Fail
correct OTP
Payment incorrect OTP Enter CVV OTP entered
Method
Enter OTP <Incorrect OTP>

iv) Test Cases for Credit card

Online Agriculture Test Designed Sourabh

Project Name:
product store by: Bhattacharya
Test Designed
Module Name: Using Credit card 15th Mar 2023
date:
Release Test Executed Sourabh
Version: by: Bhattacharya
Test Execution
15th Mar 2023
date:

User should have a Credit card and Bank account for this
Pre-condition
Payment Method
Dependencies: User should have an active internet
Test Priority

Expected Post- Actual

Test Scenario Test Case Test Steps Test Data Status
Result condition Result

Cont. to Next page

 Enter Card <valid card
Verifying the Number number>
selection of Entered Card Enter Expiry Order
<valid expiry> Payment
Credit card as Details and OTP Date Order Page Placed Pass
Successful
Payment correctly Enter CVV Successfully
Method
Enter OTP <valid OTP>
Enter Card <valid card
Verifying the Number number>
Entered Card
selection of Enter Expiry <Incorrect Expiry Enter Incorrect Enter
number correctly,
Credit card as Date Date> correct Expiry correct Fail
but Incorrect Expiry
Payment Enter CVV Expiry date Date Expiry date
date
Method
Enter OTP
Enter Card <valid card
Verifying the Number number>
selection of Entered Card Enter Expiry Incorrect
<valid expiry> Enter Enter
Credit card as details correctly, Date OTP Fail
correct OTP correct OTP
Payment but incorrect OTP Enter CVV entered
Method
Enter OTP <Incorrect OTP>

v) Test Cases for Product Availability for selected address

Online
Test Sourabh
Project Name: Agriculture
Designed by: Bhattacharya
product store
Product
Test
Module Availability 15th Mar
Designed
Name: for selected 2023
date:
address
Release Test Sourabh
Version: Executed by: Bhattacharya
Test
15th Mar
Execution
2023
date:

User should have a valid Postal address wth

Pre-condition
postal code
Dependencies: User should have an active internet
Test Priority

Expected Post-
Test Scenario Test Case Test Steps Test Data Actual Result Status
Result condition
Verify the Page accepts
Entered valid Product is
product the Postal
Postal code to Enter Postal <Postal Code available to Product
delivery on the code for Pass
check the Code available> this Postal Page
selected Postal product
Delivery code
code selection
Pop up banner
Verify the Entered
Product is not shows
product incorrect
Enter Postal <Currently available in Product "Currently Out
delivery on the Postal code to Fail
Code Out of Stock> this postal Page of Stock for
selected Postal check the
code this Postal
code Delivery
code"

Cont. to Next page

 vi) Test Cases for Product Availability for selected address

Online Test Sourabh

Project Name: Agriculture Designed Bhattachary
product store by: a
Product Test
15th Mar
Module Name: Cancellation/Re Designed
2023
turn date:
Test Sourabh
Release
Executed Bhattachary
Version:
by: a
Test
15th Mar
Execution
2023
date:

Pre-condition User should have valid Order processed

Dependencies: User should have an active internet

Test Priority

Expected Post- Stat

Test Scenario Test Case Test Steps Test Data Actual Result
Result condition us
Select <Cancel/Ret
Cancel/Ret urn
urn selected>
Select the
Testing the Enter <Cancel
Product for Product Product Product
product Cancel/Ret Reason
cancellation/Ret cancellation/ret Cancellati cancellation/retu Pass
cancellation/Ret urn Reason Selected>
urn within the urn successful on page rn successful
urn
Return period
<Pick up
Select Pick
address
up address
selected>

Select the Product is not

Pop up banner
Testing the Product for available for
Select <Cancellatio shows
product cancellation/Ret cancellation as Order
Cancel/Ret n Not "Cancellation/Re Fail
cancellation/Ret urn out of its out of Page
urn available> turn not
urn cancellation/ cancellation
available"
Return period period

vii) Test Cases for Shopping Cart

Test
Online Agriculture Sourabh
Project Name: Designed
product store Bhattacharya
by:

Cont. to Next page

 Test
15th Mar
Module Name: Shopping Cart Designed
2023
date:
Test
Sourabh
Release Version: Executed
Bhattacharya
by:
Test
15th Mar
Execution
2023
date:

Pre-condition User should be a Registered customer

Dependencies: User should have an active internet
Test Priority

Expected Post- Actual

Test Scenario Test Case Test Steps Test Data Status
Result condition Result
Items
Test that all items Selected Items are Selected
Select Add <Item Added Items in added to
are added into added in Cart Items in Pass
to Cart to Cart> Cart page cart
the cart successfully Cart
successfully
Test that the user <Item Item
Select Item Items
is able to Item Quantity is Quantity Quantity is
Quantity Items in added to
increase/decrease increased/decreased selected> selected Pass
Cart page cart
quantity from the successfully Select Add <Item Added and added
successfully
cart to Cart to Cart> to cart

viii) Test Cases for Applying Coupon code.

Online
Test Sourabh
Project Name: Agriculture
Designed by: Bhattacharya
product store
Test
Module Applying
Designed 15th Mar 2023
Name: Coupons
date:
Release Test Sourabh
Version: Executed by: Bhattacharya
Test
Execution 15th Mar 2023
date:

Pre-condition User should be a Registered customer

Dependencies: User should have an active internet
Test Priority

Expected Post- Actual

Test Scenario Test Case Test Steps Test Data Status
Result condition Result
Banner
Test that User Entering the Coupon code
show
should be able correct Coupon Apply <coupon code accepted and Checkout
"Coupon Pass
to add code in Coupon code accepted> Price adjusted page
code
coupons Checkout page accordingly
applied"

Cont. to Next page

 Banner
Entering the shows "
Test that User
incorrect Coupon
should be able Apply <Coupon code Coupon code Checkout
Coupon code code already Fail
to add Coupon code already used> not accepted. page
in Checkout used. Enter
coupons
page new coupon
code

ix) Test Cases for Seller Adding Product within Limit

Online
Test Designed Sourabh
Project Name: Agriculture
by: Bhattacharya
product store
Seller Adding Test Designed
Module Name: 15th Mar 2023
Product date:
Release Test Executed Sourabh
Version: by: Bhattacharya
Test Execution
15th Mar 2023
date:

Pre-condition Seller should be a registered seller

Dependencies: User should have an active internet
Test Priority

Expected Post- Actual

Test Scenario Test Case Test Steps Test Data Status
Result condition Result

Upload <Product Image

Product Image uploaded> Banner
Test the
Seller adding shows "
maximum Product added
product within Enter Product <Product Name Home Page Product Pass
product adding Successfully
limit Name updated> added
limit
Successfully"
Update <Product Price
Product Price updated>
Upload <Product Image Banner
Product Image uploaded> shows "
Test the Duplicate
Seller adding <Duplicate Product
maximum Enter Product Product
product over Product Home Page already Fail
product adding Name already
the limit available> available.
limit available
Update Upload New
Product Price Product"

x) Test Cases for Product Search

Online
Test Designed Sourabh
Project Name: Agriculture
by: Bhattacharya
product store
Module Searching Test Designed
15th Mar 2023
Name: Product date:
Release Test Executed Sourabh
Version: by: Bhattacharya
Test Execution
15th Mar 2023
date:

Cont. to Next page

 Pre-condition User should have Online application installed
Dependencies: User should have an active internet
Test Priority

Expected Post- Actual

Test Scenario Test Case Test Steps Test Data Status
Result condition Result
Banner
Test if the user Enter the name
Product shows "
is able to of the Product Enter Product <Product lists Product Lists
Search Searched Pass
Search the user want to name up per search> up successfully
page Item
Product Search
Listed"
Enter the name Banner
Test if the user
of the Product <Product Product Product shows "
is able to Enter Product
user want to Searched Not searched Not Search Searched Fail
Search the name
Search which is Available> successful page Item Not
Product
not available Available"

Cont. to Next page

 38. DB Design & ER Diagram

1. DB Diagram

https://lucid.app/lucidchart/b87736fa-281b-401d-90c6-5fd2415abd07/edit?invitationId=inv_a0eb0799-
3603-4585-954e-edeb7f3fc5c9&page=0_0#

Cont. to Next page

  ER Diagram

39. Data Flow Diagram

Cont. to Next page

 40. Change Request

What is a Change request - Change requests are when a stakeholder, either a client or an internal team or
department, requests a change to the processes or deliverables that had already been decided upon in the
project scope.
However, in this scenario, this change request has come up due to change in the Govt. Taxation structure. As
a BA, I would analyze the request and clarify the stakeholders exactly what the request is asking us to do in
the Online Agriculture Product Store. In a normal scenario, as a BA, I would first do the Feasibility Test, to
check, how feasible it is to change the current ongoing project with the new change request.
However, in this case, Feasibility study is not required, as it’s a Govt structure which needs to be updated
and followed. Therefore, I will follow the below steps to change the project as per the client’s requirements.

 Document the Change request.

 Look for any Supporting materials to help in adding this Change.
 Need to assess, whether the Change is an Inside or Outside scope. As its an outside scope, the
Budget and time will get impacted.
 BA and PM should ensure whether the change is a minor or a major change. Policy changes by Govt
is a major change request and we need to ensure that the change should be done according to the
Govt. instruction.
 Fill the Change request Form and get the approval from the Project Manager.
 We also need to ensure that our Team understands the priority of this change request.
 We also need to discuss the change with Change Control Board who will recommend the necessary
change on the Project.
 Once this change is approved, the project deliverables will need to be updated. This can include
plans and schedules, business process documents, and the requirements documents.
 Once these updates have been made, the project manager can communicate the new course of
action to everyone who will be impacted. Now you can delegate the necessary tasks to the people in
charge of implementing these new changes.

Cont. to Next page

 41. Change Request Vs an Enhancement
The request from Ben and Kevin is an Enhancement request, as they want to add another feature in the
Online store, which will also help the Farmers to sell the yields directly in the online store, apart from buying
products. Hence my response would a positive response to them.
Therefore as a BA, I should analyze the request and provide a project plan, requirement, design, an testing
plans for this request. I must prepare an enhancement request form and decide how much manpower and
manhours required for this enhancement request.

42. Estimations - Manhours required.

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

547-166 = 381 working days

Hence, Estimated Manhours = 8 hours * 12 resources * 381 days = 36,576 hours required.

43. UAT

User Acceptance Testing (UAT) is a phase in the software development life cycle where the users of the
Online Agriculture Product Store participate in validating that if meets their needs.
As a BA, I will verify all the validations prior to design the UAT Test cases, which will cover the functionality of
the product, System environment, any possible defects which could arise and how to deal with these
defects.

Steps for UAT

 Analysis of Business Requirements: One of the most important activities in the UAT is to identify
and develop test scenarios. These test scenarios are derived from the following documents:
(a) Business Use Cases
(b) Process Flow Diagrams
(c) Business Requirements Document (BRD)
(d) System Requirements Specification (SRS)

 Creation of UAT Plan: The UAT test plan outlines the strategy that will be used to verify and ensure
an application meets its business requirements. It documents entry and exit criteria for UAT, Test
scenarios and test cases approach and timelines of testing.
 Identify Test Scenarios and Test Cases: Identify the test scenarios with respect to high-level business
process and create test cases with clear test steps. Test Cases should sufficiently cover most of the
UAT scenarios. Business Use cases are input for creating the test cases.
 Preparation of Test Data: It is best advised to use live data for UAT. Data should be scrambled for
privacy and security reasons. Tester should be familiar with the database flow.
 Run and record the results: Execute test cases and report bugs if any. Re-test bugs once fixed. Test
Management tools can be used for execution.
Cont. to Next page
  Confirm Business Objectives met: Business Analysts or UAT Testers needs to send a sign off mail
after the UAT testing. After sign-off, the product is good to go for production. Deliverables for UAT
testing are Test Plan, UAT Scenarios and Test Cases, Test Results and Defect Log.

44. Project Closure Document

Project Closure
Online Agriculture Product Store
Version: 1.0

Revision Date: MM/DD/YYYY

Submit the document to the Project Sponsor, Business Owner, and PPMO/PMO Division Director; and archive this closure
document with the project artifacts once completed.
Approver Name Title/Role Signature Date

Peter and Ben Project Stakeholder * Ok xx/xx/xxxx

Mr. Henry Exec Sponsor (AVP or Exec. Dir) * Ok xx/xx/xxxx

Mr. Pandu Financial Head Ok xx/xx/xxxx

Mr. Vandanam Project Manager Ok xx/xx/xxxx

Mr. Kartik Delivery head Ok xx/xx/xxxx

Mr. Dooku Project Coordinator Ok xx/xx/xxxx

*By authorizing this Project Closure, the Project Stakeholder(s), and Executive Sponsor agree to all terms within this document.

Revision History
Identify document changes.
Version Date Name Description

1.0 xx/xx/xxxx Mr. Henry Ok to process

Section 1. General Information

Project Activity Date

Project Start 13th Feb 2023
Project Closure* 14th Aug 2023
* Date of Project Closure refers to the project finish date, meaning all project tasks have been completed

Cont. to Next page

Section 2. Business Objectives
As identified in section 2.2 of the Business Case.
Business Case Ref # Business Objectives Met/Not Comments
Met
BI0001 Farmer should be able to buy and sell Yes Ok
agricultural product online.

Section 3. Customer Expectation Management

Item Question Description Comments

1 Were all expected benefits and business outcomes Yes Ok
realized?
2 Were all expected performance standards satisfied? Yes Ok

Section 4. Outstanding Actions Items and Issues

Action Item Transition and/or Resolution

Section 5. Project Office Checklist

Deliverable Description
Risk Assessment completed and posted on suitable shared storage. Yes No

Business Case completed and posted on suitable shared storage. Yes No

Project Charter completed and posted on suitable shared storage. Yes No

Meeting Notes completed and posted on suitable shared storage. Yes No

Additional project documentation and artifacts posted on suitable Yes No

shared storage, including Requirements Template, Project Change
Requests, Milestone Timeline, Work Breakdown Structure, etc.

Lessons Learned documented. Yes No

Project folder moved completed projects on suitable shared storage. Yes No

Support Handover Document completed and archived. Yes No

Comments
Ok to process. Application running properly.

Cont. to Next page