Domain Model Classes and Objects Association Structure Requirement Specification Domain Model.

Slides:



Advertisements
Similar presentations
And so to Code. Forward, Reverse, and Round-Trip Engineering Forward Engineering Reverse Engineering Round-Trip Engineering.
Advertisements

Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Unified Modeling Language
UML Class Diagram. UML Class Diagrams2 Agenda What is a Class Diagram? Essential Elements of a UML Class Diagram Tips.
Jan 16, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration 1: a simple cash-only success scenario of Process Sale.
Together and UML Greg Johnson CSE 230 – Software Engineering Spring 2007.
Introduction To System Analysis and Design
UML Class Diagram and Packages Written by Zvika Gutterman Adam Carmi.
Slide 1 Chapter 7 Structural Modeling. Slide 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business.
Chapter 14 (Web): Object-Oriented Data Modeling
NJIT 1 Domain Model Visualizing Concepts Chapter 9 Applying UML and Patterns Craig Larman.
Systems Analysis and Design in a Changing World, 6th Edition
Modelling classes Drawing a Class Diagram. Class diagram First pick the classes –Choose relevant nouns, which have attributes and operations. Find the.
Chapter 9 Domain Models 1CS6359 Fall 2012 John Cole.
Chapter 14: Object-Oriented Data Modeling
Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”
Object Oriented Software Development
Domain Modeling 中国科学技术大学软件学院 孟宁 2012 年 10 月 Domain Modeling ♦What: A process performed by the development teams to acquire domain knowledge. ♦Why: –Because.
CSCI-383 Object-Oriented Programming & Design Lecture 9.
IS0514Slide 1 IS0514 Lecture Week 5 Introduction to Object Orientation.
Chapter 10: Writing Class Definitions Visual Basic.NET Programming: From Problem Analysis to Program Design.
Introduction To System Analysis and Design
Object-Oriented Analysis and Design An Introduction.
Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.
DOMAIN MODE: ASSOCIATIONS, MULTIPLICITY AND ATTRIBUTE-TEXT NOTATION SYS466.
Association Class Generalization/Specialization Whole-Part Page More Associations 1.
Slide 1 Structural Modeling Chapter 7. Slide 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business.
Unit 3 Conceptual Data Modeling. Key Concepts Conceptual data modeling process Classes and objects Attributes Identifiers, candidate keys, and primary.
Domain Model Classes and Objects Association Structure Requirement Specification Domain Model.
Conceptual Modeling Modeling the Problem Domain. Conceptual Modeling Decompose problem space into comprehensible concepts. Clarify the terminology or.
Chapter 9 Applying UML and Patterns -Craig Larman
Domain Model—Part 3: Associations, Multiplicity and Attribute- Text Notation.
Introduction to Unified Modeling Language (UML) By Rick Mercer with help from The Unified Modeling Language User Guide, Grady Booch, James Rumbaugh, Ivar.
SYS466: Analysis and Design Using OO Models Domain Class Diagram.
Lecture 6: Structural Modeling
Structural Modeling Chapter 7. Key Ideas A structural or conceptual model describes the structure of the data that supports the business processes in.
2007ACS-3913 Ron McFadyen1 Class Diagram See Schaum’s UML Outline, especially chapters 4, 5, 6, 7.
FEN NOEA/IT - Databases/ODB1 ODB – Object DataBases Object-Oriented – Fundamental Concepts UML and EE/R OO and Relational Databases Introduction.
Design Model Lecture p6 T120B pavasario sem.
Domain Modeling Yonglei Tao.
Session 02 and 03: C# OOP 1 OOP in C#: Classes and Objects in C#. Object-Oriented Design. UML Class Diagram. Object Interaction. FEN AK IT:
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Chapter 16 UML Class Diagrams 1CS6359 Fall 2012 John Cole.
Larman chapter 101 Domain Model: Visualizing concepts Larman chapter 10.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
BTS430 Systems Analysis and Design using UML Design Class Diagrams (ref=chapter 16 of Applying UML and Patterns)
Introduction to Unified Modeling Language (UML) By Rick Mercer with help from The Unified Modeling Language User Guide, Grady Booch, James Rumbaugh, Ivar.
IB Computer Science Content developed by Dartford Grammar School Computer Science Department UML.
Database Design Chapters 17 and 18.
Elaboration popo.
Chapter 9 Domain Models.
UML Class Diagrams.
Visit for more Learning Resources
Domain Model: Visualizing concepts
Chapter 16 UML Class Diagrams.
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Chapter 5: Object Oriented Analysis and Design
Introduction to Unified Modeling Language (UML)
OO Domain Modeling With UML Class Diagrams and CRC Cards
Conceptual data modeling
Object Oriented Analysis and Design
Introduction to Unified Modeling Language (UML)
SYS466 Domain Classes – Part 1.
Database Design Chapters 17 and 18.
Chapter 11: Class Diagram
ITEC 3220A Using and Designing Database Systems
Domain Model: Visualizing Concepts
Chapter 11: Class Diagram
Cheng (Sp2001): Object-Oriented Development Overview
Presentation transcript:

Domain Model Classes and Objects Association Structure Requirement Specification Domain Model

Information Need in the IT System Information need are found by analysing the problem- domain for the IT system Ask the question: What information should be registered by the IT system ? The building blocks are objects binds requirements, design and program together Result: A model showing the problem-domain – we call it Domain Model ” The most important model in OO analysis” 2

Requirement Functional Use case: find customer 1.A sales person wants to find information about customer 2.The sales person types the customers id 3.The system returns information about the customer Non functional The system has to be user friendly Clarify information Customer: id, name, address Objects binds requirements, design and programming together 3 3 Design Design of architecture Design of GUI Design of classes Design database Implementation Writing the code public class Customer { private int id, private String name; private String address; public Customer(int id) { this.id = id; } public String getName() { return name; } ….. Test idnameaddress Customer Domain object of class Customer

Class, objects, attributes and values Customer is candidateObject of class ”Customer” for a class A class describes a collection of objects of the same attributes, structure, and behaviour pattern 4

Domain model A domain model is the visual representation of conceptual classes We illustrate it by drawing a UML class diagram: 1.Domain objects or conceptual classes 2.Associations between the objects 3.Each objects attributes A conceptual class is described by: name (symbol) Definition – the purpose in problem domain (intension) Examples given on objects created from class (extension) 5

6 Example of a conceptual class Class: Definition: The customer class is used to describe the company's customers. An example: Hans Andersen, Eventyrvej 2, 5000 Odense, phone , …… Attributes: Name, adress, phone, Customer Name Adress Phone Customer

A Domain Model The classes are connected - here by an association drawn as the line between the concepts. Nameable of a verb phrase. Start with Capital Add the multiplicity defines how many instances(objects) of a class that can be associated with an instance (object) of another class Ex: a student can be enrolled in none or 1 team Result: A UML class diagram 7

Requirement specification. 8 Try to create this one in UMLet

"Multiplicity" - Diversity or cardinality 9

Association Relation between a number of objects. Association A customer can have more orders at once – an order belongs to one customer only. Drawn as a simple line like this: 10 UML Association with multiplicity UML class

Generalisation Used when there are some common attributes shared by several classes (it is implemented as inheritance) 11

Aggregation Used when there is a stronger relation between two classes than association can express 12

Patterns A pattern is defined as a generic solution to a problem often encountered in the real world Not a theoretical solution Based on empirical data and what works When we construct a domain model then we will often use patterns Next time we will look at several patterns 13