Presentation is loading. Please wait.

Presentation is loading. Please wait.

Design Model: Creating Design Class Diagrams

Published byMarlene Shields Modified over 5 years ago

Similar presentations

Presentation on theme: "Design Model: Creating Design Class Diagrams"— Presentation transcript:

1 Design Model: Creating Design Class Diagrams

2 When to create DCDs Once the interaction diagrams have been completed it is possible to identify the specification for the software classes and interfaces. A class diagram differs from a Domain Model by showing software entities rather than real-world concepts. The UML has notation to define design details in static structure, or class diagrams.

3 DCD and UP Terminology Typical information in a DCD includes:
Classes, associations and attributes Interfaces (with operations and constants) Methods Attribute type information Navigability Dependencies The DCD depends upon the Domain Model and interaction diagrams. The UP defines a Design Model which includes interaction and class diagrams.

4 Domain Model vs. Design Model Classes
Register Sale Domain Model 1 Captures 1 Date isComplete : Boolean time Register Sale Date isComplete : Boolean time Design Model 1 Captures 1 addLineItem(…) … makeLineItem()

5 An Example DCD Three section box Navigability Sale Register Date
isComplete : Boolean time 1 1 Captures addLineItem(…) … makeLineItem() methods; parameters not specified Type information

6 Creating a NextGen POS DCD
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. Register ProductSpecification description price itemID ProductCatalog Payment quantity amount Sale Store SalesLineItem address name date isComplete time quantity

7 Creating a NextGen POS DCD
Add method names by analyzing the interaction diagrams. The methods for each class can be identified by analyzing the interaction diagrams. Sale If the message makeLineItem is sent to an instance of class Sale, then class Sale must define a makeLineItem method. date isComplete time makeLineItem() 3: makeLineItem(spec, quantity) :Register :Sale

8 Creating a NextGen POS DCD
Add type information to the attributes and methods. Register ProductCatalog ProductSpecification Payment description price itemID amount … getSpecification() endSale() addLineItem() makeNewSale() makePayment() Sale SalesLineItem date isComplete: Boolean time Quantity: Integer Store becomeComplete() makeLineItem() makePayment() getTotal() Address: String Name: String getSubtotal() addSale()

9 Method Names -Multiobjects
The find message to the multiobject should be interpreted as a message to the container/ collection object. The find method is not part of he ProductSpecification class. 1: spec := getSpecification(id) :ProductCatalog 1.1: spec := find(id) :ProductSpecification

10 Associations, Navigability, and Dependency Relationships
Add the associations necessary to support the required attribute visibility. Each end of an association is called a role. Navigability is a property of the role implying visibility of the source to target class. Attribute visibility is implied. Add navigability arrows to the associations to indicate the direction of attribute visibility where applicable. Common situations suggesting a need to define an association with navigability from A to B: A sends a message to B. A creates an instance of B. A needs to maintain a connection to B Add dependency relationship lines to indicate non-attribute visibility.

11 Creating a NextGen POS DCD
Register class will probably have an attribute pointing to a Sale object. Navigability arrow indicates Register objects are connected uni-directionally to Sale objects. Sale Register Date isComplete : Boolean time Captures 1 1 endSale() addLineItem() makePayment() makeLineItem() Absence of navigability arrow indicates no connection from Sale to Register.

12 Adding Navigability and Dependency Relationships
Uses Store 1 ProductSpecification address : Address name : Text 1 1 description : Text price : Money itemID: itemID ProductCatalog addSale() Contains 1 1 1 Looks-in getSpecification() 1 Houses Illustrates non-attribute visibility Describes 1 1 * Register SaleLineItem Sale Captures Contains Date : Date isComplete : Boolean time : Time quantity : Integer 1 1 endSale() enterItem() makePayment() 1 getSubtotal() becomeComplete() makeLineItem() makePayment() getTotal() Payment amount : Money * 1 Logs-completed Paid-by 1

13 Sources Visual Paradigm Class Diagrams: paradigm.com/guide/uml-unified-modeling-language/what-is-class- diagram/ Good explanation on visibility: between-objects-in-a-uml-class-diagram

Download ppt "Design Model: Creating Design Class Diagrams"

Similar presentations

Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.

Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Object Design Examples with GRASP

Object Design Examples with GRASP
Jan 23, 200291. 3913 Ron McFadyen1 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented.

Jan 23, Ron McFadyen1 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented.
Oct 200391.3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Oct Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.
Oct 22, 200291.3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

Oct 22, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,
March 200391.3913 Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns Assigning responsibilities to objects to achieve user goals Section 17.4.

March Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns Assigning responsibilities to objects to achieve user goals Section 17.4.
Fall 2009AXS-3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Fall 2009AXS-3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.
Oct 200391.3913 Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns P. 248: “The assignment of responsibilities and design of collaborations.

Oct Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns P. 248: “The assignment of responsibilities and design of collaborations.
Fall 2009ACS-3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

Fall 2009ACS-3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,
6/8/991 Analysis Tuesday 09/14/99 Revised: September 11, 2000 (APM)

6/8/991 Analysis Tuesday 09/14/99 Revised: September 11, 2000 (APM)
October 16, 2001Class Diagrams1. October 16, 2001Class Diagrams2 (Design) Class Diagrams (1) zA class diagram is a visual representation of various classes.

October 16, 2001Class Diagrams1. October 16, 2001Class Diagrams2 (Design) Class Diagrams (1) zA class diagram is a visual representation of various classes.
Feb 4, 200291.3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – (interfaces,

Feb 4, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – (interfaces,
Feb 200592.3913 Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.

Feb Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.
November 200491.3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

November Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,
Object-Oriented Analysis and Design

Object-Oriented Analysis and Design
November 200491.3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

November Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.
Fall 2009ACS-3913 Ron McFadyen1 From the Merriam-Webster’s online dictionary (www.m-w.com): Main Entry: an·thro·po·mor·phism Date: 1753 an interpretation.

Fall 2009ACS-3913 Ron McFadyen1 From the Merriam-Webster’s online dictionary ( Main Entry: an·thro·po·mor·phism Date: 1753 an interpretation.
Designing with Interaction and Design Class Diagrams Chapters 15 & 16 Applying UML and Patterns Craig Larman With some ideas from students in George Blank’s.

Designing with Interaction and Design Class Diagrams Chapters 15 & 16 Applying UML and Patterns Craig Larman With some ideas from students in George Blank’s.
9/18/011 Software Requirements Analysis and Design (Continued)

9/18/011 Software Requirements Analysis and Design (Continued)
Object-Oriented Analysis and Design

Object-Oriented Analysis and Design

Similar presentations

Ads by Google