Object Oriented Methodologies

Slides:



Advertisements
Similar presentations
Outline Data, Information & Knowledge Database DBMS Types of Models
Advertisements

Chapter 2.2 V3.0 Napier University Dr Gordon Russell
214 CONCEPTUAL DESIGN: UML CLASS DIAGRAM RELATIONSHIPS.
Chapter 4: The Enhanced ER Model and Business Rules
1 Chapter 4 The Enhanced ER Model and Business Rules.
Chapter 3: The Enhanced E-R Model
© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,
Chapter 3  Define terms  Understand use of supertype/subtype relationships  Understand use of specialization and generalization techniques  Specify.
Object-oriented modeling Class/Object Diagrams
1 Class Number – CS 304 Class Name - DBMS Instructor – Sanjay Madria Instructor – Sanjay Madria Lesson Title – EER Model –21th June.
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Chapter 4 © 2005 by Prentice Hall 1 Objectives Definition of terms Definition of terms Use of supertype/subtype relationships Use of supertype/subtype.
Chapter 14 (Web): Object-Oriented Data Modeling
Chapter 4: The Enhanced ER Model and Business Rules
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Enhanced ER modeling techniques Transparencies
IS 4420 Database Fundamentals Chapter 4: The Enhanced ER Model and Business Rules Leon Chen.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
Chapter 14: Object-Oriented Data Modeling
1 Chapter 4: The Enhanced ER Model and Business Rules.
Jerry KotubaSYST39409-Object Oriented Methodologies1 Object Oriented Methodologies Week04.
Databases Illuminated Chapter 8 The Enhanced Entity-Relationship Model and the Object-Relational Model.
Copyright Flying Kiwi Productions Inc. 1 An Introduction to Object-Oriented Analysis Objects and UML in plain English. Chapter.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Session 11 The Class Diagram: Aggregation and Generalization Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 12, 2011 Presented.
Conceptual Data Modeling. What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model.
R McFadyen Chapter 7 Conceptual Data Modeling.
Association Class Generalization/Specialization Whole-Part Page More Associations 1.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes.
Copyright Flying Kiwi Productions Inc. 1 An Introduction to Object-Oriented Analysis Objects and UML in plain English. Chapter.
1 © Prentice Hall, 2002 Chapter 14: Object-Oriented Data Modeling Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R.
7-1 © Prentice Hall, 2007 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
Domain Modeling Part2: Domain Class Diagram Chapter 4 pp part 2 1.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
Activity & Class Modeling Labs Discussion p3 T120B pavasario sem.
Jerry KotubaSYST39409-Object Oriented Methodologies1 Object Oriented Methodologies Week05/06.
Chapter 4 1 Chapter 4: The Enhanced ER Model and Business Rules Modern Database Management Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden.
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
Object-Oriented Data Modeling
Weak Entity Sets A weak entity is an entity that cannot exist in a database unless another type of entity also exists in that database. Weak entity meets.
 Week08.  Review Schedule Weeks 8-14  This week o Review last class o Introduce Class Diagrams o ICE-03 Sheridan SYST Engineering Quality Systems.
LESSON05 Jerry Kotuba Object Oriented Methodologies 1.
Software Engineering Zhang Shuang
1 CSBP430 – Database Systems Chapter 4: Enhanced Entity– Relationship and Object Modeling Elarbi Badidi College of Information Technology United Arab Emirates.
Database Design – Lecture 12 Object Oriented Database Design cont’d.
Chapter 12 Object-oriented design for more than one class.
 Class diagrams show the classes of the system, their interrelationships (including inheritance, aggregation, and association), and the operations and.
Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
Class Diagram Lecture # 1. Class diagram A Class Diagram is a diagram describing the structure of a system shows the system's classes Attributes operations.
Chapter 4_part2: The Enhanced Entity-Relationship (EER) Model.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
The Enhanced Entity- Relationship (EER) Model
Object-Oriented Modeling
The Enhanced E-R Model and Business Rules
LECTURE 4: Chapter 4: The Enhanced E-R Model
Conceptual Design & ERD Modelling
Business System Development
EER Model – Chapter
OBJECT ORIENTED CONCEPT
Class diagram Description
Domain Class Diagram Chapter 4 Part 2 pp
Engineering Quality Software
Overview of Entity‐Relationship Model
CHAPTER 3: THE ENHANCED E-R MODEL
Software Engineering Lecture #11.
Object Oriented Analysis and Design Using the UML
Chapter 8 Properties of Objects and Classes
ADVANCED OBJECT-ORIENTED PROGRAMMING
Presentation transcript:

Object Oriented Methodologies Lesson06 Jerry Kotuba

Agenda Class Diagrams Solution I-C-E-03 & 04 Posted Take up the Class Diagrams Class Diagrams Whole-to-part associations I-C-E-05 Object Oriented Methodologies Jerry Kotuba

Generalization, Inheritance & Constraints generalization path solid line with hollow arrowhead pointing from subclass to superclass indicate basis of generalization name the path for the attribute being removed = called the discriminator discriminator shows which property is abstracted by a generalization relationship SYST39409 - Object Oriented Methodologies Jerry Kotuba

Constraints on Generalization constraints on the subclasses overlapping: descendent may be descended from more than one of the subclasses student can be both a research and teaching assistant disjoint: descendent may not be descended from more than one of the subclasses patient can not be both out and resident SYST39409 - Object Oriented Methodologies Jerry Kotuba

Constraints on Generalization complete: all subclasses are listed only have out and resident patients incomplete: all subclasses are not listed more subclasses are available can have casual, part-time employees SYST39409 - Object Oriented Methodologies Jerry Kotuba

Whole-to-Part Associations The UML provides ways to model two types of whole-to- part associations – aggregation and composition. Object Oriented Methodologies Jerry Kotuba

Definitions aggregate: In an aggregation, the class representing the whole. aggregation: An association between classes representing a part-to- whole relationship in which the parts and the whole may exist independently and in which a single part may be associated with more than one whole at the same time. Object Oriented Methodologies Jerry Kotuba

Definitions…cont’d composite: In a composition, a class representing the whole. composition: An association between classes representing a whole-to- part relationship in which the parts may belong to only one whole at a time and the whole does not exist without its parts. Object Oriented Methodologies Jerry Kotuba

Example of an Aggregation . Object Oriented Methodologies Jerry Kotuba

Example of a Composition . Object Oriented Methodologies Jerry Kotuba

Aggregation and Composition . Object Oriented Methodologies Jerry Kotuba

Categories of Whole-to-Part Associations There are three relationships that sometimes occur in an object model: Assemblies of parts Members of groups Containers and their contents You may find these useful for making your model a better tool for understanding and communication. The model can always be built without these. They do not really affect its use for system design, just for talking to the users. Object Oriented Methodologies Jerry Kotuba

Assemblies of parts Taking something apart into its components is a technique we humans often use to understand how something works. Often we find it improves our understanding to model A product and its components A business consists of branches, departments, etc. A country consists of states, provinces, counties, boroughs, shires, towns, villages, cities, etc. Object Oriented Methodologies Jerry Kotuba

Containers and their contents Container-Contents is a different and less common relationship. In some situations we may find it helpful to view a relationship as one of these, e.g., Truck or Aircraft and the Products or Shipments that it carries An actual shipping container and the goods it holds A ship, bus or airplane and its passengers A building and the businesses it houses. Object Oriented Methodologies Jerry Kotuba

Assemblies of parts Vs Containers and their contents A Container, however, is still a perfectly good Container, even without its Contents The jar is still OK even without the “hunny.” And the Contents are perfectly OK without the Container (although the “hunny” might get all over one’s paws!) The essential difference between these relationships is that: With Assemblies of parts, if you take the component away, the assembly (whole) probably won’t work any more Take a wheel off a car Take a hand off a clock Take a leg off a table. Jerry Kotuba Object Oriented Methodologies

Collection-Member (members of groups) Collection-Member is also a different and relatively uncommon relationship. Sometimes we meet an actual collection: A library full of books An art gallery A stamp or jewelry collection A fleet of trucks, ships or aircraft Other times it may help to use this to describe: A church, club or regiment and its members An inventory of furniture or equipment A herd, mob, flock, school or skein of animals. Jerry Kotuba Object Oriented Methodologies

Your Turn… Think about a book, which consists of a cover, table of contents, chapters and an index. Chapters in turn have pages, paragraphs and words. Show the special case of association between classes described here including the multiplicity. Object Oriented Methodologies Jerry Kotuba

Test Review See ICE’s on SLATE Plus Exercises 1,2,3,&4 Object Oriented Methodologies Jerry Kotuba

Test Review Permitted a “cheat sheet” Satzinger – Chapters 1,2,4,5,6 (Chap 6 only to page 225 –including Activity diagrams) Plus all material covered in class…check PPTs 10 modified T/F and 15 M/C questions Exercises Event table Use Case Diagram Includes (a.k.a. Uses) Activity Diagram Class Diagram Relationships ( Multiplicity) Association Classes Subclasses & Inheritance (incl. constraint & Discriminator Notation) Generalization & Specialization Abstract Classes Permitted a “cheat sheet” One 8 ½ X 11 sheet only (both Sides) Object Oriented Methodologies Jerry Kotuba

Next class… Mid-term test Object Oriented Methodologies Jerry Kotuba

Your turn…ICE-05 SLATE2 Object Oriented Methodologies Jerry Kotuba