Capstone Project - 1 Part - 1
Capstone Project - 1 Part - 1
Capstone Project - 1 Part - 1
Identify Business Process Model for Online Agriculture Store – (Goal, Inputs, Resources, Outputs,
Activities, Value created to the end Customer)
Answer:
Goal-To facilitate rural area farmers with the website that will help them to buy seeds,
pesticides, and fertilizers from anywhere and also let farmers and companies communicate
through internet connectivity.
Inputs- The farmers requirements and their needs, Budget allocation for the
project(2crores), Time and efforts given towards the project.
Resources-The project Team which includes (project manager, BA, developers,
coders, Testers), Financial resources (Funds), research team, Time.
Outputs- Website for Farmers for purchasing of products.
Activities- Planning for the project, requirements gathering, budget allocating, coding,
testing, implementing of the project.
Value created to the end Customer- User friendly and easily accessible.
Question 2:
Mr Karthik is doing SWOT analysis before he accepts this project. What Aspects he Should consider
as Strengths, as Weaknesses, as Opportunity and as Threats.
Answer:
Strengths - Getting a project from the SOONY company due to his previous project success.
Weaknesses - Lack of existing efficient resources for doing such project.
Opportunity - This kind of project they are launching for the first time this is the opportunity
to capture the whole market.
Threats - Budget constraints (less allocated budget).
Question 3:
Mr Karthik is trying to do feasibility study on doing this project in Technology (Java), Please help him
with points (HW SW Trained Resources Budget Time frame) to consider in feasibility Study.
Hardware Requirements - Identify all the hardware requirements like Servers, network
infrastructure.
Software Requirements – Identify third-party software components or APIs are required to build
the application like Visual Studio Code, JDK and DBMS – MySQL, and testing tools like Selenium for UI
testing were accessible.
Trained Resources – 1 Project Manager, 5 Java developers, 1 Network Admin, 1 DB Admin, 2 Testers,
1BA.
Budget - Determine the budget required for the project, including hardware and software
Time Frame – The project has a duration of 18 months under the CSR initiative.
Question 4:
Mr Karthik must submit Gap Analysis to Mr Henry to convince to initiate this project. What points
(compare AS-IS existing process with TO-BE future Process) to showcase in the GAP Analysis.
Answer:
AS-IS:
o Limited access to diverse product options due to the geographical constraints and
reliance on local suppliers.
o Current process relies heavily on physical presence, which is not feasible for farmers
in remote areas.
o Farmers may not have access to all the necessary products due to limited local
availability.
o Significant time and effort required for farmers to travel, search for products,
negotiate prices, and complete purchases.
TO-BE:
o Farmers can easily access a wide range of agricultural products online, directly from
manufacturers, eliminating the need for travel.
o The online store will provide a centralized platform for browsing, selecting, and
ordering products at competitive prices.
o Faster procurement and delivery process, reducing costs and time associated with
manual purchasing.
o The platform provides manufacturers and suppliers with access to a broader market,
reaching farmers across remote and rural areas.
o Opportunities for manufacturers to expand their customer base and increase sales.
Conclusion of Gap Analysis:
The AS-IS process presents significant gaps in terms of efficiency, cost, accessibility, and
transparency.
The TO-BE process enabled by the new online agriculture product store will close these gaps
by providing a streamlined, efficient, and user-friendly platform that benefits both farmers
and suppliers.
By highlighting these gaps and how the new platform will address them, Mr. Karthik can
effectively convince Mr. Henry of the project's value and potential impact.
This gap analysis will showcase the clear benefits of initiating the project and align it with Mr. Henry's
goal of helping farmers and supporting the broader agricultural community.
Question 5:
List down different risk factors that may be involved (BA Risks And process/Project Risks)
Answer:
Inadequate Documentation
Process/Project Risks
Budget Risks
Question 6:
Perform stakeholder analysis (RACI Matrix) to find out the key stakeholders who can take
Decisions and Who are the influencers.
Answer:
o He is the owner of the company and sponsor of the project. All key aspects are
depended on Sponsor’s approval.
o As a financial head he/ she will aid the financial support of the project and
responsible for project budget management.
o As the end-users their feedback and requirements of the platform matters and add
significant value.
o As the Delivery head, responsible for overall delivery of the project in accordance
with technical requirements, time frame & budget.
o Responsible for developing the website with all necessary and usable features.
Primary Decision-Makers:
o Mr. Henry (Overall project sponsor and initiator)
Key Influencers:
Question 7:
Answer:
Executive Summary
Farmers in remote areas face difficulties in procuring fertilizers, seeds, and pesticides,
which are essential for farming. These products are not readily available in the market
and farmers often have to travel long distances to procure them. This leads to wastage
of time and money, which could have been utilized in farming activities. Therefore, there
is a need for a platform that can facilitate the purchase of these products for farmers.
Opportunity:
o By creating an online platform, we can provide a direct purchasing channel, reduce
intermediaries, and lower costs for farmers, while expanding the market for
manufacturers.
Objectives:
o To build a user-friendly online application (web/mobile) that connects farmers with
agricultural product manufacturers.
o To enable seamless communication, ordering, and delivery of agricultural products.
Scope:
o Development of a platform to display products from various manufacturers.
o Functionality for farmers to browse, select, and purchase products.
o Integration with payment gateways and delivery services.
For Farmers:
o Easy access to quality agricultural products.
o Reduced procurement costs and delivery time.
o Access to a wider range of products.
For Manufacturers:
o Expanded market reach and direct sales channels.
o Better understanding of farmer needs and preferences.
For SOONY:
o Fulfilling Corporate Social Responsibility (CSR) objectives by supporting local
communities.
o Enhancing brand reputation as a socially responsible company.
For APT IT SOLUTIONS:
o Opportunity to demonstrate expertise in building a scalable e-commerce platform.
o Potential for long-term partnership with SOONY for future projects.
Feasibility Analysis
Technical Feasibility:
o Use of Java technology stack (Spring Boot, Hibernate, etc.) is feasible given APT IT
SOLUTIONS' existing technical expertise and resources.
o Availability of skilled developers, testers, and network/database administrators.
Operational Feasibility:
o The proposed solution is operationally viable, with clear roles assigned to
developers, testers, network, and database administrators.
o Farmers and manufacturers are already willing to use the platform.
Economic Feasibility:
o The project budget of 2 Crores INR is adequate to cover all costs, including
development, deployment, and initial marketing.
o Potential for cost savings and revenue generation through direct sales and reduced
intermediaries.
Schedule Feasibility:
o The 18-month timeline is sufficient for development, testing, and deployment of the
platform.
Risk Analysis
Key Risks:
o Incomplete Requirements
o Technology Challenges
o Budget Overruns
o Data Security
Cost-Benefit Analysis
The estimated budget for the project is 2 crores INR. This includes the cost of development, testing,
deployment, and maintenance.
Question 8:
The Committee of Mr. Henry, Mr Pandu, and Mr Dooku and Mr Karthik are having a
discussion on Project Development Approach. Mr Karthik explained to Mr. Henry about
SDLC. And four methodologies like Sequential Iterative Evolutionary and Agile. Please
share your thoughts and clarity on Methodologies.
Answer:
Iterative Methodology:
The Iterative methodology is a development approach where the project is divided into small
parts, or Iterations. Each iteration is a mini-project that goes through the phases of
requirements, design, development, and testing.
At the end of each iteration, a working version of the product is developed, and feedback is
gathered to improve the next iteration.
Allows for modifications based on feedback and changing requirements after each iteration.
Frequent testing and iterations reduce the risk of significant defects or failures late in the
process.
Can be more resource-consuming due to repetitive cycles of planning, designing, and testing.
The final project timeline can be harder to predict as changes and iterations continue.
Suitable for projects where requirements are expected to evolve, and it is important to
deliver partial functionality early, such as in prototype development or when client feedback
is crucial.
Evolutionary Methodology:
In this approach, the initial product is not fully functional but evolves over time through a
series of iterations.
Enables early partial delivery, which can be tested and used by the end-users, providing early
value.
Enables early partial delivery, which can be tested and used by the end-users, providing early
value.
Requires careful planning to decide which increments to deliver first.
Ideal for large, complex projects where it is essential to deliver value incrementally, or for
projects with high uncertainty where regular feedback is required.
Agile Methodology:
Question 9:
They discussed models in SDLC like waterfall RUP Spiral and Scrum . You put forth your
understanding on these models
When the APT IT SOLUTIONS company got the project to make this online agriculture product store,
there is a difference of opinion between a couple of SMEs and the project team regarding which
methodology would be more suitable for this project. SMEs are stressing on using the V model and
the project team is leaning more onto the side of waterfall model. As a business analyst, which
methodology do you think would be better for this project?
Answer:
Waterfall Model:
Waterfall model is a traditional model. Waterfall model follows a structured approach with
each phase having specific deliverables.
At the end of each phase a review takes place to determine if the project is running fine.
Waterfall model works well for smaller projects where requirements are very well
understood.
V Model:
RUP stands for Rational Unified Process, where phase/ module wise (long term project)
application is developed. Hence, we can track the defects at early stages. This avoids the
downward flow of the defects.
Change request is welcomed in every phase of development.
This model is called heavy weight process model.
This model has multiple stages which requires more resources and more budget.
Spiral Model:
The spiral model is a risk driven process model generator for software projects.
The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation.
A software project repeatedly passes through these phases in iterations (called Spirals in this
model).
The baseline spiral, starting in the planning phase, requirements are gathered and risk is
assessed. Each subsequent spirals builds on the baseline spiral.
Considering the available information and the stable nature of requirements in this
project, I would recommend the waterfall model as the requirements are expected to be relatively
stable and well-defined at the beginning.
Question 10:
Write down the differences between waterfall model and V model.
Answer:
Waterfall Model:
Follows a linear, sequential approach where each phase must be completed before the next
one begins. The phases do not overlap.
Testing is a distinct phase that occurs after the development phase is completed. The focus
is mainly on development, and testing comes later in the lifecycle.
Less flexible; any changes in requirements after the project has started can be challenging to
accommodate due to its rigid, linear nature.
Risk is generally detected at later stages, which can lead to higher costs and more effort to
fix issues discovered late in the process.
May be more costly and time-consuming due to late-stage defect detection.
Suitable for small projects with well-defined, stable requirements where changes are
unlikely.
Requires comprehensive documentation at each phase before moving on to the next.
Poor at handling changes after the process has started, as it requires going back to the initial
stages to implement any changes.
V Model:
Also known as the Verification and Validation model, it is an extension of the Waterfall
Model, where development and testing activities are planned in parallel. Each development
phase has a corresponding testing phase.
Emphasizes early testing, as testing activities are integrated with each development stage.
Verification (static testing) occurs parallel to development, and validation (dynamic testing)
follows after each corresponding phase.
Also less flexible, but since testing phases are planned earlier and in parallel with
development phases, defects can be detected and corrected sooner.
Risk is managed better as verification and validation are done simultaneously, and issues are
detected and resolved earlier.
Potentially more cost-effective and time-efficient because defects are identified and fixed
earlier in the process, reducing the need for significant changes later on.
Suitable for projects where requirements are clear, well-defined, and stable, and where
early testing is a priority.
Also requires detailed documentation, but focuses more on developing test cases and plans
alongside development documents.
Similar in handling changes, as changes would also require going back to the corresponding
phase and its testing counterpart.
Question 11:
As a BA, state your reason for choosing one model for this project
Answer:
I would choose V model because this type of project is quite new for the company and it require
more time on design and testing .so In V model after one phase is completed then we will do design
and testing and then only we can start with the next phase.
Question 12:
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:
Question 13:
Answer:
A Fixed Bid project (also known as a Fixed Price project) is one where the service provider or
contractor agrees to complete a project for a set price, regardless of the actual time or costs
incurred.
The total cost of the project is agreed upon before work begins. This cost remains constant
unless there is a change in scope or requirements.
The client is billed the agreed-upon price, regardless of how much time or resources the
project actually takes. Payments may be made upfront, upon milestones, or after project
completion.
The risk is primarily on the service provider. If the project takes more time or costs more than
estimated, the provider absorbs the additional cost.
Fixed Bid projects are ideal for projects with well-defined scopes, clear requirements, and
predictable deliverables.
2. Billing Projects
A Billing project (often called a Time and Materials project) is one where the client is billed
based on the actual time spent and materials used to complete the project.
There is no fixed price upfront; instead, costs are calculated based on hourly rates, time
spent, and any materials or resources used.
The client is billed periodically (e.g., weekly or monthly) based on actual time and expenses
recorded. This could include charges for hours worked by staff, materials, equipment, or
other resources.
The risk is primarily on the client since the total cost can fluctuate depending on the time
and materials required to complete the project.
Billing projects are best for projects with uncertain scope, potential for changes, or when the
project requirements are likely to evolve over time.
Question 14:
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
Answer:
Design Timesheet of a BA
Date Task Description Start End Total Comments
Time Tim Hours
e
26- Stakeholder Interviews for 09:0 11:0 2 Conducted interviews with
08- Requirements Gathering 0 0 farmers and companies
2024
26- Create Business Requirement 11:3 13:3 2 Drafted the initial BRD
08- Document (BRD) 0 0
2024
26- Develop Wireframes and 14:0 16:0 2 Created wireframes for user
08- Prototypes 0 0 interface
2024
26- Review and Approval Meeting 16:3 18:0 1.5 Held review meeting to finalize
08- with Stakeholders 0 0 requirements
2024
Development Timesheet of a BA
Date Task Description Start End Total Comments
Time Tim Hours
e
27- Requirement Clarification with 09:0 10:3 1.5 Discussed user stories and
08- Development Team 0 0 acceptance criteria
2024
27- Update Requirement 10:4 12:1 1.5 Updated user stories and use
08- Documents 5 5 cases based on feedback
2024
27- Attending Daily Scrum 12:3 13:0 0.5 Participated in stand-up to
08- Meetings 0 0 provide updates
2024
27- Preparing 14:0 15:3 1.5 Created wireframes for new
08- Mock-ups/Prototypes 0 0 features
2024
27- Review and Feedback on 16:0 17:3 1.5 Reviewed current sprint progress
08- Development Progress 0 0 with developers
2024
Testing Timesheet of a BA
Date Task Description Start End Total Comments
Tim Tim Hour
e e s
28- Review Test Cases for 09:0 10: 1.5 Reviewed test cases for
08- Functional Requirements 0 30 alignment with requirements
2024
28- Clarification Session with 11:0 12: 1 Clarified functional requirements
08- Testers 0 00 to QA team
2024
28- Validate Test Results 13:0 14: 1.5 Validated testing outcomes
08- 0 30 against acceptance criteria
2024
28- Defect Triage Meeting 15:0 16: 1 Reviewed defects and prioritized
08- 0 00 them
2024
28- Update Requirements 16:3 17: 1 Updated documentation with
08- Document Based on Test 0 30 test results and new changes
2024 Findings
UAT Timesheet of a BA
Date Task Description Start End Total Comments
Time Time Hours
29-08- UAT Planning and Preparation 09:00 10:3 1.5 Prepared UAT plan and
2024 0 checklist
29-08- User Training 11:00 12:3 1.5 Conducted training session for
2024 0 end-users
29-08- UAT Execution and Support 13:30 16:0 2.5 Supported users during UAT
2024 0 execution
29-08- Gather UAT Feedback 16:15 17:0 0.75 Collected feedback from users
2024 0
29-08- Document UAT Findings and 17:00 18:0 1 Documented UAT results and
2024 Report Preparation 0 prepared reports