15.1.2003Software Engineering 2003 Jyrki Nummenmaa 1 MORE UML DIAGRAM TYPES We have seen a number of UML diagram types while studying our example. These.

Slides:



Advertisements
Similar presentations
Withdrawal Transaction Use Case Primary Actor: Customer Pre-conditions: The customer must have a valid ATM card and PIN. Post-conditions: The customer.
Advertisements

Software Engineering 2003 Jyrki Nummenmaa 1 A BASIC OO SOFTWARE DEVELOPMENT PROCESS Earlier, we saw a number of different software lifecycle models.
Karolina Muszyńska Based on:
ESE Einführung in Software Engineering 7. Modeling Behaviour Prof. O. Nierstrasz.
UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student.
Introduction to Software Engineering 7. Modeling Behaviour.
Stereotypes Stereotypes provide the capability to create a new kind of modeling element. –They can be used to classify or mark modeling elements. –A type.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
CS 340 UML Class Diagrams. A model is an abstraction of a system, specifying the modeled system from a certain viewpoint and at a certain level of abstraction.
Interaction Diagrams Activity Diagram State Machine Diagram
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
SE 555 Software Requirements & Specification 1 Activity Diagrams.
Introduction to UML Part 2 Behavioral Modeling. Sequence (event) diagram Describes object interaction Typically captures behavior of a single use case.
Slide 10B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
Essentials of interaction diagrams Lecture 23 & 24.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
1 © Wolfgang Pelz UML2 UML Part 3. 2 © Wolfgang Pelz UML2 Chapter Ten State Machine Diagrams.
© Copyright Eliyahu Brutman Programming Techniques Course.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 10: Statecharts.
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
UML Overview. UML Diagrams to be Covered Class Diagrams Use Case Diagrams Collaboration Diagrams Sequence Diagrams Package Diagrams Component Diagrams.
Software Engineering 2003 Jyrki Nummenmaa 1 USE CASES In this lecture: Use cases - What are use cases? - Why to use use cases? - How to write.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
Class, Sequence and UML Model.  Has actors and use cases.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
(C) 2009 J. M. Garrido1 Object Oriented Simulation with Java.
程建群 博士(Dr. Jason Cheng) 年03月
Slide 16B.51 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering.
Introduction to UML By: Prof. Aiman Hanna Department of Computer Science, Concordia University, Montreal, Canada.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 9: Interaction.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Software Engineering Lecture 10 UML vs. ERD.
An Introduction to the Unified Modeling Language
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Michael Schloh von Bennewitz 1. Oktober 2002 The Unified Modeling Language Overview of theory and practice of the OMG Unified Modeling.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
UNIFIED MODELING LANGUAGE(UML) BY Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore.
System Sequence Diagram Chandan Rupakheti & Steve Chenoweth Week 5-3a.
Software Engineering Lecture 8 Object-Oriented Analysis.
OMT Modeling 1. Object Model : presented by the object model and the data dictionary. 2. Dynamic Model: presented by the state diagrams and event flow.
(14-2) UML Instructor - Andrew O’Fallon CptS 122 (December 2, 2015) Washington State University.
Slide 1 Classes and Objects. Slide 2 Messages and Methods.
Zhang Shuang Software Engineering Zhang Shuang 1.
Essentials of Visual Modeling w/ UML Instructor Notes
TK2023 Object-Oriented Software Engineering CHAPTER 9 INTRODUCTION TO OBJECT DESIGN.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 10: Statecharts.
Chapter 3: Introducing the UML
UML ACTIVITY DIAGRAM 1. Recap Formal Use Case diagram UML notation for use cases Examples 2.
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
UML (Unified Modeling Language)
Inf 43: Introduction to Software Engineering May 7, 2016.
UML Diagrams By Daniel Damaris Novarianto S..
The Movement To Objects
Review for Midterm, Fall 2009
Unified Modeling Language
Communication DIAGRAM
UML Diagrams Jung Woo.
State Machine Diagrams
UML State machine diagram
Communication DIAGRAM
CHAPTER 2 Object-Oriented Modeling Using UML (Continued)
Sylnovie Merchant, Ph.D. MIS 161 Spring 2005
Presentation transcript:

Software Engineering 2003 Jyrki Nummenmaa 1 MORE UML DIAGRAM TYPES We have seen a number of UML diagram types while studying our example. These slides show examples of a number of diagrams types not seen in our previous slides. Again, for full notation and syntax, refer to

Software Engineering 2003 Jyrki Nummenmaa 2 car1: Sedan registration_no = XYZ-999 : Garage car2 : Sedan registration_no = ABC-123 Object diagram car2 is an instance of class Truck This is really like a class diagram, but has objects instead of classes.

Software Engineering 2003 Jyrki Nummenmaa 3 Constraints Person wife husband 0..1 sex {(self.husband->size=1 implies self.husband.sex = male) and (self.wife->size=1 implies self.wife.sex = female) and not(self.wife->size=1 and self.husband->size=1)} {xor} Ministry Company manage own 0..1 * 1 1 OCL-language

Software Engineering 2003 Jyrki Nummenmaa 4 car: Sedan garage: Garage : GarageControl 1: returnCar 1.2: store(car) 1.1: return() GUI Collaboration Diagram Shows the calls between classes, but not their order (which is shown in sequence diagrams).

Software Engineering 2003 Jyrki Nummenmaa 5 State Diagram A state diagram represents how objects (instances of a class) react to external events (message). –Typically used to specify the behaviour of so- called active objects. –Is composed of states (combination of attribute values at some point of time) and transitions between them. –May include an initial state and a final state.

Software Engineering 2003 Jyrki Nummenmaa 6 Available InService Booked InUse return/ Stop counting time book take/ Start counting time service exit/ ready State Diagram Initial state

Software Engineering 2003 Jyrki Nummenmaa 7 Activity diagram An activity diagram represents how an activity is performed –Formally, this is a special case of a state diagram –Typically a higher-level activity with several actors. –The diagram can be partitioned into columns, which show the actors

Software Engineering 2003 Jyrki Nummenmaa 8 Query Book Make a bill Pay Prepare car Register rental Client Official Take car :Bill [open] :Bill [paid] Activity Diagram Fork threads Join threads Initial state Final state

Software Engineering 2003 Jyrki Nummenmaa 9 Objects Support Object Garage Sedan Storage registrationNo service(int km) return() ObjectManagement use * returnObject(Object,Storage) bookObject(Object) takeObject(Object) return() book() take() Controller Packages

Software Engineering 2003 Jyrki Nummenmaa 10 Support Database Packages in closed form