Skip to content

Sprint 2 Diagrams

Tnguyen0525 edited this page Mar 8, 2025 · 6 revisions

Class Diagram:
This diagram defines the structure of EZ-WATCH e-commerce system by illustrating different classes such as Guest, User, Buyer, Seller, Admin, Product, Order, and Search. It specifies their attributes, methods, and relationships, highlighting user roles and their interactions with products and orders.
image

Use Case Diagrams:
The Admin, Guest, and User use case diagrams illustrate the different interactions within the e-commerce system, where admins manage users and transactions, guests browse and register, and users gain access to purchasing and product management features. These diagrams define role-specific functionalities and system access
image

image

User Story 1 Sequence Diagram:
This illustrates the process of browsing and filtering products, showing how the system fetches and updates product lists based on user interactions.

User Story 1 Activity/State Diagram:
The diagram represents the states a guest goes through while browsing, searching, or filtering products, leading to either continued browsing or user registration.

User Story 2 Sequence Diagram:
This diagram outlines the registration and login process, showing interactions between a guest, user, and admin for account approval.

User Story 2 Activity/State Diagram:
This diagram diaplys structured flowchart of the registration and login process, covering input validation and access to personalized features upon successful login.

User Story 3 Sequence Diagram:
This Diagram displays the process of filtering products, where user inputs (such as budget, brand, and item ID) affect product display.

User Story 3 Activity/State Diagram:
This diagram Illustrates the states involved in product search and filtering, ensuring users can refine their search before viewing detailed product information.

User Story 4 Sequence Diagram:
This diagram details the process of a user selecting a product, prompting the system to query the database for product details and return the information. If the product is not found, the system displays an error message.

User Story 4 Activity/State Diagram:
This diagram represents the flow of retrieving product details, where the system fetches data from the database and either displays product information or an error message if the product is unavailable.

User Story 5 Sequence Diagram:
This sequence diagram outlines the shopping cart process, showing how a user adds an item to the cart, updates the system, views the cart, and proceeds to checkout.

User Story 5 Activity/State Diagram:
The diagram below visually represents the states a user transitions through when adding an item to the cart, verifying cart details, and completing checkout.

Architecture Diagram:
This diagram provides an overview of the website structure, showing how different pages like the Home, Shopping, Account, and Login pages are interconnected and interact with the browser and user registration module.

Component Diagram:
This Diagram shows the system’s architecture, breaking it into frontend, backend API, and external services. The frontend handles UI interactions, the backend manages API calls, and external components like the SQL database and payment service handle transactions and data storage.

Clone this wiki locally