Jan 21, 200291. 3913 Ron McFadyen1 Domain Modeling Specification classes “need-to-know” associations Reflexive associations “association checklist”

Slides:



Advertisements
Similar presentations
Conceptual Design using the Entity-Relationship Model
Advertisements

Developing Database Specifications TRACK 3. Learning Objectives At the end of the session, the participants should be able to Identify the information.
Jan 16, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration 1: a simple cash-only success scenario of Process Sale.
Feb 18, R McFadyen1 Feb 18, 2002 Review of some modeling concepts Introduction of Moment-Interval.
1 Domain Model Adding Associations Chapter 11 Applying UML and Patterns -Craig Larman.
6/8/991 Analysis Tuesday 09/14/99 Revised: September 11, 2000 (APM)
Database Design Concepts Lecture 19 Term 2 week 8 Worked example of normalisation.
Domain model: visualizing concepts
NJIT 1 Domain Model Visualizing Concepts Chapter 9 Applying UML and Patterns Craig Larman.
Data modeling using the entity-relationship model Winter 2006Ron McFadyen Entity-relationship model (ER model) P. 49: “This model and its variations.
Chapter 9 Domain Models 1CS6359 Fall 2012 John Cole.
9/18/011 Software Requirements Analysis and Design (Continued)
Domain Modeling Chandan R. Rupakheti and Steve Chenoweth Week 5, Day 1.
Entity/Relationship Modelling
Relational Database Need to Knows. What is a database? Data - is just a pile of numbers or stats. A business "organises" the data to be meaningful and.
Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”
Virtual Trip 5 time zones away January, 2011 K. Snyder Norwood Public School.
Object-Oriented Analysis and Design
Database Design Principles of database design. Relational Models Relational databases are designed to provide efficient structures for transaction processing.
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’
Last lecture. What is a Use Case Use cases are stories (scenarios) of how actors use (interact with) the system to fulfill his goal. Examples Process.
MIS 301 Information Systems in Organizations Dave Salisbury ( )
MIS 301 Information Systems in Organizations Dave Salisbury ( )
Information Systems Analysis and Design Class Modeling
DOMAIN MODEL— PART 2: ATTRIBUTES SYS466. Looking For Potential Classes “Know the business”. Ask Questions Identify business concepts; filter nouns (person,
Chapter 9 Domain Models. Domain Modeling After you have your requirements you start modeling the domain. You are still modeling the business, not the.
TK2023 Object-Oriented Software Engineering CHAPTER 5 DOMAIN MODELLING.
Domain Modelling Presented By Dr. Shazzad Hosain.
Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.
Database Design Sections 9 & 10 Modeling Historical Data, conditional nontranferability, time-related constraints 1.
Chapter 9 Domain Models $PH\06f522\LarmanApplUMLandPtrns\larman3EdDgmsCh01-14\09_domainModelsR2.ppt – RJL
Module 5 Planning for SQL Server® 2008 R2 Indexing.
DAY 12: DATABASE CONCEPT Tazin Afrin September 26,
Review ♦ System sequence diagram ♦ Domain model
Lecture 9 Enterprise Systems Development ( CSC447 ) COMSATS Islamabad Muhammad Usman, Assistant Professor.
Normalization Well structured relations and anomalies Normalization First normal form (1NF) Functional dependence Partial functional dependency Second.
Jan 21, Ron McFadyen1 Ch 10. Domain Model: Visualizing Concepts Domain model illustrated with a class diagram (with no operations defined)
Possible Queries Queries For All User Access: –Query 1: The purpose of this query is to allow users to view all the package details for a given tracking.
Conceptual Modeling Modeling the Problem Domain. Conceptual Modeling Decompose problem space into comprehensible concepts. Clarify the terminology or.
Group 6. What is data redundancy? Data redundancy occurs in database systems which have a field that is repeated in two or more tables... Data redundancy.
Chapter 9 Applying UML and Patterns -Craig Larman
SYS466: Analysis and Design Using OO Models Domain Class Diagram.
Elaboration Iteration 1- Part 1
2007ACS-3913 Ron McFadyen1 Class Diagram See Schaum’s UML Outline, especially chapters 4, 5, 6, 7.
BTS430 Systems Analysis and Design using UML Domain Model—Part 2: Associations and Attributes.
Domain Model—Part 2: Attributes.  A logical data value of an object  (Text, p. 158)  In a domain model, attributes and their data types should be simple,
Object Oriented Analysis: Associations. 2 Object Oriented Modeling BUAD/American University Class Relationships u Classes have relationships between each.
Repetition af Domæne model. Artifact influence emphasizing the Domain Model.
BTS430 Systems Analysis and Design using UML Domain Model—Part 2: Associations and Attributes.
BTS430 Systems Analysis and Design using UML Domain Model—Part 2A: Attributes.
January Ron McFadyen1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain of interest.
Entity/Relationship Modelling. Entity Relationship Modelling In This Lecture Entity/Relationship models Entities and Attributes Relationships Attributes.
Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.
BTS430 Systems Analysis and Design using UML Domain Model—Part 2: Associations and Attributes.
1 Object Oriented Analysis and Design Conceptual Model.
Modeling Your Data Chapter 2 cs5421. Part II Discussion of the Model: Good Design/ Bad Design? cs5422.
April 20022CS3X1 Database Design Entity-relationship modelling John Wordsworth Department of Computer Science The University of Reading
DOMAIN MODEL—PART 2: ATTRIBUTES BTS430 Systems Analysis and Design using UML.
Research Proposal Writing Resource Person : Furqan-ul-haq Siddiqui Lecture on; Wednesday, May 13, 2015 Quetta Campus.
My Dream Vacation to By:. Flight Information Departing From: Departing From: Departure Date: Departure Date: Name of the Airline: Name of the Airline:
Chapter 9 Domain Models.
Errors in ER Diagram Do not represent a concept as both a relationship type and an attribute Make sure every entity type must have a key attribute Relationship.
Entity Relationship Diagrams
MIS2502: Data Analytics Relational Data Modeling
Object Oriented Analysis and Design Conceptual Model.
Examines blended and separate transaction schemas
Database.
Domain Model: Visualizing Concepts
Page 37 Figure 2.3, with attributes excluded
Presentation transcript:

Jan 21, Ron McFadyen1 Domain Modeling Specification classes “need-to-know” associations Reflexive associations “association checklist”

Jan 21, Ron McFadyen2 Specification (Description) conceptual classes P. 142: Include a specification class when we need a description of something irrespective of its existence deletions result in loss of information it reduces duplicated information Sale SaleLineItemProductSpecification

Jan 21, Ron McFadyen3 Specification (Description) conceptual classes Flight destination arrival vs Flight destination arrival Airport Destination and arrival airports as attributes Destination and arrival airports as associations vs

Jan 21, Ron McFadyen4 Specification (Description) conceptual classes Flight is a class that keeps track of flight number, date and time for a flight, departure and arrival airports. departs from arrives in arrival departure * *1 1 Flight number date time name address Regardless of the date/time of a flight, the number and the airports involved stay constant. Airport

Jan 21, Ron McFadyen5 Specification (Description) conceptual classes Flight date time Larman suggests the use of a Description/Specification Conceptual Class to hold these attributes - to avoid an anomaly relating to information disappearing due to objects being deleted. FlightDescription number * 1 departs from arrives in arrival departure * *1 1 name address Airport

Jan 21, Ron McFadyen6 Page 164: Focus on those associations for which knowledge of the relationship needs to be preserved for some duration “need-to-know” associations Avoid showing redundant or derivable associations “need-to-know” associations correspond to verbs expressing a relationship between classes objects do not exist in isolation - they fit together in some way

Jan 21, Ron McFadyen7 “need-to-know” associations Flight date time Our database needs to record, to keep track of, when flights are scheduled, where they fly from and to - I.e. we need to know (or be able to derive) this information. FlightDescription number * 1 departs from arrives in arrival departure * *1 1 name address Airport

Jan 21, Ron McFadyen8 “need-to-know” associations departs from arrives in arrival departure Flight date time name address We can always derive the departure and arrival airports for a flight, so we don’t need to have these 2 redundant relationships Airport FlightDescription number * 1 * * 1 1 arrival departure

Jan 21, Ron McFadyen9 * 0..1 Page 158: “ a person can be Married-to only one other person at any particular moment, even though... Person is Married to ? Reflexive associations

Jan 21, Ron McFadyen10 Page 160: ? Person Supervises Reflexive associations *

Jan 21, Ron McFadyen11 Pages 156, 162: “association checklist” typical ways in which associations arise A is physically contained in B … Section in a Book A is an organizational subunit of B … Faculty in a University etc Association checklist