Module 3 Object Oriented Data Models Object Oriented notations


Published on

Module 3 Object Oriented Data Models- Object Oriented notations.

Published in: Education, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Module 3 Object Oriented Data Models Object Oriented notations

  1. 1. ER Diagramming Models for OO Relationships DOEACC B-Level OODBMS 2011 Taher S. 3.Object Oriented Data Model
  2. 7. Models as Analysis and Design Methods <ul><li>Object technology has many different methodologies to help analyze and design computer systems.   </li></ul><ul><li>  In most cases these methodologies are very similar, but each has its own way to graphically represent the entities. </li></ul><ul><li>To understand and use these methodologies would become difficult, if not impossible, for all projects.  If need be, it is possible to use concepts from one method with concepts from another technique, basically creating your own object development technique. </li></ul><ul><li>The most important point is to remember is that the final outcome is what really matters, not the choice of one analysis technique over another technique. </li></ul>
  3. 8. Methodologies: <ul><li>Coad-Yourdon </li></ul><ul><ul><li>Developed in the late 80’s </li></ul></ul><ul><ul><li>Five-step analysis method </li></ul></ul><ul><li>Shlaer-Mellor </li></ul><ul><ul><li>Developed in the late 80’s </li></ul></ul><ul><ul><li>Emphasizes modeling information and state, rather than object interfaces </li></ul></ul><ul><li>OMT Notation </li></ul><ul><li>UML Notation </li></ul><ul><li>Booch Notation </li></ul>
  4. 9. Coad- Yourdon <ul><li>Their methodology is based on a technique called &quot;SOSAS&quot;, which stands for the five steps that help make up the analysis part of their methodology. </li></ul><ul><li>Following analysis, Coad and Yourdon define four parts that make up the design part of their methodology. The steps of system design are: </li></ul><ul><ul><li>The problem domain component - This will define the classes that should be in the problem domain.  </li></ul></ul><ul><ul><li>The human interaction component - These steps defines the interface classes between objects.  </li></ul></ul><ul><ul><li>The task management component - This is where system-wide management classes are identified.  </li></ul></ul><ul><ul><li>The data management component - This design step identifies the classes needed for database access methods. </li></ul></ul>
  5. 10. Coad Yourdon- Analysis Part
  6. 11. Coad Subject Diagrams Gen- Spec Relationship Whole- Part Relationship
  7. 12. Shlaer- Mellor <ul><li>Shlaer-Mellor methodology has its primary strength in system design and is considered somewhat weak on analysis. </li></ul><ul><li>The Shlaer-Mellor methodology includes three models; the information model, the state model, and the process model.  </li></ul><ul><li>Developed by Sally Shlaer and Stephen Mellor, this system is also known as the Object-Oriented Systems Analysis (OOSA). </li></ul><ul><li>OOSA contains a wide variety of diagrams including: a domain chart diagram, object information model diagram, state transition model, an action data flow diagram, a class diagram, and a class structure chart. </li></ul>
  8. 13. Shlaer- Mellor
  9. 14. Shlaer Mellor- Domain Chart
  10. 15. Shlaer- Mellor- Relationships
  11. 16. Shlaer Mellor - Inheritance
  12. 17. OMT Notation <ul><li>James Rumbaugh's Object Modeling Technique (OMT) is one of the precursors to the Unified Modeling Language (UML). There are three main diagrams in OMT: object, dynamic, and functional. </li></ul><ul><li>Object View Diagrams </li></ul><ul><ul><li>The OMT object model illustrates the static relationship among classes and objects in a system. This diagram is similar to the UML object and class diagrams. </li></ul></ul><ul><li>The OMT Dynamic Diagram Notations </li></ul><ul><ul><li>The OMT dynamic models resemble UML sequence and UML statechart diagrams. </li></ul></ul><ul><li>The OMT Static Diagram Notations </li></ul><ul><ul><li>The OMT static models consist of multiple data flow diagrams. </li></ul></ul>
  13. 18. OMT – Object Diagram
  14. 19. OMT- Other Diagrammatic Notations <ul><li>Objects: Draw an object using a rectangle with rounded corners. Attributes must have values assigned to them. </li></ul><ul><li>Linked Attribue: To describe the properties of a link or association, you can use an arc to attach an attribute to the relationship. </li></ul>
  15. 20. OMT- Other Diagrammatic Notations <ul><li>Qualified associations: Qualifier  used to distinguish among the set of objects in the  many end  of the association. </li></ul><ul><li>  The qualified association is unique to the OMT notation. Place the qualifier box at the end of the association, near the class you want to qualify. </li></ul>
  16. 21. Booch Notation <ul><li>Grady Booch's Object-Oriented Design (OOD), also known as Object-Oriented Analysis and Design(OOAD), is a precursor to the Unified Modeling (UML). The Booch method includes six types of diagrams: class, object, state transition, interaction, module, and process. </li></ul><ul><li>Booch Class and Object Diagrams: </li></ul><ul><ul><li>Classes: Illustrate classes using a cloud shape with a dashed border. </li></ul></ul><ul><ul><li>Objects: Draw objects using a cloud shape with a solid border. </li></ul></ul>
  17. 22. Booch Class and Object Diagrams: <ul><li>Class Adornments: </li></ul><ul><li>Use adornments to provide additional information about a class. You can create an adornment notation using the basic triangle shape. </li></ul><ul><li>Place a letter inside the triangle to represent the following: </li></ul><ul><li>A - Abstract.  An abstract class cannot be instantiated because it represents a wide variety of object classes and does not represent any one of them fully. For example, mammal could be thought of as an abstract class. F - Friend.  A friend class allows access to the nonpublic functions of other classes. S - Static.  A static class provides data. V - Virtual.  A virtual class is a shared base class, the most generalized class in a system. </li></ul>
  18. 23. Booch Class and Object Diagrams: A Booch class Diagram