0% found this document useful (0 votes)
10 views9 pages

ER, Context, Data Flow

The document discusses the structural and functional modeling of an eye optical management system using entity-relationship diagrams and data flow diagrams. It describes the key entities, attributes, relationships in the ERD as well as the external entities, processes, data flows, and data stores in the level 1 DFD for placing an order.

Uploaded by

arunkumar1100155
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
0% found this document useful (0 votes)
10 views9 pages

ER, Context, Data Flow

The document discusses the structural and functional modeling of an eye optical management system using entity-relationship diagrams and data flow diagrams. It describes the key entities, attributes, relationships in the ERD as well as the external entities, processes, data flows, and data stores in the level 1 DFD for placing an order.

Uploaded by

arunkumar1100155
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/ 9

EYE OPTICAL MANAGEMENT SYSTEM

SOFTWARE ENGINEERING LAB


SLOT: L13+ L14
VL2023240505809

SUBMITTED BY:
ARUN.U
21BCE3187

1|Page
Assessment – II

1. Analyse the structural modelling using Entity-Relationship


Diagram.

Introduction :

An Entity-Relationship Diagram (ERD) is a visual representation of the


core components (entities) of a system and the ways they are
interconnected (relationships).
In the context of your Eye Optical Management System, an ERD would
provide a blueprint of your database structure. It helps visualize how
data about customers, products, orders, suppliers, sales, and more are
organized and linked together.

Components and Relationships:

Entities:

 Optical shop portal (Portal_url, Portal_name)


 Customer: (customerID, name, address, contact info)
 Eye Power Specifications: (Customer_id, left eye, right eye)

 Admin: (Admin_id, Admin name)


 Product: (productID, name, brand, price, Current stock)
 Shopping Cart: (Purchase_id, Customer_id, Product_id, Quantity,
Unit price, Total price, Supplier id)
 Supplier: (supplierID, name, contact info,Email, Address)
 Sale: (Sale_id, Product_id, Sale amount)
 Payment: (Transaction_id, Total amount, Date)
 Receipt: (Receipt_id, Receipt amount)
 Delivery: (DeliveryID, Customer_id, Receipt_id, shippingAddress,
deliveryStatus, deliveryDate)

2|Page
 Employee: (EmployeeID, Name, Address, Contact, Department)
Relationships:
 Customer, Employee, Admin login Optical shop Portal (M:1)
 Admin add/view Supplier, Employee (1:M)
 Customer makes Shopping Cart (1:1)
 Customer views Product (1:M)
 Customer updates Eye Power Specifications (1:M)
 Eye Specifications updated to Product inventory(M:1)
 Shopping cart contains Products (1:M)
 Employee updates Product inventory (M:M)
 Employee updates Sale (M:M)
 Shopping cart checked out for Payment (1:1)
 Payment Generates Receipt(1:1)
 Payment updates Product(1:M)
 Receipt Processes Delivery (1:1)

Advantages and Disadvantages of the ER of my project

Advantages:

Clarity: Visualizes the database structure, making it easier to understand


for developers and stakeholders.
Database Design Foundation: Acts as a guide for creating your database
tables and columns.
Communication Aid: Facilitates discussions about the system's data
requirements.
Maintenance: An accurate ERD assists in making future database
modifications as needed.

Disadvantages:

Complexity: ERDs for large systems can become very intricate.

3|Page
Focus on Structure: Doesn't show process flow
Potential for Oversimplification: Real-world systems often have more
complex relationships that may be difficult to model simply in an ERD.

2. Describe the functional modelling using Context Flow Diagram


and Data Flow Diagram.

Context Flow Diagram:


Central System: "Eye Optical Management System"

External Entities:

4|Page
 Admin
 Employee
 Customer
 Payment Gateway
 Delivery Service

Initial Sketch:

Data Flow Refinement

Optical Shop Portal: This is primarily an interface, not a separate entity.


The CFD mainly focuses on external interactions.
Admin: Manages stock (interactions with the supplier), sales analysis
Employee: Updates products (catalog), processes orders, customer
care.

5|Page
Data Flow Diagram:
Level 1 DFD: Place Order

Processes:

Customer Browses Catalog (1.0):

6|Page
Input: Product Data
Output: Product Selection (to be added to cart)
Customer Adds to Cart (1.1):

Input: Product Selection, Customer Data (if not already logged in)
Output: Updated Shopping Cart Data
Customer Confirms Order (1.2):

Input: Shopping Cart Data, Delivery Address, Payment Method


Output: Order Details
Validate Order Details (1.3):

Input: Order Details


Output: Validated Order / Error Messages (if invalid)
Process Payment (1.4):

Input: Validated Order, Payment Method


Output: Payment Status (Success/Failure)
External: Payment Gateway
Generate Receipt (1.5):

Input: Validated Order, Payment Status (Success)


Output: Receipt Data
Update Inventory (1.6):

Input: Validated Order (products purchased)

7|Page
Output: Updated Inventory Data
Data Stores:

Product Data: Stores details of available products.


Customer Data: Stores customer information (name, address, etc.)
Shopping Cart Data: Temporarily stores products the customer selects.
Order Data: Stores confirmed order details.
Inventory Data: Stores current stock levels for products.
Receipt Data: Stores receipt details for successful orders.

After every purchase the inventory will be tracked and reported to admin
and Supplies were ordered and updated accordingly.

8|Page
9|Page

You might also like