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

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
Advertisements

Object Design Examples with GRASP
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Sucha Smanchat  Steps in OOAD using UML  Use Case Diagram  Sequence Diagram / Communication Diagram  Class Diagram  State.
Oct 22, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,
Copyright ©2004 Cezary Z Janikow 1 Domain Model n Visualization of entities and relationships n In UP presented as Class Diagrams – Classes, Relationships,
Page 1  Copyright © 1997 by Rational Software Corporation Class Diagrams A class diagram shows the existence of classes and their relationships in the.
Domain model: visualizing concepts
Feb 4, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – (interfaces,
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
November Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
PRJ566: PROJECT PLANNING AND MANAGEMENT Class Diagrams.
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.
Unified Modeling Language
Object-Oriented Analysis and Design
CSSE 374: Design Class Diagrams Steve Chenoweth Office: Moench Room F220 Phone: (812) These slides and others.
Objectives Design Class Diagrams Issues in system design Generalization Review UML papers.
Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
Object-Oriented Analysis and Design An Introduction.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
Real Time Systems Modeling Structure in UML (Part I)
Domain Modeling Part2: Domain Class Diagram Chapter 4 pp part 2 1.
Design Class Diagrams (DCDs)
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
Chapter 16 Applying UML and Patterns Craig Larman
Chapter 8 Analysis & Modeling. Data Modeling examines data objects independently of processing focuses attention on the data domain creates a model at.
Copyright © Craig Larman All Rights Reserved The Domain Model.
DOMAIN MODEL- VISUALIZING CONCEPTS Identify conceptual classes related to the current iteration requirements. Create an initial domain model. Distinguish.
NJIT UML Class Diagrams Chapter 16 Applying UML and Patterns Craig Larman.
Part VII: Design Continuous
Design Model Lecture p6 T120B pavasario sem.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Class Diagram Chapter 21 Applying UML and Patterns Craig Larman.
Class diagrams Terézia Mézešová.
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
Chapter 16 UML Class Diagrams 1CS6359 Fall 2012 John Cole.
TK2023 Object-Oriented Software Engineering CHAPTER 9 INTRODUCTION TO OBJECT DESIGN.
Larman chapter 101 Domain Model: Visualizing concepts Larman chapter 10.
OO Methodology Elaboration Phase Iteration 1- Part 3.
04 - OOD Intro.CSC4071 Software Design ‘Requirements’ defines –The goals the system needs to satisfy. ‘Specification’ defines –The externally-observable.
BTS430 Systems Analysis and Design using UML Design Class Diagrams (ref=chapter 16 of Applying UML and Patterns)
Chapter 9 Domain Models.
UML Class Diagrams (more notation)
Domain Model: Visualizing concepts
Chapter 5: Object Oriented Analysis and Design
Domain Model Refinement
Chapter 8 Analysis & Modeling
UML SEQUENCE AND CLASS DIAGRAMS
Software Architecture & Design Pattern
Visualizing Design Patterns in Their Applications and Compositions
Domain Class Diagram Chapter 4 Part 2 pp
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Understand and Use Object Oriented Methods
OBJECT ORIENTED ANALYSIS AND DESIGN
Chapter 11: Class Diagram
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Chapter 16 Class Diagrams.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 16 UML Class Diagrams
Appendix A Object-Oriented Analysis and Design
Chapter 11: Class Diagram
Design Model: Creating Design Class Diagrams
Presentation transcript:

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

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

3 What is Class Diagram ?  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.

4 Domain Model vs. Design Model Classes

5 Example DCD

6 Creating 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.

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

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

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 the ProductSpecification class.

10 Adding Navigability & Dependency Relationships