Use Case realization How classes collaborate to realize use cases or system functionality.

Slides:



Advertisements
Similar presentations
1 Behavioral Modeling Chapter 8. 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports business processes.
Advertisements

ZEIT2301 Design of Information Systems Behavioural Design: State Machines School of Engineering and Information Technology Dr Kathryn Merrick.
Chapter 6: Behavioral Modeling
Assess A Claim Object Interaction Diagrams. Object sequence Diagrams - Use case Sequence of events that occur during one particular execution of a system.
Object-Oriented Analysis and Design
Software Engineering COMP 201
Slide 1 Systems Analysis & Design CS183 Spring Semester Dr. Jonathan Y. Clark Course Website:
Activity, Collaboration, and Component Diagrams Philip Liew
1 © Wolfgang Pelz UML2 UML Part Two. 2 © Wolfgang Pelz UML2 Chapters Four & Twelve Interaction Diagrams.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
7M822 UML Interaction Diagrams 25 November 2010.
Unified Modeling Language 7/12/2015B.Ramamurthy1 The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson, and Jim Rumbaugh.
Slide 1 Chapter 8 Behavioral Modeling. Slide 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports.
SE-565 Software System Requirements More UML Diagrams.
Unified Modeling Language
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
1 Object-Oriented Testing CIS 375 Bruce R. Maxim UM-Dearborn.
UML Collaboration Diagram. Recap System Sequence Diagrams (SSD) UML for SSD Examples.
Interactions. 2 Objects communicate with each other by sending messages. Sending a message is another name for a member function call. –Some C++ examples.
Class, Sequence and UML Model.  Has actors and use cases.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
Interaction diagrams Sequence and collaboration diagrams.
Chapter 5 – System Modeling
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.
CSC 395 – Software Engineering Lecture 13: Object-Oriented Analysis –or– Let the Pain Begin (At Least I’m Honest!)
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Behavioral Modeling Chapter 8.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Sequence diagram in UML Martin Palkovik. Sequence diagram  It is a graphic representation of system operations based on chronology - a time sequence.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
© 2008 Prentice Hall, Ovidiu Noran Lecture 7b 1 Modelling OO Logic Requirements: Sequence Diagrams and Activity Diagrams (Textbook Chapter 8, Appendix)
Chapter 7 The Object-Oriented Approach to Requirements.
Interaction Diagrams Interaction Diagrams allow the designer to show how groups of objects collaborate in some behavior. –Interaction Diagrams will show.
Object-Oriented Analysis and Design 1 Mira Balaban & Arnon Sturm Object-Oriented Analysis and Design Session 3a: Behavioral Modeling - Interactions.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
UNIFIED MODELING LANGUAGE(UML) BY Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
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.
Dynamic Models Sequence Diagrams Collaboration Diagrams Activity Diagrams.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
UML Review of Use case diagrams. 2 Unified Modeling Language The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson,
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Communication Diagrams Lecture 8. Introduction  Interaction Diagrams are used to model system dynamics  How do objects change state?  How do objects.
 The Sequence Diagram models the collaboration of objects based on a time sequence.  It shows how the objects interact with others in a particular scenario.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
1 Kyung Hee University Interaction Diagrams Spring 2001.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
More on UML 1. 1.Use-case diagram 2.Class diagram [Object diagram] (static) 1.1 Domain/analysis model – of reality 1.2 Design model – of decisions 3.
Chapter 7 Behavioral Modeling Brandon A. Jones Stand and Deliver ITEC March 6, 2011.
Test Generation from UML Specifications Michael A. Gray American University Washington, DC.
ITEC1301 Object-Oriented Systems Construction Lecture Notes #4 1.
Developing Business Processes Developing an activity diagram of the business processes can provide us with an overall view of the system.
Systems Analysis and Design in a Changing World, Fourth Edition
Analysis Classes Unit 5.
UML Diagrams By Daniel Damaris Novarianto S..
Interactions.
Sequence Diagram.
Communication DIAGRAM
University of Central Florida COP 3330 Object Oriented Programming
Activity Diagrams Activity diagrams describe the workflow behavior of a system.  The diagrams describe the state of activities by showing the sequence.
UML dynamic Modeling (Behavior Diagram)
Interactions.
Requirements To Design In This Iteration
Interaction diagrams Interaction diagrams are models that describe how groups of objects collaborate in some behavior. Typically, an interaction diagram.
Communication DIAGRAM
Presentation transcript:

Use Case realization How classes collaborate to realize use cases or system functionality

Analysis class diagrams Tells a story about the system Generic and valid for all implementations Involves classes and associations Describes the nature of interaction between classes Described using roles played by classifier

Interaction diagrams Describes object (instance) interaction Specifically describes how the objects collaborate and interact Collaboration diagram – describes structured relationships between objects Sequence diagram – describes time- ordered sequence of messages between objects

Collaboration is a static set of relationships between instances Interaction is a dynamic interaction – including specific messages Collaboration: Object A has a role with B Interaction: A plays with B, A studies with B, A …. with B Descriptor form – describes roles played by instances Shows - Context in which interaction may occur Instance form of collaboration diagram is between objects and has links

Class Diagram –Manager class has an association (named boss) to Supervisor Object Diagram: Collaboration –Peter:Manager has links to Jack:Supervisor –Assigntask, employ, and assist can be part of the boss role Object Interaction Diagram – for use-cases Peter object first requests addschedule(..) to ManageSchedule which then does updateschedule(..) to Jack object

Messages can be sent to multi-object. Messages sent to oneself are self- delegating requests One can depict branching and iterations as well Object creation and disposal are also shown when appropriate Concurrent objects are shown in bold boxes Object states can be clarified with curved edge boxes.

Sequence Diagram Similar to Object Interaction Diagram Shows a sequence of interactions involved in a use-case Objects are laid left to right and events are depicted top to bottom as they occur.

Activity Diagram Similar to flow chart – except uses OO elements It is a diagrammatic representation of the algorithm – and hence corresponds to the source code. Activity can be deemed atomic (can’t be broken down), uninterruptible, or instantaneous You have a start state and stop state

Decisions during activity Concurrent activity Flow of outputs from one activity to another can also be shown Sending and reception of signals (asynchronous communication of information) can also be represented

Which one to use? Collaboration diagram emphasize collaboration between objects. And roles played by instances Sequence diagram emphasize the interaction as time ordered sequence of messages between instances These two are isomorphic Activity diagrams are OO flow charts – models a process