The document discusses several diagrams used in a project's system design: an entity relationship diagram to understand how database entity sets relate; a sequence diagram to show lifelines, processes, objects and message exchanges; level 0 and level 1 dataflow diagrams to show broader and more detailed data flows. An activity diagram represents control flow among activities and a use case diagram represents system interaction scenarios with people/organizations. These diagrams were used to design the logical structure, processes, and interactions of the project system.

1. Group 1
Project 1

2. System Design

3. Entity Relationship Diagram
 Help us to understand the relationship or how the entity sets
relate to one another in the database.
It also help us to understand how the logical structure of the
database display .

4. ER DIAGRAM

5. Sequence Diagram
Because we need to know the lifelines of the project, the
processes(Sales, payment, login, logout) and the
objects(manager, employee, customers) that live simultaneously,
and the messages exchanged among them to perform a function
before the lifelines end, we used a Sequence Diagram

7. Dataflow Diagram
Level 0
This level help us to get a broader view of how the data flow but
offers little details.

9. Dataflow Diagram
Level-1
Though we still get a general view, but able to get more details compared
to Level-0.
In this level, we were able to break down single process node into sub
processes leading to additional data flow and data store

11. Activity Diagram
This diagram help us to represent and understand the flow of control among
the activities in the system

12. Sales Activity Diagram

13. Use Case Diagram
This diagram is used as a team to represent;
Scenarios in which the system interact with people, organization. In this
case, employee, manager, supplier, customres.

16. Thank You
Group 1