 Kia Manoochehri ◦  Office Hours: 2:30-4:00 M/W ◦ HEC 308 (The Cave)

Slides:



Advertisements
Similar presentations
UML & Together 2006 tutorial Hong Qing Yu 10/2006.
Advertisements

Improved software quality through semantic descriptions (Skutt) Karlstad University Dept. of Computer Science UML introduction A short introduction.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Page 1  Copyright © 1997 by Rational Software Corporation Class Diagrams A class diagram shows the existence of classes and their relationships in the.
IMSE 11 - UML Class Diagrams
MORE ON CLASS MODELS Lecture Outline Aggregation and composition Roles Navigability Qualified association Derived association Constraints Association.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
© The McGraw-Hill Companies, 2006 Chapter 7 Implementing classes.
Unified Modeling Language
Relationships. In the Interaction diagrams, we began to look at how classes communicate with one another. Now, we'll focus on the relationships between.
CS 2511 Fall UML Diagram Types  2 Main Types Structure Diagrams ○ Class Diagrams ○ Component Diagrams ○ Object Diagrams Behavior Diagrams ○
 2008 Pearson Education, Inc. All rights reserved (Optional) Software Engineering Case Study: Identifying the Classes in the ATM Requirements.
Association & Aggregation Lecture-9. Vehicle Car Tyre Engine Bus Passenger.
Introduction to UML Lian Yu Department of Computer Science and Engineering Arizona State University Tempe, AZ
UML Unified Modeling Language. What is UML? Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software.
OBJECT ORIENTED PROGRAMMING LECTURE 12 Instructor: Rashi Garg Coordinator: Gaurav Saxena.
1 Announcements Research Paper due Friday November 19 For Wednesday read
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes.
Lab 04.
Distributed Java Programming Distributed Java Programming Class #2 August 22, 2002.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
Unit 1 INTRODUCTION TO MODELING AND CLASS MODEL Ref : L7-UML.PDF.
UML Diagrams: The Static Model Class Diagrams. The Static Model Define the static structure of the logical model Represent classes, class hierarchies.
(Reference: Jason Roff – UML Beginner’s Guide).  Box  Top section is class name  Second section is class attributes (data members)  Third section.
BCS 2143 Object Oriented Design Using UML. Objectives Objects Interactions Finding Classes Relationship Between Classes Attribute and Operation Class.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Design Jon Walker. More UML ● What is UML again?
Class Diagram. Classes Software Design (UML) Class Name attributes operations A class is a description of a set of objects that share the same attributes,
Design Model Lecture p6 T120B pavasario sem.
Object Oriented Analysis: Associations. 2 Object Oriented Modeling BUAD/American University Class Relationships u Classes have relationships between each.
Object Oriented Analysis and Design Class and Object Diagrams.
Class Modeling Design Class diagram. Classes The term “class ” refers to a group of objects that share a common attributes and common behaviour (operations).
Database Design – Lecture 12 Object Oriented Database Design cont’d.
Class Diagram Chapter 21 Applying UML and Patterns Craig Larman.
CS212: Object Oriented Analysis and Design Lecture 33: Class and Sequence Diagram.
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
 Class diagrams show the classes of the system, their interrelationships (including inheritance, aggregation, and association), and the operations and.
INFSY 535.  Small systems  Larger systems 1.Understand the program requirement- what 3. Write and test each part (unit testing) 4. Maintenance 2. Specify.
Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A.
Basic ER modeling was adequate for simpler databases, but in the 1980’s more demanding databases required more extensive modeling requirements. Some such.
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.
Department of Electrical Engineering and Computer Science University of Central Florida Fall 2014.
Class Diagrams Revisited. Parameterized Classes Parameterized Classes - are used to represent relationships between templates.
25/2/16. Software Design (UML) ClassName attributes operations A class is a description of a set of objects that share the same attributes, Operations.
Inf 43: Introduction to Software Engineering May 7, 2016.
Class Diagram Associations Class Diagrams, Class Stereotypes, Class Associations Dr. Neal CIS 480.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Unified Modeling Language (UML)
Object-Orientated Analysis, Design and Programming
COMP 2710 Software Construction Class Diagrams
UML SEQUENCE AND CLASS DIAGRAMS
UML PPt by: Hong Qing Yu.
Showing Relationships in UML
Introduction to UML Introduction to UML Shiyuan Jin September,23,2002
COP 4331 Recitation #2 University of Central Florida
UML Diagrams: The Static Model Class Diagrams
Unified Modeling Language
Domain Class Diagram Chapter 4 Part 2 pp
Software Engineering Lecture #11.
Software Engineering Lecture 10.
Software Engineering System Modeling Extra examples Dr.Doaa Sami
Class and Object Diagrams
Understand and Use Object Oriented Methods
Class Diagrams Class diagram is basically a graphical representation of the static view of the system and represents different aspects of the application.
Class Diagram.
Object Oriented System Design Class Diagrams
Information System Design
UML & Together 2006 tutorial
From Class Diagram to Contract Diagram
Presentation transcript:

 Kia Manoochehri ◦  Office Hours: 2:30-4:00 M/W ◦ HEC 308 (The Cave)

Class & Sequence Diagrams

 Each class is divided into three components:

Class Name

 Each class is divided into three components: Class Name Attributes

 Each class is divided into three components: Class Name Attributes Attributes can be: + Public - Private # Protected

 Each class is divided into three components: Class Name Attributes Operations

Patron

# ID_Number : integer +Name : String - Fines : double

Patron # ID_Number : integer +Name : String - Fines : double checkFines() payFines()

 Class diagrams also contain information regarding the relationship between them ◦ Association ◦ Dependency ◦ Generalization

 Association: A link indicating that two classes need to communicate with one another StudentProfessor

 Association: A link indicating that two classes need to communicate with one another ◦ Multiplicity: Every professor has 1 or more students StudentProfessor [1…*]

 Association: A link indicating that two classes need to communicate with one another ◦ Multiplicity: Every professor has 1 or more students ◦ Role Names: Students learn from Professors StudentProfessor learns from teaches

 Aggregation: “has a” association. Each part exists outside of the whole  Shown by using an empty diamond Car Wheel Engine

 Composition: demonstrates strong ownership, the part cannot exist without the whole and vice versa  Shown by using a filled diamond Person Arm Leg

 Dependency relationship: ◦ Is a semantic relationship between classes because the functionality of one depends on the other Calendar addEvent(p: Party) Party

 Generalization: connection between a subclass and a superclass People StudentProfessor

 Sequence diagrams emphasis the time ordering of messages

◦ Objects create the “object life line”

 Messages are shown by a horizontal line between life lines ◦ May include a condition CustomerBank withdraw money

 A return message is a response from the object CustomerBank withdraw money money

 The end of an object life line is demonstrated by an X Bank

Class & Sequence Diagrams