Capstone Project -1 Part – 2

Question 1: Check list

4 Quarterly Audits are planned Q1, Q2, Q3, Q4 for this Project What is your knowledge on how these
Audits will happen for a BA?

Answer:

Quarterly Audits for a BA:

Purpose: Ensure the project aligns with scope, budget, timeline, quality, and stakeholder needs.
Identify risks, issues, and deviations early.

BA Role:

 Requirement Verification: Confirm requirements are accurate and up-to-date.

 Documentation Review: Provide requirement specs, user stories, etc., to show compliance.
 Stakeholder Engagement: Show stakeholder feedback integration.
 Gap Analysis: Identify gaps between progress and objectives.
 Risk and Issue Management: Present risks, issues, and mitigation plans.
 Compliance Check: Ensure alignment with scope and standards.

Audit Phase Q1:

Stage Quarter 1 Audit Report: Requirements gathering phase

Tenure Week 1 – Week 10 (10 Weeks)
BRD template
Elicitation results report
Check
Client Sign off
list
Functionalities and features client sign off
Email Communication

Audit Phase Q2:

Stage Quarter 2 Audit Report: Requirements analysis phase

Tenure Week 16 – Week 23 (7 Weeks)
UML diagrams, Business to functional requirements mapping,
Check Client Signoff documents
list RTM document
Email Communication

Audit Phase Q3:

Stage Quarter 3 Audit Report: Design phase

Tenure Week 30 – Week 37 (7 Weeks)
Utilization of tools
Check Documented evidence of on Client communication
list Stakeholder MOM
Email Communication
Audit Phase Q4:
 Stage Quarter 4 Audit Report: Development and Testing phase
Tenure Week 40 – Week 75 (35 Weeks)
JAD Session report, BA & Developer MOM,
Test case documents & summary, End user training
Check
report,
list
Email communications as necessary

Outcome:

 Provide audit reports, recommendations, and corrective actions.

 Collaborate with the Project Manager and team to address any issues.

Question 2:

Before the Project is going to Kick Start, The Committee asked Mr Karthik to submit BA Approach
Strategy

Write BA Approach strategy (As a business analyst, what are the steps that you would need to follow
to complete a project – What Elicitation Techniques to apply, how to do Stakeholder Analysis
RACI/ILS, What Documents to Write, What process to follow to Sign off on the Documents, How to
take Approvals from the Client, What Communication Channels to establish n implement, How to
Handle Change Requests, How to update the progress of the project to the Stakeholders, How to
take signoff on the UAT- Client Project Acceptance Form )

Your Team

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 - You

Technical Team have assembled to discuss on the Project approach and have finalised to follow 3-tier
architecture for this project.

Answer:

BA Approach Strategy for the Online Agriculture Product Store Project

Elicitation Techniques:

Interviews: With stakeholders (Mr. Henry, Peter, Kevin, Ben, SOONY Committee, etc.).

Workshops: Collaborative sessions to gather and prioritize requirements.

Surveys: To gather insights from a broader group of farmers.

Observation: Understand current processes of farmers.

Prototyping: Create wireframes to clarify requirements.

Stakeholder Analysis:

 Identify Primary Stakeholders and Secondary Stakeholders

 RACI Matrix: Define roles (Responsible, Accountable, Consulted, Informed).

RACI/ILS:

Define the RACI (Responsible, Accountable, Consulted, Informed) or ILS (Input, Legal, Support) matrix
to clarify the roles and responsibilities of stakeholders in the project. This matrix will ensure clear
communication and accountability within the team.

Document Writing:

 Business Requirement Document.

 Functional Requirements Specification.
 Non - Functional Requirements Specification.
 Requirements Traceability Matrix (RTM).

Document Signoff Process:

 Present the draft documents to stakeholders in meetings.

 Conduct review sessions and gather feedback from all stakeholders.
 Revise documents based on feedback and finalize.
 Obtain formal approval and sign-off through email confirmation or digital signatures.
 Store signed-off documents in a shared repository accessible to all stakeholders.

Client Approvals:

 Submit documents for review and approval in stages: initial draft, revised draft, and final
version.
 Arrange review meetings with the client (Mr. Henry and SOONY Committee) to clarify doubts
and confirm requirements.
 Obtain written confirmation from the client for approvals and document them in the project
repository.

Communication Channels:

 To Establish effective communication channels with stakeholders, including regular meetings,

status updates, and progress reports.
 Use tools such as email, project management software, and collaboration platforms to
facilitate efficient communication and information sharing.

Handling Change Requests:

This includes documenting change requests, assessing their impact on project scope, timeline, and
budget, and obtaining appropriate approvals before implementing changes.

Updating Project Progress:

Provide regular progress updates to stakeholders, including the project manager, technical team, and
committee members. This can be done through status reports, dashboards, and meetings to ensure
transparency and keep stakeholders informed.

UAT Signoff:

 Conduct UAT with stakeholders and end-users to validate that the application meets all
agreed-upon requirements.
 Document all feedback and defects found during UAT in a UAT log.
 Address any issues or defects identified during UAT and conduct retesting if necessary.
 After successful UAT, obtain formal sign-off from the client (Mr. Henry and the SOONY
Committee) using a Client Project Acceptance Form.

Question 3:

Explain and illustrate 3-tier architecture?

Answer:

Application Layer: GUI Graphical User Interfaces like Screens and Pages, Validations on pages,
Organization specific business logic will be on the Application Layer

Business Logic Layer: All reusable components, frequently changing components, governing body
rules and regulations, compliances should go to middle layer Ex: Printer, Payment Gateways, mail
Servers, RBI rules for banks, IRDA rules for Insurance, etc.,

Data Layer: Data Base Components connecting to databases will be at the Data Layer.

Application Layer

Business Logic Layer

Data Layer

Question 4:

Business Analyst should keep What points in his/her mind before he frames a Question to ask to

the Stakeholder

(5W 1H – SMART – RACI – 3 Tier Architecture – Use Cases, Use case Specs, Activity Diagrams,
Models, Page designs)

Answer:

Before framing questions to ask stakeholders, a Business Analyst (BA) should consider the
following key points to ensure that they gather relevant, clear, and actionable information:

 5W 1H Approach:
o Who: Who are the stakeholders involved? Who will use or be affected by
the solution?
 o What: What are the business goals, problems, and requirements? What
features or functionalities are needed?
o When: When do the stakeholders expect to see deliverables or certain
milestones completed?
o Where: Where will the solution be used? Are there location-based
constraints or requirements?
o Why: Why is this requirement important? Why is the current solution not
sufficient?
o How: How will the solution work? How will it integrate with existing systems
or processes?

 SMART Criteria:
Questions should be designed to gather information that is:

o Specific: Focused on particular aspects, not vague.

o Measurable: Can the requirement be quantified or measured?
o Achievable: Is the requirement feasible given the project constraints?
o Relevant: Does it align with the project's objectives and business goals?
o Timebound: Is there a timeline for the requirement or deliverable?

 RACI Consideration:
Understand the roles and responsibilities of stakeholders:

o Responsible: Who will provide the necessary information?

o Accountable: Who has the final authority over decisions?
o Consulted: Who should be consulted for their opinions or expertise?
o Informed: Who should be kept informed about decisions and progress?

 Tier Architecture Understanding

Understand how the solution will be implemented across the three tiers:

o Application Layer: Questions regarding user interfaces, page designs, and user
experience.
o Business Logic Layer: Questions about the functionalities, workflows, and rules
the application must support.
o Data Layer: Questions about data storage, access, security, and performance.

 Use Cases, Use Case Specs, and Activity Diagrams

o Use Cases: What are the main scenarios that the application must support?
o Use Case Specifications: What are the detailed steps, preconditions, and
postconditions for each use case?
o Activity Diagrams: What are the workflows and processes involved? How do users
interact with the system?
o Models: What are the steps in each process, and how do they interconnect?
 o Page Designs: What are the key design elements, layout, and user interface
components?

Question 5:

As a Business Analyst, What Elicitation Techniques you are aware of? (BDRFOWJIPQU)

Answer:

 Brainstorming:

Brainstorming can be done either individually or in groups. The ideas collected can then be reviewed
analysed and where relevant included within the system requirements. Ideas can come from what
users / stakeholders have seen (example: at software exhibitions) or experienced elsewhere (eg
before they joined the present organization).

 Document Analysis:

Reviewing existing documentation, such as reports, manuals, policies, or previous project

documents, to gather relevant information and requirements.

Document Analysis is one of the compulsory elicitation techniques for any project.

 Reverse Engineering:

If the software for an existing system has little or outdated documentation and it is necessary to
understand what the system actually does, reverse engineering is an elicitation technique that can
extract implemented requirements from the software code.

There are two general categories of reverse engineering:

o Black Box Reverse Engineering: The system/product is studied without examining its internal
structure.
o White Box Reverse Engineering: The inner workings of the system/product are studied.

Reverse Engineering is generally done for Migration Projects.

 Focus Groups:

Structured discussions with a selected group of stakeholders or users to gain a deeper understanding
of their needs, expectations, and opinions on specific topics.

 Observations:

This technique involves watching stakeholders perform their tasks to understand their workflows,
processes, and challenges firsthand.

 Workshops:

Engaging sessions to gather requirements, align on priorities, and validate findings. Different types of
workshops may include brainstorming, JAD (Joint Application Development), and review sessions.

 Joint Application Development:

The Joint Application Development (JAD) technique is an extended, facilitated workshop. It involves
collaboration between stakeholders and systems analysts to identify needs or requirements in a
concentrated and focused effort.

 Interviews:

Conducting one-on-one or group interviews with stakeholders to gather detailed information about
their needs, expectations, and experiences. Interviews can be structured, semi-structured, or
unstructured.

 Prototypes:

Creating visual models, mock-ups, or prototypes of the system or product to help stakeholders
visualize the solution and refine requirements through feedback.

 Questionnaires/Surveys:

Distributing structured questionnaires or surveys to gather information from a large group of

stakeholders, especially when stakeholders are dispersed or when the requirements need to be
validated on a broad scale.

 Use Case Analysis:

Developing use cases that describe how users will interact with the system to accomplish specific
goals. This technique helps identify functional requirements, user interactions, and scenarios.

Question 6:

Which Elicitation Techniques can be used in this Project and Justify your selection of Elicitation
Techniques?

Prototyping

Use case Specs

Document Analysis

Brainstorming

Fertilizers, seeds, pesticides details from the manufacturers and should be able to display them to
the Farmers.
To gather the business requirements from the client, you went to SOONY and met Mr. Henry. When
Mr. Henry was asked about the project and what are they expecting from the project, Mr. Henry
stated that he is expecting to have a login for all its users (fertilizers, seeds, pesticides manufacturers
and Farmers), a product catalogue of fertilizers, seeds, pesticides, a search option to search for
products, payment process, and delivery tracking.

After doing the stakeholder analysis, you have found out that Peter, Kevin, Ben are the key
stakeholders and you have scheduled an appointment to meet them. After meeting with them and
trying to gather the stakeholder requirements, Kevin said that, a Farmer should be able to browse
through the products catalogue once they visit the website and need to have a search option so that
they can search for any product they need. Peter said that, if a farmer wants to buy any product or
add them to buy-later list, they need to login first using their email id and password. If it is a new
user, then they can create a new account by submitting their email ID and creating a secure
password. Ben added saying that, 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. Kevin mentioned that, a user gets an email confirmation regarding their
order status. A delivery tracker to track the whereabouts of their order.

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 in the application.

Answer:

For the Online Agriculture Product Store project, the following elicitation techniques can be
effectively used:

1. Prototyping

o Visual Understanding: Prototyping helps stakeholders (especially farmers and non-

technical users) visualize the application’s look and feel. Since farmers may not be
familiar with technical aspects, seeing a prototype will make it easier for them to
provide feedback on the design, layout, and functionality.

o Early Feedback: By creating wireframes or interactive prototypes, stakeholders can

interact with a version of the product early on. This helps in identifying any usability
issues, design flaws, or missing features before full-scale development begins,
reducing the risk of costly changes later.

o Alignment on Requirements: It ensures all stakeholders have a shared

understanding of the final product, leading to clearer and more detailed
requirements.

2. Use Case Specifications

o Clear User Interactions: Use case specs define the interactions between users
(farmers, manufacturers, admin users) and the system. Given the different user roles
in this project, use cases will help identify all possible scenarios that need to be
supported, including user goals (e.g., buying seeds, listing products).
 o Detailing Functional Requirements: This technique helps outline each function the
application must perform, including the main success scenarios, alternative flows,
and exception handling, providing clarity to developers and testers.

o Improves Development and Testing: By specifying use cases, the development team
can better understand the required features, and testers can design test cases based
on the documented scenarios.

3. Document Analysis

o Leveraging Existing Information: Reviewing existing documents, such as agricultural

product catalogues, current procurement records, regulations, and any previous
studies related to farmers' challenges, helps understand the context and identifies
the key requirements and constraints.

o Identifying Constraints and Compliance Requirements: It helps uncover legal,

regulatory, and compliance requirements relevant to the agriculture sector, which
the new solution must adhere to.

o Improving Accuracy: Provides a baseline of existing practices and needs, ensuring

that the proposed solution builds on accurate and relevant information.

4. Brainstorming

o Generating Diverse Ideas: Brainstorming sessions can involve stakeholders (like Mr.
Henry, Peter, Kevin, Ben) and project team members to generate ideas and solutions,
especially for features, functionalities, and potential challenges.

o Encourages Stakeholder Engagement: Helps gather varied perspectives, especially

from farmers who have first-hand knowledge of their challenges, ensuring the
solution is well-aligned with their needs.

o Identifies Risks and Opportunities: Through open discussions, potential risks,

opportunities, and innovative ideas can surface, allowing for a more comprehensive
approach to requirements gathering.

Based on the information gathered from Mr. Henry, Peter, Kevin, and Ben, here are the identified
business requirements (including stakeholder requirements):

Additional Business Requirements

BR003 – All users (farmers, manufacturers) should have a login functionality. New users should be
able to create an account by providing their email ID and creating a secure password.

BR004 – Farmers should be able to browse the product catalogue without logging in.
BR005 – Farmers should be required to log in to add products to their "buy-later" list or to make a
purchase.

BR006 – The application should provide a secure and easy-to-use payment gateway that includes
multiple payment options: Cash-on-Delivery (COD), Credit/Debit Card, and UPI.

BR007 – Farmers should receive an email confirmation regarding their order status after a purchase
is made.

BR008 – The application should have a delivery tracking feature to allow farmers to track the
whereabouts of their orders.

BR009 – The application should have a user-friendly product catalogue that displays all available
products in fertilizers, seeds, and pesticides.

BR010 – The application should provide a search functionality for users to find specific products
based on their needs (e.g., product type, name, or manufacturer).

Question 7:

Make suitable Assumptions and identify at least 10 Business Requirements.

Answer:

Identified Business Requirements:

1. BR001 – Farmers should be able to browse and search for available products (fertilizers,
seeds, pesticides) in the product catalogue without logging in.

2. BR002 – Manufacturers should be able to upload and display their products (fertilizers,
seeds, pesticides) on the platform, including product details, pricing, and stock availability.

3. BR003 – The application should provide user login and account management functionality
for farmers and manufacturers, with the ability to create accounts using an email ID and
password.

4. BR004 – The system should support multiple payment options, including Cash-on-Delivery
(COD), Credit/Debit cards, and UPI, to ensure flexibility for farmers.

5. BR005 – Farmers should receive automated email confirmations for order placement,
payment status, and delivery tracking.

6. BR006 – The application should feature a delivery tracking system that allows farmers to
monitor the location and status of their orders in real-time.

7. BR007 – The application should provide a secure payment gateway that complies with
industry standards, protecting users’ financial and personal data.

8. BR008 – The application should be optimized for both web and mobile devices, ensuring
ease of access for farmers and manufacturers using smartphones.

9. BR009 – The platform should offer multi-language support to accommodate users who
speak different regional languages, making it accessible to non-English speakers.

10. BR010 – The system should allow farmers to add products to a "buy-later" list after logging
in, which can be accessed for future purchases.
Question 8:

List your assumptions

Answer:

Assumptions:

To frame relevant business requirements, the following assumptions are made based on the given
case study:

1. Target Users: The primary users of the application will be farmers (mostly from rural areas)
and agricultural product manufacturers (fertilizers, seeds, and pesticides).

2. Device Usage: Farmers are likely to access the platform primarily via smartphones, while
manufacturers may use both web and mobile platforms.

3. Geographical Scope: The application will serve farmers in remote areas, where internet
connectivity may be unstable.

4. Logistics: There will be third-party delivery partners responsible for delivering agricultural
products to farmers.

5. Payment Systems: Farmers prefer multiple payment methods such as cash on delivery
(COD), mobile wallets, and bank transfers.

6. Language Barrier: Many farmers may not be proficient in English, so local language support
will be needed.

7. Technical Literacy: Farmers have minimal experience with digital platforms, so the system
must be extremely user-friendly.

8. Compliance: The platform must comply with government regulations related to agriculture,
trade, and e-commerce.

9. Inventory Management: Manufacturers will need an interface to update stock, product

details, and pricing.

10. Product Support: There will be a customer support system to help users navigate and resolve
issues on the platform.

Question 9:

Give Priority 1 to 10 numbers (1 being low priority – 10 being high priority) to these Requirements
after discussions with the stakeholders

Req ID Req Name Req Description Priority

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

BR002 Manufacturers upload their Manufacturers should be able to 8

Products upload and display their products in
 the application

Once the requirements are finalized, as a business analyst, one of the major roles is to act as a liaison
between the client and the project team. To gather the requirements correctly from the client side
and then to deliver those requirements to the project team in a way they understand.

To make the project team understand the requirements, you need to convert those requirements
into UML diagrams and screen mock-ups.

Answer:

Req ID Req Name Req Description Priority

BR001 Farmer Search for Farmers should be 8
Products able to search for
available products in
fertilizers, seeds,
pesticides
BR002 Manufacturers Upload Manufacturers should 8
their Products be able to upload and
display their products
in the application
BR003 User-Friendly The application must 10
Interface be easy to use for
farmers with minimal
technical skills
BR004 Multi-language The platform must 7
Support support multiple
languages, especially
regional languages
BR005 Payment Gateway The platform must 9
Integration support multiple
payment options
(online payments,
COD, mobile wallets)
BR006 Order Placement and Farmers should be 9
Tracking able to place and track
orders through the
platform
BR007 Logistics and Delivery The platform must 9
System integrate with logistics
providers for
deliveries to remote
locations
BR008 Communication Enable 6
Channel communication
between farmers and
manufacturers for
product inquiries
BR009 Inventory Alerts and Notify manufacturers 5
Notifications about low stock and
 farmers about product
updates, discounts,
and changes
BR0010 Customer Support and Provide customer 6
Help Center support options for
farmers to resolve
queries and issues

Question 10:

Draw use case diagram

Answer:
Question 11:

Prepare use case specs for all use cases.

Answer:
(1)

Use case spec: Login

Description: To enter Username & Password

Actors: Farmers, website

Preconditions: Active internet connection, browser compatibility

Postconditions: Home page should be displayed

Basic flows: Username and Password are Correct

Alternate flow: Password is wrong

User name is wrong

Username and password are wrong

Exceptional flow: forget password

Forget username

Assumptions: users have basic computer knowledge and English

Constraints: Usernames cannot be special character

Dependents: user should be pre-registered

Inputs: Username and Password

Output: status flag or error code.

Business rules: User should use valid Email id & password should have special character

(2)

Use case spec: Shop Products

Description: To add to products to cart and purchase

Actors: Farmers, website

Preconditions: Active internet connection to browse through different products

Postcondition: Able to add items to cart and directed to payment page.

Basic flow: Items selected are correctly captured by the system

Alternative flow: Wrong items captured while adding to cart.

Exceptional flow: While adding to cart different pages pops out.

Not directing to payment page

Assumptions: Users should know how to add product to cart.

Constraints: At least 2 products to be added to cart.

Dependencies: The product should be available with the company.

Input: The chosen product

Output: The order gets through to the payment site.

Business rules: Debit cards/ Credit cards/ UPI for payment rules and regulations.

(3)

Use case spec: New user Registration

Description: To get registered and email verified

Actors: Farmers, website

Preconditions: Active internet connection, To have valid Email account

Postconditions: Able to register and login to website

Basic flows: OTP verification and Email verification done

Alternate flow: OTP is not being received

Verification email is not being received

Exceptional flow: No valid Email account

Mobile No. not working

Assumptions: Users have basic mobile knowledge, have a valid Email account

Constraints: Both mobile and Email need to be verified to do the registration

Dependents: User should have Email and number to be linked

Inputs: OTP and Email

Output: Registration done and able to login to the website

Business rules: User should use valid Email id & password should have special character

(4)

Use case spec: Upload products

Description: To upload products and refill stock

Actors: Manufacturers, website

Preconditions: Stock replenishment data to be generated for easy controlling of website

Postconditions: Stock is available all the time for demanded products

Basic flows: Stock information is provided correctly

Alternate flow: Stock information is not provided correctly

Exceptional flow: Takes more time show stock data

No control on the data

Assumptions: Manufacturers gets notified about the stock of products.

Constraints: Stock cannot be refilled for just one product

Dependents: If order is received the stock should meet order requirements

Inputs: Refill notification goes to manufacturer

Output: Product available or not available intimation

Business rules: Once all old stock is finished then only new stocks will be refilling.

Question 12:

Activity diagrams
Answer: