
π Student Projects (College Reports) Β· Data Flow
Order data flowing between the customer, seller, payment gateway, courier and the shop's data stores.
Drawing diagramβ¦
Level 1 data flow diagram for an online shopping system: the customer browses and places orders; the seller adds products; processes are manage catalogue, manage cart, place order, process payment and arrange delivery; the payment gateway returns payment status and the courier returns delivery updates; data stores are products, customers, orders and payments.
flowchart LR
subgraph EXT ["π External Entities"]
C["Customer"]
SL["Seller"]
PG["Payment Gateway"]
CR["Courier"]
end
subgraph PROC ["βοΈ Core Processes"]
P1["1.0 Manage catalogue"]
P2["2.0 Manage cart"]
P3["3.0 Place order"]
P4["4.0 Process payment"]
P5["5.0 Arrange delivery"]
end
subgraph STORE ["ποΈ Data Stores"]
D1[("D1 Products")]
D2[("D2 Customers")]
D3[("D3 Orders")]
D4[("D4 Payments")]
end
SL -->|"1. Product details"| P1
P1 -->|"2. Product record"| D1
D1 -->|"3. Catalogue"| C
C -->|"4. Items chosen"| P2
P2 -->|"5. Cart"| P3
D2 -->|"6. Address"| P3
P3 -->|"7. Order record"| D3
P3 -->|"8. Reduce stock"| D1
P3 -->|"9. Amount due"| P4
P4 -->|"10. Payment request"| PG
PG -->|"11. Payment status"| P4
P4 -->|"12. Payment record"| D4
P4 -->|"13. Paid order"| P5
P5 -->|"14. Pickup request"| CR
CR -->|"15. Delivery updates"| P5
P5 -->|"16. Order status"| CWho uses a college library system and what each of them can do: members, the librarian and the system administrator.
The database of a library system: books and their copies, authors, members, loans, reservations and fines, with keys and cardinality.
How data moves through a library system: members and the librarian, the main processes, and the data stores they read and write.
The main classes of a library system with attributes, methods and UML relationships.
The steps when a member borrows a book: checks, loan record and the copy status update.
What students, examiners and the administrator do in an online examination system.