Class Diagram

Purpose: The purpose of the Class Diagram template is to document the structural aspects of a system using the UML. Below, an example of a simple Class Diagram is shown:


Core concerns: The class diagram shows the system’s classes, attributes, operations and the relationships between classes and other objects such as packages. Below you can se an example of a Class Diagram where the relationship between the Classes “Customer” and “Internet user” with the packages “WEB-API”, “Reservation Control”, “GUI” and “Database” is shown:


Relation to other templates: The Class Diagram presents a detailed structural view of information. It can for example be a decomposition of an Information System which typically is presented in an Application Architecture Diagram. If a Class Diagram becomes too complex or large, a Package Diagram, where the classes are grouped into Packages, could be modelled instead.

Properties and metadata: The Class Diagram can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Extensions regarding constraints and tagged values
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

In the picture below you can see the Class Diagrams properties dialogue window, where the information can be viewed and edited:


Leave a Comment