1.3. Suggested Case Scenario

🛒 Project: Online Grocery Ordering System (Mini MVP) Problem Statement: A local grocery chain wants to launch a simple web-based system where customers can view available products, add them to a cart, place an order, and schedule home delivery.

This chunk outlines the main project, which is to create an Online Grocery Ordering System. The goal is to develop a web-based platform for a local grocery chain, enabling customers to browse products, select items, place orders, and arrange for home delivery. This system aims to simplify the shopping experience for customers by providing an easy-to-use interface.

Think of this system as a digital version of your favorite grocery store. Imagine being able to sit at home, browse through the aisles, add items to your virtual cart, and have everything delivered to your door without needing to leave the house.

✅ Phase 1: Elicit Requirements 🎯 Tasks: ● Identify stakeholders (e.g., customers, store staff, delivery team, admin) ● Conduct 2–3 mock interviews or prepare stakeholder personas ● Create a stakeholder matrix (with RACI if possible) 📄 Deliverables: ● Stakeholder List & Roles ● Interview Notes / Persona Profiles ● Stakeholder Requirement Summary

In this phase of the project, the business analyst focuses on gathering information necessary to define what the system needs to do. This involves identifying key stakeholders, such as customers who will use the system and staff involved in operations. Mock interviews are useful for understanding stakeholders' perspectives and concerns. A stakeholder matrix can help clarify each stakeholder's responsibilities.

The deliverables for this phase include a list of stakeholders and their roles, notes from interviews, and a summary of the requirements that emerge from stakeholder input.

Imagine planning a family event, where you gather input from everyone involved: who wants what food, how many people are coming, etc. Just as you’d jot down everyone’s preferences to ensure the event satisfies all, a business analyst documents stakeholders' needs to ensure the system meets user demands.

✅ Phase 2: Document Requirements 🎯 Tasks: ● Write 5–8 user stories using INVEST format ● Define acceptance criteria using Gherkin (Given–When–Then) ● Categorize requirements: business, functional, non-functional ● Create a Requirement Traceability Matrix (RTM) 📄 Deliverables: ● User Stories Document ● Acceptance Criteria Sheet ● BRD or FRD (can be simplified) ● RTM in Excel or Table format

In this phase, the goal is to formalize the requirements gathered in the previous phase. User stories, written in the INVEST format (Independent, Negotiable, Valuable, Estimable, Small, Testable), help capture specific functionalities from the user’s perspective. Acceptance criteria define what needs to be met for a feature to work properly. Categorizing requirements helps prioritize them effectively. Lastly, a Requirement Traceability Matrix (RTM) allows tracking of these requirements throughout the project lifecycle to ensure all are addressed.

Think of user stories like recipes for a dish. Each recipe identifies what ingredients (features) are necessary, along with directions (acceptance criteria) to provide a finished meal (software). By organizing these, you ensure the final dish is perfect and meets everyone’s taste.

✅ Phase 3: Model the System 🎯 Tasks: ● Draw Use Case Diagram for order placement ● Draw Activity Diagram for customer flow (browse → checkout) ● Create Wireframes or Mockups (use Draw.io, Balsamiq, or Figma) 📄 Deliverables: ● Use Case Diagram ● Activity Diagram ● Low-fidelity Wireframes (for 2–3 key screens)

Modeling the system involves creating visual aids to better understand how users will interact with the system and how different components will work together. A Use Case Diagram provides a high-level overview of the interactions between users and the system. An Activity Diagram details the step-by-step flow customers will follow, from browsing products to checkout. Wireframes serve as blueprints for key screens to visualize how the final product will look.

Much like creating a map before a trip, these diagrams help visualize the journey of a customer using the grocery ordering system. They highlight all potential routes (choices) customers can take, ensuring that every path leads to a smooth checkout experience.

✅ Phase 4: Test Planning (Optional) 🎯 Tasks: ● Write 3–5 test cases ● Map them to requirements in RTM ● Identify a sample defect (if any) from testing 📄 Deliverables: ● Test Case Table (ID, Steps, Expected Result) ● Defect Log (Optional, for extra challenge)

The test planning phase is crucial to ensure that the system works as intended. Test cases describe specific scenarios to validate whether the functionalities meet the specified requirements. By mapping these test cases to the requirements in your RTM, you can see which aspects have been tested. Identifying defects helps improve the system before release.

Consider this phase similar to a quality check in a factory. Before a product is shipped, it must run through several tests to ensure quality and functionality. Just like ensuring no item leaves damaged, test cases help confirm that software functions flawlessly for users.

✅ Phase 5: Presentation & Review 🎯 Tasks: ● Create a summary presentation (6–8 slides max) ● Include business problem, solution scope, user stories, diagrams, and next steps ● Present your project to peers or mentor (live or recorded) 📄 Deliverables: ● Slide Deck (PDF or PPT) ● Optionally, record a 5-minute video walkthrough

The final phase of the project involves summarizing and presenting the entire analysis process and outcomes. A clear presentation helps convey the business problem, the proposed solution, important user stories, visual diagrams created earlier, and planned next steps. This showcases the culmination of the workflow to peers or mentors for feedback and validation.

Think of a concert where the performers present the whole show after many rehearsals. Similarly, presenting this project is like showcasing your hard work, explaining your solutions and insights to an audience who will appreciate the careful planning that went into it.

📌 Evaluation Criteria (Optional if used for classroom/training) Area Points Requirement 2 Clarity 0 Documentation 2 Quality 0 Diagram 1 Accuracy 5 Practical 1 Feasibility 5 Presentation & Structure 5 Creativity & Detail 5

Evaluation criteria provide a way to assess the project’s outputs and overall effectiveness. Each area, such as clarity, quality, and accuracy, carries points, helping evaluators measure how well the project is executed. This can guide improvement in future projects by highlighting strengths and areas needing more focus.

Imagine being graded on an assignment in school. Each section of your work gets a score based on how clear, detailed, or creative your submission is. Just as grades reflect your understanding, these criteria reflect the strength and effectiveness of the project.

🧠 Bonus Challenge Adapt the same case for a different domain, e.g.:
● Healthcare: Appointment Booking System
● Banking: Personal Loan Application Portal
● Education: Online Course Enrollment Flow

The bonus challenge encourages students to think creatively and apply what they’ve learned to different industries. This task helps reinforce adaptability and understanding of business analysis by reimagining the grocery ordering system in various fields, demonstrating how fundamental requirements can be tailored to different scenarios.

Just as a talented chef can use the same basic ingredients to make different dishes (like pasta, pizza, or bread), students can use the same analytical skills across various industries by adjusting their approach to meet the specific needs of each sector.

--