Proj Prep 1 Case Part 1 : Online Agriculture Products Store

 2 Crores INR and 18 months Duration under CSR initiative

 Current problems:
1. difficulties in procuring fertilizers.
2. buying seeds for farming for certain crops.
3. lack of pesticides which could help in greatly reducing pests in crops.

Looking at current problem, Mr. Henry has a team pulled in on-board.

 Mr. Henry’s company (SOONY) has the following team:

1. Mr Pandu - Financial Head
2. Mr Dooku - Project Coordinator.

 Mr. Henry has outsourced this project to a company named (APT IT SOLUTIONS)
1. Mr Karthik - Delivery Head in APT IT SOLUTIONS
2. Mr Vandanam - project Manager
3. Ms. Juhi - Senior Java Developer
a) MrTeyson - Java Developers
b) Ms Lucie - Java Developers
c) Mr Tucker - Java Developers
d) Mr Bravo - Java Developers
4. Mr Mike - Network Admin
5. John - DB Admin
6. Mr Jason - Tester
7. Ms Alekya – Tester
8. Myself – Business Analyst

Decoding the case study:

 Project Idea – to develop a website devoted to make an online agriculture product store to
facilitate remote area farmers to buy agriculture products.
 Current Need - to facilitate farmers to buy seeds, pesticides, and fertilizers from anywhere
through internet connectivity.
 Overview of the project – It is an Online Web / mobile Application with the help of which
Farmers and Companies (Fertilizers, seeds and pesticides manufacturing Companies) can
communicate directly with each other.
 Current problems: difficulties in procuring fertilizers, buying seeds for farming, lack of pesticides.
 1. BUSINESS PROCESS MODEL:
It is a visual representation or diagram that illustrates the flow of activities and tasks within a
business process.

 Goal: to create an online platform/ mobile application (agriculture product store) that
facilitates remote area farmers to purchase agricultural products like seeds, pesticides and
fertilizers directly from the manufacturers with a seamless process.
 Input: farmer’s details, manufacturer’s details, product information, technology requirement
to build the platform, budget for the project and the deadline of the project.
 Resources: Software, Human resources and financial resources.
 Outputs: Online agriculture product store (web/mobile application), sales, revenue and
active users.
 Activities:
o Collecting all the details from the manufacturers and farmers.
o Designing the application architecture with all the specifications and features.
o Testing the product functioning and its accessibility.
o Making the application available for the users through play store.
o Monitoring application performance.
o Collecting and working on the feedbacks received from the users (manufacturers or
customers)
 Values: customer satisfaction, accessibility, social responsibility, efficiency and user-friendly
experience.

2. SWOT ANALYSIS:

STRENGTHS WEAKNESSES
a) OPPORTUNITIES
Social responsibility. a) THREATS among farmers.
Low level of awareness
b) Direct benefit for farmers. b) Lack of proper education in farmers.
a) Growing demand. a) Competition.
c) Cost efficient.penetration in villages. c) Technology barrier.
b) Smartphone b) Local/traditional suppliers
d) Ease of useinterest.
(application). d) Delivery challenges.
c) Investors goodwill.
e) Transparency. e) Operational and maintenance cost.
d) Expansion of the product and small- c) Delivery challenges.
f) No middle
scale man involved.
businesses. d) Stock maintenance issues.
e) Market opportunity for advancement. e) Cybersecurity threats like scams
and online frauds.
f) Financial challenges for the
 3. FEASIBILITY STUDY:

a) Technology: The project will be technologically feasible based on the database server, used
methods of payment options/gateways, security and API. Also, the internet connection in
rural area and the compatibility of the device (mobile phones) would play a vital role in this.
b) Hardware: Storage, backup system, network infrastructure, server infrastructure, user device
(farmer and manufacturer device).
c) Software: Shopping cart software, payment gateway software and security software.
d) Resources: Human resources and financial resources.
e) Budget: Personnel cost, software and hardware development cost, marketing cost,
operational cost, logistics cost and reserves.
f) Timeframe: It is the overall time every resource would take for the project completion. It
also depends on the number of specifications/features needed and the number of resources
we have.

4. GAP ANALYSIS:

Current State (Where we are now):

 Farmers being in rural areas have lack of knowledge about the basic understanding
of the product specifications.
 Having limited access to the internet or lack of technology friendly environment.
 Lack of awareness about any online platform and farmers being dependent on the
traditional sellers/middle man to buy the product at monopoly market price.
 Farmers facing challenges to get the product timely due to geographical barrier and
lack of smooth communication.
 Being in rural areas, there is least knowledge about the payment gateways or online
payment methods.
 Lack of post purchase support and no facility to provide feedback for the
improvement.

Desired State (Where we need to be):

a) Develop educational content and organize small campaigns to raise awareness so that
farmers can have the good understanding about the variety of agricultural products.
b) Improvement of the internet connection for farmers to have an easy access to the app.
c) Having an easy-to-use mobile app along with the easy payment gateway options which allow
farmers to purchase the products seamlessly with different cost options.
d) Establishing good communication through the app between farmers and manufacturers to
improve the tracking of the products.
e) Increasing awareness about the payment methods and having an app with multiple forms of
payment, including UPI, digital wallets, credit/debit cards, and COD (Cash on Delivery).
 f) Having a dedicated customer support team for after sales service, return requests, and order
tracking facilities.
5. RISK ANALYSIS:

a) Internal Risks:
I. Lack of coordination between the teams.
II. Shortage of skilled personnels.
III. Misalignment between direction of work and project objective.
IV. Project exceeding the timeline.
V. Budget overrun.

b) External Risks:
I. Change in market trends.
II. Entry of the competitors.
III. Change in government laws.
IV. Logistics and delivery challenges.

c) BA Risks:
I. Incomplete/incorrect requirement.
II. Lack of communication with stakeholders.
III. Continuous changes in the primary objective of the project

d) Project based risks

I. Project exceeding the timeline.
II. Project budget overrun.
III. Adaptability and understanding issue between farmers and manufacturers.

6. RACI Matrix
Option Name of the resources Designation Details
Mr Dooku Project Coordinator Contact Number - 9149163673
Ms Juhi Senior Java Developer Contact Number - 9278402626
Mr Teyson Java Developers Contact Number - 9394790723
Ms Lucie Java Developers Contact Number - 9515362931
Mr Tucker Java Developers Contact Number - 9316104604
Responsible Mr Bravo Java Developers Contact Number - 9635981556
Mr Mike Network Admin Contact Number - 9184310661
Ms Alekya Tester Contact Number - 9310617790
Mr Jason Tester Contact Number - 9501308686
Mr Vandanam Project Manager Contact Number - 9449891948
Peter, Kevin, Ben Stakeholders Contact Number - 9679232122
Accountabl Mr Henry Founder Contact Number - 9354602628
e Mr Pandu Financial Head Contact Number - 9408509561
Mr Karthik Delivery Head Contact Number - 9700062843
 Mr Vandanam Project Manager Contact Number - 9137082939
John DB Admin Contact Number - 9236880399
Myself Business Analyst Contact Number - 9587709074
Mr Dooku Project Coordinator Contact Number - 9149163673
Ms Juhi Senior Java Developer Contact Number - 9278402626
Mr Teyson Java Developers Contact Number - 9394790723
Ms Lucie Java Developers Contact Number - 9515362931
Mr Tucker Java Developers Contact Number - 9316104604
Mr Bravo Java Developers Contact Number - 9635981556
Mr Mike Network Admin Contact Number - 9184310661
Ms Alekya Tester Contact Number - 9310617790
Consulted
Mr Jason Tester Contact Number - 9501308686
Mr Vandanam Project Manager Contact Number - 9449891948
Peter, Kevin, Ben Stakeholders Contact Number - 9679232122
Mr Henry Founder Contact Number - 9354602628
Mr Pandu Financial Head Contact Number - 9408509561
Mr Karthik Delivery Head Contact Number - 9700062843
John DB Admin Contact Number - 9236880399
Myself Business Analyst Contact Number - 9587709074
Informed NA NA NA

7. BUSINESS CASE DOCUMENT:

 Why is this project initiated?

Answer - This project is initiated with the goal of solving a critical problem faced by farmers
involved in agriculture in the remote areas. After becoming a successful business man, Mr. Henry
observed the difficulties faced by farmers like Peter, Levin and Ben regarding the procurement of
the basic products used in agriculture like fertilizers, seeds, and pesticides. Since the same issue
was faced by the other farmers as well, Mr Henry decided to create an online agriculture product
store (mobile app) through which farmers can easily connect with the manufacturers and get all
the products as per their respective requirements at different price range.

 What are the current problems?

Answer – The current problems faced by the farmers are:

a. Lack of access to the basic agricultural products like seeds, fertilizers and pesticides.
b. Lack of logistic and delivery facility in the rural areas.
c. Lack of connectivity and communication between the manufacturers and farmers.
d. Lack of knowledge and awareness about the best options available in the market.

 With this project, how many problems could be solved?

Answer – With the help of this project the below problems can be solved:
 a. Easy access to the agricultural products for the farmers like seeds, fertilizer and
pesticides.
b. Improvement in connectivity between farmers and manufacturers so that they can
directly communicate about their requirements.
c. Reduction in the travel and logistic cost since the delivery services would be
managed by the project owners and famers would not have to travel to buy these
products.
d. This project will save farmers time since buying these products manually require lots
of man hours.
e. Improvement in knowledge and awareness about the products available in the
market along with their best utilities.

 What are the resources required?

Answer – This project requires – Human resource, financial resources and technology resources.

 How much organizational change is required to adopt this technology?

Answer – The changes in the organization would depend on the current state of the
organization’s infrastructure, however, we might need to do some moderate changes.

For this, we can include the below pointers –

a. Adoption of the digital payment method.

b. Changes in the supply chain and logistics to ensure seamless delivery process.
c. Training of the human resources according to the need of the application
development.
d. Creation of customer support system/team for the application users to provide after
sale services and addressing ongoing escalations.

 What is the Time frame to recover ROI?

Answer – The ROI depends on the different factors like – adaptability of the users, increase in the
subscribers, volume of sales, profit converted and operational cost.

However, since the target audience for this project is mainly from the rural areas, it might take
12-14 months to increase the awareness about the application and upto 2 years to get significant
increase in users. Therefore, the project ROI is expected to be between 3-4 years.

 How to identify stakeholders?

Answer – Stakeholders are the individuals that are directly and indirectly effected by the
outcome of the project. They play a vital role in making any decisions or changes regarding the
project.

For this project we can follow the below steps:

 a. Creating a list of team members.
b. Identifying the role and functions of each member to bifurcate in different
categories of RACI matrix (Responsible, Accountable, Consulted and Informed).
i. Responsible – The person who performs the day-to-day work AND
contributes towards the development of the project.
ii. Accountable – The person who is responsible for monitoring and
ensuring the work is done on time.
iii. Consulted – The person who is consulted frequently regarding their
inputs in the project.
iv. Informed – The person who is kept informed about the development
and progress of the project.

c. Gathering all the details and having a meeting with all the stakeholders to ensure
the objective and direction of the project is on the right track.
d. Maintaining communication with all the stakeholders frequently to ensure the
proper alignment of the project success.

8. Four SDLC Methodologies

A. Sequential – Waterfall Model: Waterfall model is the most common and classic models
of SDLC. Each phase of the model is important to be completed before we move to the next
step. Also, it is very important to review the work at the end of each phase since it helps to
understand if the project is on right track or not.
Here are the stages of the waterfall model:

I. Requirement Gathering: We collect all the details from the stakeholders and
document them to begin the project. This document is also known as BDR (Business
Requirement Document).
II. Requirement Analysis: In this step we analyse the documented information and find
out about the required techniques based on the business need.
III. Design: After the analysis, we identify the system architecture and design.
IV. Development (coding): In this process the codes are prepared and complied based
on the design specifications.
V. Testing: After the software is created, it undergoes testing to identify and resolve any
issues.
VI. Deployment and Implementation: After testing, the software is deployed where it
becomes accessible to end users.
VII. Maintenance: Post deployment the software is updated and the maintenance is
done to fix any issues that arise during actual use and to enhance the system with
new features.

 Functional Specifications (FS), Software Requirements Specification (SRS), Requirements

Traceability Matrix (RTM).
 High-Level Design Document (HDD), Low-Level Design Document (LDD)
 Stages of Waterfall Model Resources Artifacts
Requirements gathering BA, PM BRD
BA, PM,
Requirements Analysis Tech Team – Sol Arch, NW Arch, FS/ FRS, SSD, SRS, RTM
DB Arch
Tech Team – Sol Arch, NW Arch, HDD / ADD,
Design
DB Arch, GUI Designer Solution Document
Development – coding Programmers, Developers LDD / CDD, Application
Test Documents,
Testing Testers
Application with less Errors
Unit, Component, System, System Integration, UAT
PROCESS - Configuration Management PM
Deployment & Implementation Release Engineers

B. Iterative – RUP (Rational Unified Process): It is an iterative software development

process framework created by the Rational Software Corporation, which was acquired by
IBM in February 2003.
It is a software development methodology that uses an iterative approach, where the
project is developed through repeated cycles (iterations). Unlike the Waterfall model, which
follows a linear progression, RUP emphasizes incremental improvements and adaptability to
change throughout the project lifecycle.

Here are the six engineering disciplines in RUP:

I. Business Modeling: In this stage we identify and understand the business context,
needs, and processes that the software must support.
II. Requirements: In this stage, the requirements for the system are gathered,
analyzed, and documented. We create the use cases to capture functional
requirements, and non-functional requirements.
III. Analysis and Design: This stage involves designing the system's architecture and
creating a blueprint for the solution.
IV. Implementation: The coding is done at this stage, where the design is translated
into executable code.
V. Testing: In the testing stage, the software undergoes thorough testing to identify
and fix defects. The testing verifies the quality of the software and ensures that it is
ready for production.
VI. Deployment: This stage focuses on releasing the software and making it available to
users.

Apart from the above, there are four project life cycle phases as below:

I. Inception: In this phase the agreement is done among the team and customer as to
what will be built. This stage is to identify business requirements, project goals,
estimation of resources and determine the risk.
II. Elaboration: At this stage, the team decides the architecture and design required to
achieve the desired system behaviour.
 III. Construction: After the elaboration phase, the software is built and developed
based on the architecture and design established.
IV. Transition: At this stage, the testing is done to rectify all the defects and post this
the software is deployed to make it accessible for the end users.

Phases
Inception Elaboration Construction Transition
Disciplines

Business Modelling

Requirements

Analysis & Design

Implementation

Test

Deployment

Configuration and
Change mgmt.

Project Management

Environment

Iterations
Initial Elab #1 Elab #2 Const #1 Const #2 Const #N Tran #1 Tran #2

C. Evolutionary – Spiral: It is a software development process that combines iterative

development with elements of the Waterfall model. This model gives more emphasis placed
on risk analysis since the project passes through multiple iterations (or spirals), each of
which includes four key phases: Planning, Risk Analysis, Engineering, and Evaluation.

The spiral model has four phases:

I. Planning – In this step the requirements are gathered and analyzed. Also, a plan for
the current iteration is created, including timelines, resources, and goals.
II. Risk Analysis - The primary focus of this phase is identifying potential risks and
evaluating alternative solutions to mitigate those risks.
III. Engineering - Based on the risk analysis and feedback, the actual software is
developed, refined, and tested.
IV. Evaluation - The team and stakeholders evaluate the progress of the project so that
the customers can review the current version of the software and provide feedback
to guide the next iteration.

Advantages
a. High amount of risk analysis.
 b. Good for large and mission-critical projects.
c. Software is produced early in the software life cycle.

Disadvantages
a. Can be a costly model to use.
b. Risk analysis requires highly specific expertise.
c. Project’s success is highly dependent on the risk analysis phase.
d. Doesn’t work well for smaller projects

Cumulative cost

Progress through steps

Plan Risk Analysis

Risk Analysis

Evaluate alternatives,
Determine Objectives Risk Analysis identity, resolve risks
Alternate constrains
Risk Analysis Operational
Prototype
Prototype
Prototype
Com
Commitment Ops Prototype
Review Rqts plan
Partition Concept of
Life cycle
operations
plan
Detailed
Development Requirement Software product Design
plan Validation design
Code
Unit
Integration and Design validation Test
test plan and verification Integration
And test
Acceptance
Evaluate Implementation
test Engineering

Plan next Develop, verify next level product

D. Agile – Scrum: is a project management and software development methodology that

focuses on flexibility, collaboration, customer feedback, and iterative progress. Unlike
traditional linear approaches like the Waterfall model, Agile emphasizes adaptive planning,
continuous improvement, and rapid delivery of functional software.
The Agile approach is widely used in software development but can also be applied to other
types of projects and industries.
 Agile methodology - Agile methodology is a project management framework that breaks
projects down into several dynamic phases, commonly known as sprints.

The Agile framework is an iterative methodology. After every sprint, teams reflect and look
back to see if there was anything that could be improved so they can adjust their strategy
for the next sprint.

6. Review 1. Plan

Agile
5. Deploy 2. Design
methodology

4. Test 3. Develop

Here are the four main values of Agile:

a. Individuals and Interactions over Processes and Tools

b. Working Software over Comprehensive Documentation
c. Customer Collaboration over Contract Negotiation
d. Responding to Change over Following a Plan

Also, there are twelve principles of Agile:

I. Satisfy the customer.

II. Welcoming changing requirements.
III. Deliver working software frequently.
IV. Frequent interaction with stakeholders.
V. Motivated individuals.
VI. Face-to-face communication.
VII. Measure by working software.
VIII. Maintain constant pace.
IX. Sustain technical excellence and good design.
X. Keep it simple.
XI. Empower self-organizing teams.
XII. Reflect and adjust continuously.
9. Four SDLC Models:
A. V- Model: Verification and Validation Model, is a software development methodology that
emphasizes a sequential and structured approach to the development lifecycle. It is an
extension of the traditional Waterfall model, with a focus on testing and validation at each
stage of the development process.

Below are the phases of the V-Model –

Verification Phase
I. Requirement Analysis
II. System Design
III. Software Design
IV. Module Design
V. Coding

Validation
VI. Unit Testing
VII. Integration Testing
VIII. System Testing
IX. Acceptance Testing

Requirement Analysis Acceptance Testing

System Design System Testing

Verification Phase Validation Phase

Software Design Integration Testing

Module Design Unit Testing

Coding

B. RUP (Rational Unified Process): It is an iterative software development process framework

created by the Rational Software Corporation, which was acquired by IBM in February 2003.

It is a software development methodology that uses an iterative approach, where the

project is developed through repeated cycles (iterations). Unlike the Waterfall model, which
follows a linear progression, RUP emphasizes incremental improvements and adaptability to
change throughout the project lifecycle.

Here are the six engineering disciplines in RUP:

 VII. Business Modeling: In this stage we identify and understand the business context,
needs, and processes that the software must support.
VIII. Requirements: In this stage, the requirements for the system are gathered,
analyzed, and documented. We create the use cases to capture functional
requirements, and non-functional requirements.
IX. Analysis and Design: This stage involves designing the system's architecture and
creating a blueprint for the solution.
X. Implementation: The coding is done at this stage, where the design is translated
into executable code.
XI. Testing: In the testing stage, the software undergoes thorough testing to identify
and fix defects. The testing verifies the quality of the software and ensures that it is
ready for production.
XII. Deployment: This stage focuses on releasing the software and making it available to
users.

Apart from the above, there are four project life cycle phases as below:

V. Inception: In this phase the agreement is done among the team and customer as to
what will be built. This stage is to identify business requirements, project goals,
estimation of resources and determine the risk.
VI. Elaboration: At this stage, the team decides the architecture and design required to
achieve the desired system behaviour.
VII. Construction: After the elaboration phase, the software is built and developed
based on the architecture and design established.
VIII. Transition: At this stage, the testing is done to rectify all the defects and post this
the software is deployed to make it accessible for the end users.

Phases
Inception Elaboration Construction Transition
Disciplines

Business Modelling

Requirements

Analysis & Design

Implementation

Test

Deployment

Configuration and
Change mgmt.

Project Management
Initial Elab #1 Elab #2 Const #1 Const #2 Const #N Tran #1 Tran #2
Environment C. Evolutionary – Spiral: It is a software development process that combines
iterative development with elements of the Waterfall model. This model
Iterations
gives more emphasis placed on risk analysis since the project passes through multiple
iterations (or spirals). The spiral model has four phases:
 i. Planning – In this step the requirements are gathered and analyzed. Also, a plan for
the current iteration is created, including timelines, resources, and goals.
ii. Risk Analysis - The primary focus of this phase is identifying potential risks and
evaluating alternative solutions to mitigate those risks.
iii. Engineering - Based on the risk analysis and feedback, the actual software is
developed, refined, and tested.
iv. Evaluation - The team and stakeholders evaluate the progress of the project so that
the customers can review the current version of the software and provide feedback to
guide the next iteration.

Advantages
a. High amount of risk analysis.
b. Good for large and mission-critical projects.
c. Software is produced early in the software life cycle.

Disadvantages
a. Can be a costly model to use.
b. Risk analysis requires highly specific expertise.
c. Project’s success is highly dependent on the risk analysis phase.
d. Doesn’t work well for smaller projects

Cumulative cost

Progress through steps

Plan Risk Analysis

Risk Analysis

Evaluate alternatives,
Determine Objectives Risk Analysis identity, resolve risks
Alternate constrains
Risk Analysis Operational
Prototype
Prototype
Prototype
Com
Commitment Ops Prototype
Review
SSS Rqts plan
Concept of
Partition Life cycle
operations
plan
Detailed
Development Requirement Software product Design
plan Validation design
Code
Unit
Integration and Design validation Test
test plan and verification Integration
Evaluate And test
D. Scrum: It is an Agile framework
Acceptance used primarily for managing
software development, though itImplementation
can be applied
testto other fields as well. It focuses on Engineering
delivering small, workable increments of a product over time. Scrum emphasizes
teamwork, accountability, and iterative progress toward a well-defined goal.
Plan next Develop, verify next level product
It can be implemented either at the beginning of the project or when you sense that the
project is falling behind schedule. This model exercises full Admin Power.

 Scrum team – Project resources are grouped as Scrum teams which comprises of
BAs, Developers, Testers. Each Team size will on average be 7-8.

a. Product Owner – He will decide what needs to be in the product and will be
responsible for how the product has to be. He will regularly interact with
customers and BAs. This role may be played by BA or any person who worked for
end users for a long time or customer himself.
b. Scrum Master – He will monitor the performance of the team within the sprint.
Team will raise all their issues to scrum master and he will run to look for
answers. This role can be played by any person in team, however, normally BA’s
plays this role.

 Sprint: This is a period that team decides to deliver their objective. Normally a
sprint period will be for 2 weeks but may extend to 4 weeks.

 Meetings:
a. Sprint Planning Meeting – This happens at the beginning of each sprint and
team decides on what they will be delivering in the sprint.

b. Daily Scrum Meeting – This happens each day where team will just answer 3
questions:
I. What did you do today?
II. What will you do tomorrow?
III. Is there any impediments that is slowing or stopping you?

c. Sprint Review Meeting – This happens at the end of the sprint where team will
demo the completed stories to product owner and get it cleared.

d. Sprint Retrospective Meeting – This happens at the end of the sprint where
team will answer the below 3 questions-
I. What went well in the sprint?
II. What did not go well?
III. What are the required areas of improvement in the next sprint?

10.Waterfall Vs V-Model
 Waterfall Model: Waterfall model is the most common and classic models of SDLC. Each phase of
the model is important to be completed before we move to the next step. Also, it is very important
to review the work at the end of each phase since it helps to understand if the project is on right
track or not.

V-Model: Verification and Validation Model, is a software development methodology that

emphasizes a sequential and structured approach to the development lifecycle. It is an extension of
the traditional Waterfall model, with a focus on testing and validation at each stage of the
development process.

Here are some of the differences between Waterfall model and V-Model:

Sr No. Aspect Waterfall Model V-Model (Verification and Validation Model)

This is linear and sequential but involves testing
1 Process Type This is linear and sequential
at each stage
It works as per step-by-step Each development phase has a corresponding
2 Approach
process with no overlap. testing phase.
This has Waterfall model phases, but testing is
involved with each phase:
This model has 4 phases –
Requirement, Design, Requirement Gathering <-> Acceptance Testing
3 Phases
Implementation, Verification, System Design <-> System Testing
and Maintenance. Software Design <-> Integration Testing
Model Design <-> Unit Testing
Coding
Testing begins only after the Testing starts alongside or directly after each
4 Testing development phase is development phase, ensuring early detection of
complete. issues.
Very rigid, changes are hard to Less flexible due to sequential nature but allows
5 Flexibility implement once a phase is testing at each phase, which can lead to earlier
completed. detection of defects.
No overlapping of phases; Each development phase has a corresponding
once a phase is completed, the testing phase, and the two sides of the V are
6 Phases Overlap
project moves to the next linked together, but no overlap in the
phase. development side.
Focus on documentation and
Focus on verification and validation, with early
7 Emphasis deliverables at the end of each
and continuous testing.
phase.
Risks are typically identified
Risks are detected early due to integrated testing
8 Risk Detection late in the process, during the
at every stage.
testing phase.
Changes are costly and
Changes are still costly but defects are identified
9 Cost of Changes difficult to implement once
earlier, reducing late-stage rework.
the development progresses.
Best suited for projects with
Suitable for projects where requirements are
Suitability for clear, well-defined
10 clear but with a strong emphasis on testing and
Projects requirements that are unlikely
quality assurance.
to change.
Users typically see the product User feedback can be incorporated during the
11 User Feedback only after development is testing phases, especially during acceptance
complete (during UAT). testing.
 Projects with stable, well-
Projects where verification and validation are
understood requirements
12 Ideal Use Case critical, such as medical software, aerospace, or
(e.g., simple applications or
safety-critical systems.
systems).
High documentation at each Documentation is similarly required, but testing
13 Documentation phase (e.g., requirements, plans and results are tightly integrated with
design documents). development documentation.
Simple applications, small
Safety-critical applications, embedded systems,
projects, or systems where
14 Examples regulatory-compliant software (e.g., healthcare,
requirements do not change
defense).
during development.
This is more time taking as compared to the
This is less time taking as
15 Time Required waterfall model since it requires testing at each
compared to the V-model.
stage.

11.Justify your choice

Question: As a BA, state your reason for choosing one model for this project?
Answer: According to my understanding, V-model is suitable for Mr. Henry’s project due to
the below reasons:
1. Target audience – Farmers being the target audience for this project involves various
risk due to the limited exposure of online platforms, lack of education and awareness
about the new technologies. In such condition, V-Model would suit best because of
its nature.
2. Reliability – V-Model is more reliable since it involves rigorous testing of each stage,
whereas in waterfall model the software can be testing after the
coding/development is done.
3. Testing - Continuous testing at each phase will minimize risks and ensure the
application meets expectations from the start.
4. Stakeholder Requirement – Since the most critical stakeholders are farmers and
manufacturers from the rural area (majorly) and from the urban area as well, the V-
model would help us to ensure that quality and requirements are consistently met.
5. User Friendly Software – With the help of verification and validation process, the
feedbacks can be addressed properly resulting to a user friendly application.
6. Trust and relationship – Since farmers are the primary reason behind this project, it is
very important to maintain the trust and good relationship to assure them about the
fulfilment of their requirement.

12.Gantt Chart
 Question - The Committee of Mr. Henry, Mr Pandu, and Mr Dooku discussed with Mr Karthik and
finalised on the V Model approach (RG, RA, Design, D1, T1,D2,T2,D3,T3,D4, T4 and UAT) Mr
Vandanam is mapped as a PM to this project. He studies this Project and Prepares a Gantt chart with
V Model(RG, RA, Design, D1, T1, D2, T2, D3, T3, D4, T4 and UAT) as development process and the
Resources are PM, BA, Java Developers, testers, DB Admin, NW Admin.

Answer – Here is the Gantt chart for the provided job titles and stages of the project (development
process):

Resources RG RA Design D1 T1 D2 T2 D3 T3 D4 T4 UAT

Project Manager 1

Business Analysis 1

Java Developers 5 2

Testers 2

DB Admin 1

NW Admin 1

13.Difference between Fixed Bid Vs Billing Project

A. Fixed Bid Project: In these types of projects, the cost is pre-agreed for delivering the required
product/software, regardless of the number of resources required. In these types of projects,
the requirements are defined at the beginning and the budget is fixed and agreed before it
starts.

Advantages of the Fixed Bid –

a. Predictable Costs for the Client: The pre-decided cost protects the client from
unexpected expenses and budget overruns.
b. Resource Planning for the Provider: The vendor can effectively plan and allocate
resources according to the agreed-upon budget.
c. Structured Project Management: Each stage of the project is clearly defined in terms of
manpower and financial requirements, enabling better categorization and planning.

Disadvantage of the Fixed Bid Project

a. Limited Flexibility: The fixed budget restricts the ability to make changes to the project,
as any amendments may result in additional expenses.
 b. Risk of Loss for the Provider: The service provider may face financial losses if the initial
cost or effort estimations are inaccurate.

B. Billing Project: In these types of projects, the billing is done based on the time and resources
utilized on the project. Since there is no pre-decided budget, the service provider gets flexibility
to use the resources as per their convenience.

Advance of Billing Project –

a. Flexibility for the Client: These types of projects offer flexibility as the final cost may be
lower than the initially estimated budget if the project is completed efficiently.
b. Resource Allocation for the Service Provider: The service provider can allocate resources
without being constrained by a fixed budget.
c. Ideal for Unclear Requirements: Billing projects are well-suited for projects where
requirements are not clearly defined at the outset.

Disadvantage of Billing Project –

a. Higher Cost for the Client: The client may end up paying more since the budget is not
predetermined.
b. Potential Resource Management Issues: The service provider might struggle to manage
resources efficiently, as there are no strict budgetary constraints.

Difference between Fixed Bid project and Billing project –

Sr No. Feature Fixed Bid Project Billing Project
1 Budget The budget id pre-decided in The billing is done based on the time
these types of projects. consumed and resources utilized.
2 Cost This is cost effective since the This can be cost effective if the project
expenses are pre-agreed. is done efficiently, however there is a
risk of over costing.
3 FlexibilityThese is low flexibility. There is high flexibility.
4 Risk The risk bearer is service The risk bearer is client.
provider.
5 Nature This is best for the projects with This is best for the projects where the
fixed and well-defined changes are implemented frequently.
objectives.
6 Resource The resources are planned There are no constraints while
Management according to the provided deciding the resources since there is
budget. no restrictions of the budget.
7 Project Since the budget is pre-decided In this process, it involves risk at every
direction the project direction can be well stage since the budget is not
defined. provided.
8 Project Project planning is done more Project planning may fail at some
planning efficiently. stages.
 14.Preparer Timesheets of a BA in various stages of SDLC

 Design Timesheet of a BA
 Development Timesheet of a BA
 Testing Timesheet of a BA
 UAT Timesheet of a BA
 Deployment n Implementation Timesheet of a BA

WEEKLY TIME SHEET

Field Details
Name of Business Analyst
Email Address
Phone Number
Project Name
Project timeframe
Reporting Manager

Stage Name - Design

Date Stage/Process Name Start Time End Time Total Hours Task Description Remarks
Description about Remark for the
DD/MM/YY Design HH:MM HH:MM HH:MM
the task work done
DD/MM/YY Design
DD/MM/YY Design

Stage Name - Development

Date Stage/Process Name Start Time End Time Total Hours Task Description Remarks
Description about Remark for the
DD/MM/YY Development HH:MM HH:MM HH:MM
the task work done
DD/MM/YY Development
DD/MM/YY Development

Stage Name - Testing

Date Stage/Process Name Start Time End Time Total Hours Task Description Remarks
Description about Remark for the
DD/MM/YY Testing HH:MM HH:MM HH:MM
the task work done
DD/MM/YY Testing
DD/MM/YY Testing

Stage Name - UAT

Date Stage/Process Name Start Time End Time Total Hours Task Description Remarks
Description about Remark for the
DD/MM/YY UAT HH:MM HH:MM HH:MM
the task work done
DD/MM/YY UAT
DD/MM/YY UAT

Stage Name - Deployment n Implementation

Date Stage/Process Name Start Time End Time Total Hours Task Description Remarks
Deployment n Description about Remark for the
DD/MM/YY HH:MM HH:MM HH:MM
Implementation the task work done
Deployment n
DD/MM/YY
Implementation
Deployment n
DD/MM/YY
Implementation

Summary: