Use Cases and Object Interaction CS 123/CS 231. Depicting System Behavior zFirst, identify the use cases ÕUse case: typical interaction between a user.

Slides:



Advertisements
Similar presentations
Requirements Diagrams With UML Models
Advertisements

Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself A set.
BTS430 Design Model: Sequence Diagrams involving collections.
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
1 Behavioral Modeling Chapter 8. 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports business processes.
Interaction Diagrams CS 124. Object collaboration A use case carried out involves objects and interaction or collaboration between these objects Method.
Use cases.
Chapter 15: System Modeling with UML
Introduction To System Analysis and Design
Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,
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.
Overseas Library Catalog – Request Item Overseas Library Catalog Request loaned item.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Sequence Diagrams By Zvika Gutterman Adam Carmi. Agenda Interaction Diagrams A First Look at Sequence Diagrams Objects Messages Control Information Examples.
Sequence Diagrams By Zvika Gutterman Adam Carmi. Sequence Diagrams2 Agenda Interaction Diagrams A First Look at Sequence Diagrams Objects Messages Control.
Object Interaction Modeling
Slide 1 Chapter 8 Behavioral Modeling. Slide 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports.
Sequence Diagrams By Zvika Gutterman Adam Carmi. Sequence Diagrams2 Agenda Interaction Diagrams A First Look at Sequence Diagrams Objects Messages Control.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
VCE IT Theory Slideshows
Unified Modeling Language
Chapter 7: The Object-Oriented Approach to Requirements
It is not necessary to login to use the card catalog, but extra features are available when you are logged in. It is the same user name and password as.
CMPT 275 Software Engineering
Chapter 2 (Horstmann’s Book) – Part 2 The Object-Oriented Design Process Hwajung Lee.
Introduction to Sequence Diagrams
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 25. Review Design Level Class Diagram Identifying classes/Operations/Attributes Associations – Simple associations.
1 Object orientation. 2 What benefits does OO give? Primarily –Encapsulation (Associates data & operations) –Types & specialisation –Software re-use.
1 Sub-Phase Low Level Design (cont). Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces.
Introduction To System Analysis and Design
10/17/01H-1 © 2010 T. Horton CS 4240: Principles of SW Design Interaction Diagrams Examples of Collaboration and Sequence Diagrams Phone modeling exercise.
Dynamic Modeling Chapter 11 Part of Analysis Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Other UML Diagramming Techniques CS 124. UML Diagramming Techniques Class Diagrams Use Case Diagrams Interaction Diagrams Sequence diagrams Collaboration.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
Structured Design and Modeling CS 123/CS 231. Design Models Revisited zUML: Modeling Language for OO Systems zFor the Procedural (Structured) Paradigm.
3M Cloud Library and iOS How do I get started?. To download eBooks from both Overdrive and the 3M Cloud Library, set up an Adobe ID at
Behavioral Modeling Chapter 8.
1 CMPT 275 Phase: Design. Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces Data Persistance.
Object-Oriented Design Notation CS 123/CS 231. References zMain Reference: UML Distilled, by Martin Fowler ÕChapters 3, 4, 6, and 8 zSupplementary References:
Final Notes on the UML CS 123/231. UML Diagramming Techniques zClass Diagrams zUse Case Diagrams zInteraction Diagrams Õ Sequence diagrams ÕCollaboration.
West Virginia University Slide 1 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  Please revise the solution.
Software Design CS 123/CS 231. What is Design? zDesign is the activity of specifying a solution to a problem zContrast this against other software engineering.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
Phase 6 Start: Saturday14 April End: Saturday 21 April
1 Class Relationships in C++ CS 123/CS Class Diagram Notation Revisited zMultiplicity zAssociation and Navigability zComposition zAggregation.
12/24/2015B.Ramamurthy1 Analysis and Design with UML: Discovering Classes Bina Ramamurthy.
1 LAB What is Collaboration diagram? 4 Collaboration diagrams illustrate the interaction between the objects, using static spatial structure. 4.
OOP Review CS 124.
Chapters 10, 11 SSD (Revision) SD DCD Exam Object-Oriented Design.
Interaction Diagrams CS 124. Object collaboration A use case carried out involves objects and interaction or collaboration between these objects Method.
IT 240 Programming Paradigms MS Information Technology Offshore Program Ateneo de Davao Session 3.
Class Diagrams Software Design and Development. Classes in a Class Diagram zClass name onlyExample zWith DetailsExample Class Name attributes methods.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Use Case Diagram Example
Class Relationships in C++
Sequence Diagrams Mimi Opkins CECS 493 Fall2016
SEMCOM COLLEGE LIBRARY INFORMATION SYSTEM
Start at 17th March 2012 end at 31th March 2012
Software Design AITI GP John Paul Vergara.
SNSCT_CSE_PROGRAMMING PARADIGM_CS206
Sequence Diagrams.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4th edition, Prentice Hall, Hans Van Vliet, Software Engineering:
Interaction diagrams.
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Other UML Diagramming Techniques
Sequence Diagrams.
Chapter 4 Sequence Diagrams
Presentation transcript:

Use Cases and Object Interaction CS 123/CS 231

Depicting System Behavior zFirst, identify the use cases ÕUse case: typical interaction between a user and the system zUse Case Diagram ÕDepicts all use cases for a system zInteraction Diagram ÕDepicts a single use case as a collection of interacting objects

Example: Use Case Diagram Facilitate Checkout Facilitate Return Search for Book LIBRARY SYSTEM Borrower Librarian

Use Case Diagram Notation zStick Figures – Actors ÕCould be a human user or a subsystem zEllipses - Use Cases zLinks - between actors and use cases zLinks between use cases Õ >: to depict inclusion of a use case Õ >: to depict variations of a general use case

Example: > Facilitate Checkout Facilitate Return Librarian Log-in > Note: UML v.1.3 uses > instead of >

Example: > Search for Book query Borrower By Author By Subject > Note: query is called an extension point

Describing a Use Case zNarrative ÕLibrary example (Facilitate Checkout): Given a borrower’s ID Card and the book to be borrowed, the librarian enters the borrower’s ID number and the book’s catalogue number. If the borrower is allowed to check out the book, the system displays that the book has been recorded as borrowed zOr, an Interaction Diagram

Example: Interaction Diagram Checkout Screen :Borrower :Book 1: checkIfDelinquent() 3: borrowBook() 2: checkIfAvailable() 4: setBorrower()

Interaction (Collaboration) Diagram Notation zRectangles: Classes/Objects zArrows: Messages/Method Calls zLabels on Arrows Õsequence number (whole numbers or X.X.X notation) Õmethod name (the message passed) Õmore details, if helpful and necessary (iterators, conditions, parameters, types, return types)

Methods zInteraction Diagrams suggest/imply methods for classes ÕHas consequences on detailed class diagram zThe label(s) of an arrow should be a method of the class the arrow points to zLibrary System ÕBorrower class should have at least two methods (checkIfDelinquent and borrowBook)

Including Conditions and Types Checkout Screen r:Borrower b:Book 1: delinq = checkIfDelinquent():boolean 3:[!delinq & avail] borrowBook(Book b) 2: avail = checkIfAvailable():boolean

Creating an Object znew means a constructor is being called ÕImplies object creation :Customer :CustomerList 1: addCustomer(custdetails) :Encoder 2: new Note: this means the addCustomer method will contain code that creates a Customer object

Iteration z* is an iterator Õmeans the method is called repeatedly :Branch :Store 1: printSalesSummary() :Manager 2: * getTotalSales() Note: Store needs data from all branches to produce a summary

Summary zProvide a Use Case Diagram to depict the use cases of a system zFor each use case, describe and provide an Interaction Diagram ÕDepict use case as a collection of interacting objects zOther diagramming techniques that aid in building a dynamic model: ÕState diagram: describes object state changes ÕActivity diagram: describes method behavior