1 / 22

UML Class Diagrams (more notation)

This guide provides an in-depth look at UML Class Diagrams, highlighting their role in static modeling of systems. It covers the design class diagram (DCD), which includes more details than domain models. Key concepts such as attributes, association lines, dependencies, and composition are explained with clear notations and guidelines. Learn how to represent visibility, multiplicity, and qualified associations effectively. This resource is essential for anyone looking to master UML Class Diagrams and enhance their system design skills.

paulette-lemaire
Télécharger la présentation

UML Class Diagrams (more notation)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UML Class Diagrams(more notation)

  2. Class Diagrams • Used for static modeling, i.e. modeling the static aspects of system • Design class diagram (DCD) – used in design model, incorporates more detail than class diagram used for domain model

  3. Fig. 16.2

  4. Attributes • How to show: • Attribute text • Association line labeled • Attribute text notation: name : type Use +/- for visibility of attribute

  5. Fig. 16.3

  6. Attribute as association • Association line (in design model): • Navigability arrow • Multiplicity • Role name • No association name

  7. Fig. 16.2

  8. Fig. 16.4

  9. Attributes Guideline: use attribute text for data type objects, use association lines for more substantial objects . . .

  10. Fig. 16.5

  11. Fig. 16.6

  12. Fig. 16.7

  13. Fig. 16.12

  14. Dependencies • Dependency relationship: client object has knowledge of other object • Dependency line used in UML to show: • Global visibility • Parameter variable • Local variable • Static method

  15. Fig. 16.9

  16. Fig. 16.10

  17. Composition • Two closely related concepts: • Aggregation – part/whole • Composition – stronger form of part/whole (Note: for our purposes we will not make the distinction and just refer to it as composition.) • Notation: • Use (closed) diamond • Do not label association

  18. Fig. 16.13

  19. Qualified Association • Qualified association • Provide a name for one end of an association • Usually reduces multiplicity from many to one • Names an item within a context to show uniqueness • Example: File – Directory: use a filename as a qualifier

  20. Fig. 16.15

  21. Association Class • Association class • Allows attributes that more naturally belong to association than to either class • Example: Company – Person with association Employs, Salary more naturally belongs to association than to either of classes

  22. Fig. 16.16

More Related