Copyright © Craig Larman. 2000 All Rights Reserved The Domain Model.

Slides:

Advertisements

Similar presentations

7M701 1 Information Systems Modelling and Design with.

Advertisements

Object-Oriented Analysis and Design Introduction 1.

Chapter 1 Object Oriented Analysis and Design. UML, Patterns, and Object-Oriented Analysis and Design  The essential skills for the creation of well-designed,

Sucha Smanchat  Steps in OOAD using UML  Use Case Diagram  Sequence Diagram / Communication Diagram  Class Diagram  State.

Object-Oriented Analysis and Design

Object Oriented Analysis and Design

PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 The.

NJIT Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman Presented By :Satish Khanna.

Domain model: visualizing concepts

NJIT 1 Domain Model Visualizing Concepts Chapter 9 Applying UML and Patterns Craig Larman.

Object Oriented Analysis and Design Chapter 1 Applying UML and Patterns -Craig Larman.

Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.

Kari R. Schougaard, PhD Stud. Værktøjer og Teknikker, 2006 UNIVERSITY OF AARHUS Department of Computer Science Unified Modeling Language Visual language.

6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.

Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”

Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.

IntellAgile Copyright © 2002 Craig Larman. All rights reserved. Craig Larman’s Applying UML and Patterns: Hands-on Mastery of OOA/D.

IntellAgile Copyright © 2002 Craig Larman. All rights reserved. Visualizing Concepts with a Domain Model.

What is a domain model? “A domain model captures the most important types of objects in the context of the business. The domain model represents the ‘things’

BTS430 Systems Analysis and Design using UML Domain Model Part 1—Finding Conceptual Classes.

Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.

1 On to Object Design Chapter 14 Applying UML and Patterns.

SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler

Chapter 6: Structured Vs. Object Oriented Analysis and Design.

Object-Oriented Analysis and Design An Introduction.

DOMAIN MODE: ASSOCIATIONS, MULTIPLICITY AND ATTRIBUTE-TEXT NOTATION SYS466.

11 Partnership for Performance How to hear this lecture Click on the icon: to hear the narration for each slide.

Chapter 7 Applying UML and Patterns Craig Larman

Copyright © Craig Larman All Rights Reserved Responsibility-Driven Design with the GRASP Patterns.

Jan 21, Ron McFadyen1 Ch 10. Domain Model: Visualizing Concepts Domain model illustrated with a class diagram (with no operations defined)

Structural Modeling. Objectives O Understand the rules and style guidelines for creating CRC cards, class diagrams, and object diagrams. O Understand.

Object-Oriented Analysis and Design Fall 2009.

1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.

Chapter 16 Applying UML and Patterns Craig Larman

Domain Model Refinement Larman, chapter 31 CSE 432: Object-Oriented Software Engineering Glenn D. Blank, Lehigh University.

UML Diagrams A tool for presentation of Architecture.

Chapter 9 Applying UML and Patterns -Craig Larman

Domain Model—Part 3: Associations, Multiplicity and Attribute- Text Notation.

♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.

NJIT UML Class Diagrams Chapter 16 Applying UML and Patterns Craig Larman.

What to remember from Chap 13 (Logical architecture)

Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.

1 On To Object Design Chapter 14 Applying UML and Patterns -Craig Larman.

Repetition af Domæne model. Artifact influence emphasizing the Domain Model.

Object-Oriented Analysis and Design ธนวัฒน์ แซ่ เอียบ.

Object Oriented Analysis and Design Chapter 1 Applying UML and Patterns -Craig Larman.

UML Package Diagrams. Package Diagrams UML Package Diagrams are often used to show the contents of components, which are often packages in the Java sense.

Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN Objectives Describe the book goals and scope Define OOA/D (Object-Oriented Analysis and Design) Illustrate.

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.

Summary from previous lectures

TK2023 Object-Oriented Software Engineering CHAPTER 11 CLASS DIAGRAMS.

BTS430 Systems Analysis and Design using UML Design Class Diagrams (ref=chapter 16 of Applying UML and Patterns)

Object Oriented Analysis & Design By Rashid Mahmood.

Copyright © Craig Larman All Rights Reserved Large-Scale System Partitioning.

Software Modelling Class Diagram. Class Diagrams The main building block in object oriented modeling They are used both for general conceptual modeling.

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

Chapter 9 Domain Models.

Domain Model: Visualizing concepts

BTS430 Systems Analysis and Design using UML

Chapter 6: Structured Vs. Object Oriented Analysis and Design.

Chapter 5: Object Oriented Analysis and Design

Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN

Chapter 13 Logical Architecture.

A tool for presentation of Architecture

A tool for presentation of Architecture

Chapter 13 Logical Architecture.

Object Oriented Analysis and Design

Chapter 13 Logical Architecture.

Presentation transcript:

Copyright © Craig Larman All Rights Reserved The Domain Model

Copyright © Craig Larman All Rights Reserved 2 Introduction n Partitions and illustrates the important domain concepts. n A classic object-oriented analysis activity. n What are the objects of interest in the this domain? – their attributes? – their relationships? n IMPORTANT: Not software objects, but a “visual dictionary” of domain concepts.

Copyright © Craig Larman All Rights Reserved 3 A Domain Model Does Not Represent Software Objects n A model of domain concepts, not of software objects. – A “visual dictionary” of important words in the domain. n Uses UML static structure diagram notation.

Copyright © Craig Larman All Rights Reserved 4 Terminology n UP domain model = book conceptual model

Copyright © Craig Larman All Rights Reserved 5 Partitioning the Domain Model n Although this is conceptually accurate, a person will not actually draw package boxes around groups as in this example. Rather, a CASE tool will allow “drill down”.

Copyright © Craig Larman All Rights Reserved 6 Finding Domain Concepts n Candidate lists n “Abbott” Analysis n Existing analysis patterns – Analysis Patterns, Fowler – Data Model Patterns, Hay – The Data Model Resource Book, Silverston

Copyright © Craig Larman All Rights Reserved 7 Associations

Copyright © Craig Larman All Rights Reserved 8 Multiplicity

Copyright © Craig Larman All Rights Reserved 9 Focus on Important Associations

Copyright © Craig Larman All Rights Reserved 10 Attributes n Show only “simple” relatively primitive types as attributes. n Connections to other concepts are to be represented as associations, not attributes.

Copyright © Craig Larman All Rights Reserved 11 Do Not Use Attributes To Relate Concepts n Why not?

Copyright © Craig Larman All Rights Reserved 12 An Example