60 likes | 191 Views
This guideline outlines the essential components for creating a class diagram based on your project scenario. It includes an introduction to the scenario from which to draw your main entities, such as students, courses, and departments. You will also identify classes, their corresponding attributes, and operations. This guide emphasizes the importance of accurately mapping relationships between classes, including associations, compositions, and aggregations, as well as specifying multiplicities such as 1..* or 0..* to effectively represent the environment's structure.
E N D
WEEK 3 – PRESENTATION GUIDELINE Class Diagram Modeling
Expected Content • Introduction (Scenario) • Main Entities of the Environment • Classes, Attributes & Operations • Class Diagram
Introduction (Scenario) • This section give a description of the scenario that you want to create class diagram for. The scenario comes from the project case of each individual group. • Recall sample scenario discussed in class
Main Entities of the Environment • This part should discuss, the main entities extracted from the scenario described above (in the previous slide). • By entities, we refer to things that we want to store information about them. • Example entities can be: students, courses, projects, department, managers, etc.
Classes, Attributes & Operations • In this section, you should identify: • Classes, e.g. student • Attributes making the classes e.g. student name, student age, etc. • Operations associated with the classes, e.g. resister student(), updatestudentrec(), etc.
Class Diagram • Last step draw class diagram, indicating the • relationships (association, composition and aggregation) between the classes • multiplicities between the classes, i.e. (1..*, 0..*, etc.)