Object Modeling THETOPPERSWAY.COM. Object Modelling Technique(OMT)  Building a model of an application domain and then adding implementation.

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

Computer Science Dept. Fall 2003 Object models Object models describe the system in terms of object classes An object class is an abstraction over a set.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
7M701 1 Class Diagram advanced concepts. 7M701 2 Characteristics of Object Oriented Design (OOD) objectData and operations (functions) are combined 
Unified Modeling Language (UML)
Class Diagram & Object Diagram
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
7M822 UML Class Diagrams advanced concepts 15 September 2008.
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
7M822 UML Class Diagrams advanced concepts 14 October 2010.
Object Oriented Concepts. Movement toward Objects Instead of data-oriented or process-oriented Analysis, many firms are now moving to object-oriented.
1 Object-Oriented Modeling Using UML CS 3331 Fall 2009.
Unified Modeling Language
Object-Oriented Analysis and Design
UML Diagrams Computer Science I.
UML Unified Modeling Language. What is UML? Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software.
1 A Student Guide to Object- Orientated Systems Chapter 4 Objects and Classes: the basic concepts.
OBJECT AND CLASES: THE BASIC CONCEPTS Pertemuan 8 Matakuliah: Konsep object-oriented Tahun: 2009.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
What is MOF? The Meta Object Facility (MOF) specification provides a set of CORBA interfaces that can be used to define and manipulate a set of interoperable.
Object-Oriented Modeling Using Modified Modeling Language (UML)
Object-Oriented Modeling Using Modified Modeling Language (UML)
Object-Oriented Software Development F Software Development Process F Analyze Relationships Among Objects F Class Development F Class Design Guidelines.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
Chapter 7 System models.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Unified Modeling Language © 2002 by Dietrich and Urban1 ADVANCED DATABASE CONCEPTS Unified Modeling Language Susan D. Urban and Suzanne W. Dietrich Department.
The Static Analysis Model Class Diagrams Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty of Computers and Information, Cairo University.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
UML Class Diagram Trisha Cummings. What we will be covering What is a Class Diagram? Essential Elements of a UML Class Diagram UML Packages Logical Distribution.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Advanced UML Class Diagrams.
Design? !… When it needs? To understand, to communicate with customers Complex problem What is good design? Separate What to do?(Policy) and How to do(mechanism)
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Modeling the Static Structure: Relationships ©SoftMoore ConsultingSlide 1.
Class diagrams Terézia Mézešová.
Chapter 16 UML Class Diagrams 1CS6359 Fall 2012 John Cole.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
 Class diagrams show the classes of the system, their interrelationships (including inheritance, aggregation, and association), and the operations and.
Object Oriented Analysis and Design Using the UML
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
Class Diagrams Revisited. Parameterized Classes Parameterized Classes - are used to represent relationships between templates.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Data Modeling Using the Entity- Relationship (ER) Model
UML Diagrams: Class Diagrams The Static Analysis Model
Visit for more Learning Resources
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Class Diagrams.
Abstract descriptions of systems whose requirements are being analysed
Object Oriented Analysis and Design
Software Engineering Lecture #11.
Chapter 20 Object-Oriented Analysis and Design
Object Oriented System Design Class Diagrams
Presentation transcript:

Object Modeling THETOPPERSWAY.COM

Object Modelling Technique(OMT)  Building a model of an application domain and then adding implementation details to it.  Following four stages:- –Analysis; –System Design; –Object Design; –Implementation.

Three Models  Object Model – describes the static structure of objects in the system and their relationships.  Dynamic Model – describes the aspect of the system that change over time, i.e. interaction among objects.  Functional Model – describes data value transformation in the system.

Object Model  Describes the structure of objects in a system- - Identity - Relationship to other objects - Their attributes - And their operations.

Dynamic Model  Describes those aspects of the system concerned with time and sequencing of operations-  Events that make change  Sequence of events  States that define context of events  And organization of events and states.

Functional Model  Describes those aspects of the system concerned with transformation of values-  Functions  Mappings  Constraints  Functional dependencies  Is represented with Data Flow Diagrams.

CS 3300 Object-Oriented ConceptsObject-Oriented Modeling Using UML12 Objects and Classes Interpretation in the Real WorldInterpretation in the Model Object An object is a thing that can be distinctly identified. An object has an identity, a state, and a behavior. Class A class represents a set of objects with similar characteristics and behavior. This objects are called the instances of the class. A class characterizes the structure of states and behaviors that are shared by all instances.

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 13 Objects  Each of object has a unique identity.  The state of an object is composed of a set of fields (data fields), or attributes.  Each field has a name, a type, and a value.  Behaviors are defined by methods.  Each method has a name, a type, and a value.  Each method may or may not return a value.  Features are a combination of the state and the behavior of the object.

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 14 Classes  A class defines a template for creating or instantiating its instances or objects.  A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics.

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 15 Example Class name: Point class Point { Fields: x, y int x, y; Method: move public void move (int dx, int dy){ (int dx, int dy){ // implementation // implementation }

CS 3300 Object-Oriented ConceptsObject-Oriented Modeling Using UML16 UML Notation for Classes ClassName The top compartment shows the class name. field 1 … field n The middle compartment contains the declarations of the fields of the class. method 1 … method m The bottom compartment contains the declarations of the methods

Object Model Notations –Object classes are rectangles with the name at the top, attributes in the middle section and operations in the bottom section;

CS 3300 Object-Oriented ConceptsObject-Oriented Modeling Using UML18 UML Notation for Object ObjectName : ClassName The top compartment shows the object name and its class. field 1 = value 1 … field n = value n The bottom compartment contains a list of the fields and their values. objectName -- objectName whose class is of no interest :ClassName -- anonymous object of ClassName which can be identify only through its relationship with other object.

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 19 Examples P1:PointPoint p1 = new Point(); x = 0 y = 0 p1.x = 0; P1.y = 0; P1:PointPoint p1 = new Point(); x = 24 y = 40 p1.x = 24; P1.y = 40;

Object Model Notations (Contd.) –Relationships between object classes (known as associations) are shown as lines linking objects

Example (Line) L1 (Point) P2 (Point) P1 Intersects (Line) L2 (Line) L3 (Line) L4 Instance Diagram Class Diagram Line name Point name Intersects 2+ L3 L1 L2 L4 P1 P2 Sample Data

 Connection between objects  Solid line –Direction optional –Arrowhead depends on meaning  Name (optional)  Multiplicities (optional)  Visibility (optional) Associations

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 23 Association  Association represents binary relationship between classes StudentCourse Faculty advisee adviser * enroll teach ** 1 1 *

Aggregation  An aggregation model shows how classes that are collections are composed of other classes.  Aggregation models are similar to the part-of relationship in data models.

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 25 Aggregation and Compositon  Aggregation is a special form of association –Has-a or part-whole relationship  Composition is a stronger form of aggregation

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 26 Example UniversityDepartment Faculty Chairman-ofMember-of ** CollegeStudent * *

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 27 Inheritance  Define a relationship among classes and interfaces  Inheritance model -- the is-a(n) relationship

CS 3300 Object-Oriented Concepts Object-Oriented Modeling Using UML 28 Example

Multiple inheritance

Generalization  Models the concept of inheritance  Subclasses inherit the attributes and operations of all their superclasses  Objects of a subclass should be substitutable for objects of their superclasses  Uses hollow triangle arrowhead on superclass

Generalisation Example GeneralizationSpecialization

Abstract Classes  Used to hold common operations and data  Used in inheritance hierarchy –Derived (child) classes provide implementations  Documented with class name in italics –Can also use {abstract} property Shape {abstract} +move() +erase() : void {abstract} +draw() : void {abstract}

Constraints  A restriction in the design  Documented inside curly braces {} attached to any diagram element Window length width {0.5<(length/width)<1.5}

Metadata  Data about data.  Data that describes other data.  Metadata is defined as data providing information about one or more aspects of the data, such as: o Means of creation of the data o Purpose of the data o Time and date of creation o Creator or author of data o Location on a computer where the data was created.

Candidate Keys  Minimal set of attributes that uniquely identifies an object or link.  It is denoted by braces {C.K.} {Candidate key:(Person, Company)} Person name Company name Works-for

THANKS….  THETOPPERSWAY.COM