Scribd
Upload
7 views14 pages

Bean & Bear Coffee Shop Website Requirement Analysis (2) (3)

The document outlines the requirements for the digital transformation of Bean & Bear Coffee Shop, emphasizing the need for an online platform to enhance customer experience and operational efficiency. Key features include an online menu, ordering system, event updates, and customer accounts, aimed at addressing current limitations such as long wait times and limited information. The analysis includes functional requirements, UML diagrams, and a data flow model to illustrate the system's architecture and interactions.

Uploaded by

nkunalotricia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views14 pages

Bean & Bear Coffee Shop Website Requirement Analysis (2) (3)

The document outlines the requirements for the digital transformation of Bean & Bear Coffee Shop, emphasizing the need for an online platform to enhance customer experience and operational efficiency. Key features include an online menu, ordering system, event updates, and customer accounts, aimed at addressing current limitations such as long wait times and limited information. The analysis includes functional requirements, UML diagrams, and a data flow model to illustrate the system's architecture and interactions.

Uploaded by

nkunalotricia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Where Innovation Meets Functionality

Number of team: 3 People

Name of team: Creative Pulse Movement

Team Leader: Cynthia Panzu – Project Manager ST10174327

Team Members:

Philadelphia Lotricia Nkuna – Business Analyst ST10304249

Mendes Sithole – Software Developer ST10332172


Contents
Bean & Bear Coffee Shop Website Requirement Analysis........................................5
What's Happening at Bean & Bear (The Problem Domain)........................................5
Solution Domain..............................................................................................5
Why This Matters for Bean & Bear (Functional requirement specs)............................6
Functional Requirements Table.............................................................................6
UML Use Case Diagram...................................................................................7
Primary Systems:.............................................................................................7
Human Actors:................................................................................................7
Mechanical System Actors:...............................................................................7
Logical System Model – Data Flow Diagram..................................................12
Overview......................................................................................................12
Key Elements........................................................................................12
Processes..............................................................................................13
Bean & Bear Coffee Shop Website Requirement Analysis

This document presents a formal analysis of the requirements for the digital
transformation of Bean & Bear Coffee Shop, focusing on the transition from traditional
operational models to a comprehensive online platform.

What's Happening at Bean & Bear (The Problem Domain)

Bean & Bear Coffee Shop works mainly through in-person communication and uses a
traditional way of taking orders. While this method creates a personal experience for
customers, it also limits the shop's ability to grow and work well.

 Lines are Long: When its busy, people have to wait a while to order. This can
make some customers unhappy.
 Information is Limited: If you're not in the shop, you don't really know what
they're selling, or what events they have planned or promotions they have.
 Growing is Hard: They want to reach more people, but they're limited by how
many people can physically come into the shop.
 They're Missing Out Online: Other coffee shops have websites and online
ordering, and Bean & Bear is falling behind.

Solution Domain

To fix these issues, they need a good website. Think of it as an online version of their
shop, making things easier for both customers and staff:

 A Great Online Menu: Customers should be able to see all their drinks, food,
and merchandise with pictures and descriptions.
 Online Ordering: People should be able to order from their phones or
computers and pay securely. This will help with those long lines!
 Event Updates: A place to post upcoming events, specials, and promotions.
 Customer Accounts: Customers should be able to save their favorite orders
and see their order history.
 Easy Online Payments: Safe and secure payment options for online orders.

Why This Matters for Bean & Bear (Functional requirement specs)

By creating a website, Bean & Bear can:

 Build a loyal customer base.


 Make customers happier by offering convenience.
 Run their business more efficiently.
 Reach a wider audience.
 Compete with other coffee shops that are already online.
 Build a stronger community around the coffee shop.

Functional Requirements Table

Participant (Active Function of the System Participant (Passive


Actor) Actor)

Customer Browse Menu Staff


Customer Search Menu System
Customer View Item Details System
Customer Place Order Staff
Customer Customize Order System
Customer View Order Summary System
Customer Select Pickup/Delivery Staff
Customer Manage Order Staff
Customer Register Account System
Customer Login System
Customer Update Profile System
Customer View Order History System
Customer Leave a Review Staff
Customer Initiate Payment Payment Gateway
Customer Select Payment Method Payment Gateway
Customer Enter Payment Details Payment Gateway
Payment Gateway Receive Payment Customer
Confirmation
Email Service Send Order Confirmation Customer
Staff Manage Menu Customer
Staff Add menu Customer
specials/promos
Staff View Orders Customer
Staff Update Order Status Customer

UML Use Case Diagram

Primary Systems:

 Customer Interface System


 Order Management System
 Administrative System
 Payment Processing System

Human Actors:

 Customer
 Staff Member

Mechanical System Actors:

 Payment Gateway
 Email Notification System
Class diagram table

Entity Name Properties of Entity (UML Class) Related to


(UML Class)
Customer  customerId(int, Auto-Increment) Order, Account,
 name (string - 30 characters) Review
 address (string-60 characters)
 email (string - 50characters)
 phone (20- characters)
Account  AccountId (int, Auto-Increment) Customer
 CustomerId (int - FK)
 Username (string- 50 characters)
 password_hash (string-255 characters)
 account_status Enum ('Active', 'Inactive',
'Suspended', 'Blocked')

Order  orderId (int, Auto-Increment) Customer,


 customerId (int - FK) OrderItem, Staff,
 order_date (Datetime) Payment
 order_time (Time)
 total_amount (Decimal (10, 2))
 order_status Enum ('Pending',
'Processing', 'Delivered', 'Cancelled',
'Refunded')
 pickup_delivery Enum ('Pickup',
'Delivery')
 delivery_address (string –60 characters)
 payment_id (int -FK)
OrderItem  OrderItemId (int, Auto-Increment) Order, MenuItem
 OrderId (int, FK)
 MenuItemId (int, FK)
 quantity (int)
 subtotal (Decimal-(10, 2))
MenuItem  menuItemId (int, Auto-Increment) OrderItem,
 Description (string – 255 characters) Review
 Price (Decimal -(10, 2))
 Category (string –50 characters)
 Availability (Boolean)
Review  reviewId: (int, Auto-Increment) Customer,
 customerId:(FK) MenuItem
 menuItemId: (int – FK)
 rating: int
 comment: (string – 255 characters)
 review_date (datetime)
Payment  PaymentId (int, Auto-Increment) Order
 orderId (int - FK)
 payment_method (string – 50
characters)
 payment_date (datetime)
 payment_amount (Decimal-(10, 2))
 transaction_status (Enum ('Success',
'Failed', 'Pending'))
Staff  staffId (PK, Auto-Increment) Order, MenuItem
 name (string – 100 characters)
 role (string – 50 characters)

Event  eventId (int, Auto-Increment)


 eventName (string – 255 characters)
 eventDate (Date)

Class diagram
Logical System Model – Data Flow Diagram

Overview
This Data Flow Diagram (DFD) represents the logical system model for an
online ordering system, like the one for Bean & Bear Coffee Shop. It
demonstrates how data moves between users, processes, and data
stores, from placing an order to receiving confirmation.

Key Elements
Inputs

These are the data or actions provided by the user:

 Customer Profile Info – name, email, address, preferences.

 Menu Selections – selected items for the order.


 Payment Details – card information or digital payment.

Processes
1. Profile Updates

o Users update their profile details.

o Data is saved to the Profile Data store.

o A Receipt is generated as confirmation.

2. Place Order

o The user selects products from the menu.

o Order information is sent to the Order data store.

o It also retrieves profile data for delivery info.

3. Verify Payment

o This process checks the user’s payment details.

o Payment is validated before proceeding.

4. Send Confirmation

o Triggered after successful payment.

o Sends both a Receipt and a Confirmation Email to the user.

o Updates the Order Status.

Data Stores

 Profile Data – stores user information.

 Order – stores placed order data.

 Order Status – stores order processing stages like “In Progress,” “Out
for Delivery,” etc.
Outputs

What the system sends back to the user:

 receipt – for profile update or order confirmation.

 Confirmation Email – confirms that the order is being processed.

 Updated Order Status – informs the user of real-time order tracking.

Relationships & Flow

 Each arrow in the DFD represents the flow of data.

 Each process is responsible for transforming specific inputs into


valuable outputs.

 Processes interact with data stores to read or write data as needed.

 The system is user-centric, focusing on smooth user interaction and


fast feedback.

You might also like