Search for the Right Document
-
Planning and Strategy
-
Requirements
-
- Customer Feedback Report
- Capacity Planning Report
- Stakeholder Input Record Example
- List of Customer Journeys
- Reverse Engineering: Legacy Inventory Management System
- Task Analysis: Customer Support Ticketing System
- Requirements Workshop: Employee Onboarding System
- Mind Mapping Session: Mobile Travel Planning App
- SWOT Analysis: New Food Delivery App
- Storyboarding Session: Mobile Health & Fitness App
- User Story Mapping Session: Online Grocery Shopping Platform
- Focus Group: Requirements Gathering for Fitness Tracking App
- Prototyping Session Example: E-Commerce Website
- Document Analysis Example: Hospital Management System Requirements
- Observation Session: Warehouse Operations
- Survey: E-Learning Platform Requirements
- Workshop Session Example: Requirements Gathering for Mobile Banking App
- Interview Session Example: Requirements Gathering for CRM System
- Event Storming Session: Retail Order Management System
- Show all articles ( 4 ) Collapse Articles
-
- Customer Requirement Document (CRD)
- Customer Journey Map
- Internal Stakeholder Requirement Document (ISRD)
- Internal System Use Case Example: CI/CD System
- User Stories & Acceptance Criteria
- Technical Specification Document Example
- BDD Scenarios Example for User Login
- Non-Functional Requirements Example
- Functional Requirements Specification Example
- Use Case Example: User Login
-
-
Communication
-
Design
- Functional Specification for Inventory Management Workload
- Technical Specification for Inventory Management System
-
- Overview of Design Diagrams
- High-Level System Diagram Standards
- User-Flow Diagram Standards
- System Flow Diagram Standards
- Data-Flow Diagram (DFD) Standards
- Sequence Diagram Standards
- State Diagram Standards
- Flowchart Standards
- Component Diagram Standards
- Network Diagram Standards
- Deployment Diagram Standards
- Entity-Relationship Diagram (ERD) Standards
- Block Diagram Standards
-
Operations
-
-
- Creating a Visualization Dashboard Guide
- Business Outcome Metrics Dashboard Guide
- Trace Analysis Dashboard
- Dependency Health Dashboard
- Guidelines for Creating a Telemetry Dashboard
- Guidelines for Creating a User Behavior Dashboard
- Improvement Tracking Dashboard
- Customer Status Page Overview
- Executive Summary Dashboard Overview
- Operations KPI Dashboard Example
- Stakeholder-Specific Dashboard Example
- Business Metrics Dashboard Example
- System Health Dashboard Example
- Guide for Creating a Dependency Map
-
-
-
- Event Management Policy Example
- Incident Management Policy
- Problem Management Policy
- Example Training Materials for Escalation
- Runbook Example: Incident Management with Escalation Paths
- Escalation Path Document Example
- Incident Report Example: Failed Deployment Investigation
- Incident Playbook Example: Investigating Failed Deployments
- Contingency Plan for Service Disruptions
-
-
-
Testing
-
Development
< All Topics
Print
Entity Relationship Diagram Example for a E-commerce System
PostedNovember 16, 2024
UpdatedNovember 16, 2024
ByKevin McCaffrey
Entities and Relationships:
- Entity: User
- Attributes:
- UserID (Primary Key)
- FirstName
- LastName
- Email (Unique)
- Password
- CreatedAt
- Relationships:
- A user can have many orders (One-to-Many relationship with the Order entity).
- Attributes:
- Entity: Product
- Attributes:
- ProductID (Primary Key)
- ProductName
- Description
- Price
- StockQuantity
- CategoryID (Foreign Key)
- Relationships:
- A product belongs to one category (Many-to-One relationship with the Category entity).
- A product can be included in many order items (Many-to-Many relationship with the Order entity through the OrderItem entity).
- Attributes:
- Entity: Category
- Attributes:
- CategoryID (Primary Key)
- CategoryName
- Relationships:
- A category can have many products (One-to-Many relationship with the Product entity).
- Attributes:
- Entity: Order
- Attributes:
- OrderID (Primary Key)
- UserID (Foreign Key)
- OrderDate
- TotalAmount
- Status
- Relationships:
- An order belongs to one user (Many-to-One relationship with the User entity).
- An order can contain multiple products (Many-to-Many relationship with the Product entity through the OrderItem entity).
- Attributes:
- Entity: OrderItem
- Attributes:
- OrderItemID (Primary Key)
- OrderID (Foreign Key)
- ProductID (Foreign Key)
- Quantity
- UnitPrice
- Relationships:
- An order item belongs to one order (Many-to-One relationship with the Order entity).
- An order item refers to one product (Many-to-One relationship with the Product entity).
- Attributes:
Diagram Layout Description
- User Entity: Positioned at the top-left of the diagram, connected to the Order entity with a “One-to-Many” relationship.
- Order Entity: Positioned in the center, connected to the OrderItem entity with a “One-to-Many” relationship and to the User entity.
- OrderItem Entity: Positioned below the Order entity, connecting to both Order and Product entities with “Many-to-One” relationships.
- Product Entity: Positioned at the top-right, connected to the OrderItem entity and to the Category entity with a “Many-to-One” relationship.
- Category Entity: Positioned above the Product entity, connected to the Product entity with a “One-to-Many” relationship.
Example Relationships
- User – Order: A user can place multiple orders.
- Order – OrderItem: Each order can contain multiple order items.
- OrderItem – Product: Each order item refers to a specific product.
- Product – Category: Each product belongs to one category.
Table of Contents