The use case diagram shows how the system is used in real-world scenarios, which functionality needs to be implemented, and which actors interact with the system.
The class diagram makes the system structure and relationships between its components easier to understand.
The sequence diagram shows interactions between objects and how they exchange messages to complete a specific task. It also helps identify interaction issues and opportunities to improve system performance.
I started the database design with a logical data model, defining entity attributes, primary and secondary keys, and relationships between entities.
The physical data model defines the final database structure, data types and field constraints, while supporting efficient memory usage and database performance within a relational model.
