1 / 10

Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book.

Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book. What is Class Diagram ? T he different between Domain Model and Design Model. H ow to build UML Class Diagram ( Class, Attribute, Relationship ). Overview.

camilla-hess
Download Presentation

Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book.

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. Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book.

  2. What is Class Diagram ? • The different between Domain Model and Design Model. • How to build UML Class Diagram (Class, Attribute, Relationship). Overview

  3. A class diagram shows the existence of classes and their relationships in the logical view of a system. • UML modeling elements in class diagrams: • Classes and their structure and behavior. • Association, aggregation, dependency, and inheritance relationships. • Multiplicity and navigation indicators. • Role names. What is Class Diagram ?

  4. Domain Model vs. Design Model Classes

  5. Example DCD

  6. Identify all the classes participating in the software solution. Do this by analyzing the interaction diagrams. Draw them in a class diagram. • Duplicate the attributes from the associated concepts in the Domain Model. Creating NextGen POS DCD

  7. Add method names by analyzing the interaction diagrams. • The methods for each class can be identified by analyzing the interaction diagrams. Creating NextGen POS DCD

  8. Add type information to the attributes and methods. Creating NextGen POS DCD

  9. The find message to the multiobject should be interpreted as a message to the container/collection object. • The find method is not part of the ProductSpecification class. Method Names - Multiobjects

  10. Adding Navigability & Dependency Relationships

More Related