Understand and Use Object Oriented Methods

Slides:



Advertisements
Similar presentations
UML Class Diagram. UML Class Diagrams2 Agenda What is a Class Diagram? Essential Elements of a UML Class Diagram Tips.
Advertisements

2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
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.
Class Diagram & Object Diagram
Page 1  Copyright © 1997 by Rational Software Corporation Class Diagrams A class diagram shows the existence of classes and their relationships in the.
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.
Overview Objective: refine information gathered
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
UML Class Diagrams: Basic Concepts. Objects –The purpose of class modeling is to describe objects. –An object is a concept, abstraction or thing that.
The Unified Modeling Language (UML) Class Diagrams.
UML Unified Modeling Language. What is UML? Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software.
Conceptual Data Modeling. What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
UML Diagrams: Class Diagrams The Static Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
Databases : Data Modeling 2007, Fall Pusan National University Ki-Joune Li.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
Chapter 16 Applying UML and Patterns Craig Larman
1 Class Diagrams: The Essentials. 2 Terms and Concepts A class is... The most important building block of any object-oriented system. A description of.
The Static Analysis Model Class Diagrams Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty of Computers and Information, Cairo University.
Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain.
UML Diagrams: The Static Model Class Diagrams. The Static Model Define the static structure of the logical model Represent classes, class hierarchies.
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.
Lecture 1: UML Class Diagram September 12, UML Class Diagrams2 What is a Class Diagram? A class diagram describes the types of objects in the system.
Design Model Lecture p6 T120B pavasario sem.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
 Building Block Building Block  Things in the UML Things in the UML  Structural Things Structural Things  Behavioral Things Behavioral Things  Grouping.
Chapter 4 Extended Entity-Relationship (EER)Model Incorporates Set-subset Relationships Incorporates Generalization Hierarchies Constraints: Coverage Constraints:
1 Introduction to Classes. 2 Terms and Concepts A class is... –The most important building block of any object- oriented system. –A description of a set.
CS212: Object Oriented Analysis and Design Lecture 33: Class and Sequence Diagram.
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.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Data Modeling Using the Entity- Relationship (ER) Model
Appendix 3 Object-Oriented Analysis and Design
UML Diagrams: Class Diagrams The Static Analysis Model
Object-Oriented Modeling
DATA REQIREMENT ANALYSIS
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Class Diagrams.
Object-Oriented Modeling with UML
Entity-Relationship Model
Analysis and Design with UML: Discovering Classes and Relationships
Entity-Relationship Modeling
Analysis and Design with UML: Discovering Classes and Relationships
Software Engineering System Modeling Chapter 5 (Part 2) Dr.Doaa Sami
UML Class Diagrams: Basic Concepts
Analysis and Design with UML: Discovering Classes and Relationships
UML Diagrams: The Static Model Class Diagrams
Object Oriented Analysis and Design
Lec 3: Object-Oriented Data Modeling
Object Oriented Analysis and Design Using the UML
UML Class Diagram.
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
SYS466 Domain Classes – Part 1.
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
Copyright 2007 Oxford Consulting, Ltd
Analysis and Design with UML: Classes and Relationships
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
ITEC324 Principle of CS III
From Class Diagram to Contract Diagram
Presentation transcript:

Understand and Use Object Oriented Methods Session 3 Understand and Use Object Oriented Methods

Review OOAD refers to the development of systems with the base concept of objects and classes UML is a modeling tool used in Information systems Technical systems Embedded systems Distributed systems System software Business Systems SDLC refers to different phases in the software development process OOAD with UML / Session 3 / 2 of 25

Objectives Discuss the class diagram and object diagram Represent the relationships between classes Discuss the concept of object Model Identify classes during analysis OOAD with UML / Session 3 / 3 of 25

Class and Object Class - A class is a description of a group of objects with common properties (attributes), behavior (Operations), relationships, and semantic Object - An object represents an entity, either physical, conceptual, or software OOAD with UML / Session 3 / 4 of 25

Class Diagram-1 Class Object OOAD with UML / Session 3 / 5 of 25

Class Diagram-2 Class Names Class Attributes Class Methods Constraints Comment OOAD with UML / Session 3 / 6 of 25

Representation of Relationship Multiplicity-Multiplicity defines how many objects participate in a relationship OOAD with UML / Session 3 / 7 of 25

Multiplicity & Navigation Student Schedule Navigation Multiplicity 0..* 1 Define Navigation OOAD with UML / Session 3 / 8 of 25

Aggregation An aggregation is a stronger form of relationship where the relationship is between a whole and its parts Student Schedule Aggregation Whole Part OOAD with UML / Session 3 / 9 of 25

Aggregation-Composition Composition is a form of aggregation with strong ownership and coincident lifetimes of the part with the aggregate Student Schedule Aggregation Whole Part OOAD with UML / Session 3 / 10 of 25

Aggregation-Dependency A dependency relationship is a weaker form of relationship OOAD with UML / Session 3 / 11 of 25

Aggregation-Generalization A specialization/generalization relationship is one, in which objects of the specialized element (the child) are substitutable for objects of the generalized element (the parent) Superclass Subclass OOAD with UML / Session 3 / 12 of 25

Association Association is a connection between classes Professor University Works for Class Association Name Role Names Employer Employee OOAD with UML / Session 3 / 13 of 25

Constraints of Association An association may have a name that is placed on, or adjacent to the association path The name of the association should reflect the purpose of the relationship and be a verb phrase; the name of an association can be omitted, particularly if roles names are used. Names like “has” and “contains should be avoided”, as they add no information about what the relationships are between the classes. Each end of an association is a role specifying the face that a class plays in the association (not a constraint). Each role must have a name, and the role names must be unique. The role name should be a noun indicating the associated object’s role in relation to the associating object. The use of association names and role names are mutually exclusive: one should not use both an association name and role name. For each association, it needs to decide as to which conveys more information. OOAD with UML / Session 3 / 14 of 25

Association Classes OOAD with UML / Session 3 / 15 of 25

Qualified Association Theatre Seat 1 99 Theatre Seat 1 Row {1,2,…9} Column {1,2,..11} OOAD with UML / Session 3 / 16 of 25

Recursive Association OOAD with UML / Session 3 / 17 of 25

Inheritance and Generalization-1 OOAD with UML / Session 3 / 18 of 25

Inheritance and Generalization-2 The mechanism for sharing attributes and operations using the principle of generalization is referred to as inheritance OOAD with UML / Session 3 / 19 of 25

Same Association or Aggregation OOAD with UML / Session 3 / 20 of 25

Interface OOAD with UML / Session 3 / 21 of 25

Object Model Language independent Notation allowing the specification of classes, their data or attributes (private) and methods (public), inheritance This diagram depicts the structural relationship and functional behavior of the classes OOAD with UML / Session 3 / 22 of 25

How to Identify Classes? Tangible things Events Roles played Interactions Location Organizational Units Nouns in problem statement Knowledge of the problem domain Use Cases Physical entities Devices Events Roles played Operational procedures Sites Organisational units The Requirements statement Use Cases Application experts Studying the system Similar systems Previous systems OOAD with UML / Session 3 / 23 of 25

Candidate Classes OOAD with UML / Session 3 / 24 of 25

Summary A class icon is a rectangle with three sections within it Association is a connection between classes An interface is a collection of operations that are used to specify a service of a class or a component Object Model generally deals with classes OOAD with UML / Session 3 / 25 of 25