Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams.

Slides:



Advertisements
Similar presentations
Use Case Diagrams Damian Gordon.
Advertisements

CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
Use Case & Use Case Diagram
Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
CS3773 Software Engineering Lecture 03 UML Use Cases.
2008/03/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
Object-Oriented Analysis and Design
Chapter 15: System Modeling with UML
Use-case Modeling.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
© Copyright Eliyahu Brutman Programming Techniques Course.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
SE 555 Software Requirements & Specification Requirements Analysis.
Unified Modeling Language
IS0514 Lecture Week 3 Use Case Modelling.
USE Case Model.
CMPT 275 Software Engineering
6. Basic Behavioral Modeling Interactions. Sung Kim CS6359 Chapter 15Slide 2 Overview Interactions – Roles – Links – Messages – Actions – Sequences Modeling.
2005/05/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
1.  Modeling the context of a system  Modeling the requirements of a system 2.
Software Engineering Design & Modelling
Interaction Modeling. Introduction (1) Third leg of the modeling tripod. It describes interaction within a system. The class model describes the objects.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Chapter 5 Models and UML Notation for The Object-Oriented Approach.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
1 Structuring Systems Requirements Use Case Description and Diagrams.
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
Business Analysis with For PG MDI, Gurgaon Kamna Malik, Ph.D.
Analysis Modeling CpSc 372: Introduction to Software Engineering
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Use Cases and Use Case Diagrams Reporter: 陳雅萍. Outline Use cases, actors Organizing use cases Modeling the behavior of an element Use case diagrams Common.
Use Case Diagram Lecture # 1. Use Case Diagram Use-cases are descriptions of the functionality of a system from a user perspective.  Depict the behaviour.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
UC Diagram & Scenario RKPL C & D. Using Use Case Diagram Use case diagrams are used to visualize, specify, construct, and document the (intended) behavior.
Lawrence ChungCS6359.OT1: Module 141 Module 14: Use Cases & Use Case Diagrams.
Using Use Case Diagrams
Chapter 4: Business Process and Functional Modeling, continued
Use Case Modeling - II Lecture # 27.
Unified Modeling Language
Dynamic Modeling of Banking System Case Study - II
UML Use Case Diagrams.
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Object Oriented Analysis and Design
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
IS0514 Lecture Week 3 Use Case Modelling.
Software Design Lecture : 15.
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Use Case Model Use case diagram – Part 2.
Using Use Case Diagrams
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Use Case Modeling Part of the unified modeling language (U M L)
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Presentation transcript:

Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams

Sung KimCS6359 Chapter 16 Slide 2 Overview Use cases –Include –Extend Actors Modeling behavior of an element. Realizing use cases with collaborations. Modeling the context of a system. Modeling the requirements of a system. Testing from use cases.

Sung KimCS6359 Chapter 16 Slide 3 Use Case Definition …User Guide –Description of a set of sequences of actions that a system performs to yield/hasil an observable result of value to an actor. Object-oriented Software Engineering; Jacobson, ‘92 –Narrative document that describes the sequences of events of an actor using a system to complete a process.

Sung KimCS6359 Chapter 16 Slide 4 Use Cases Defines “what” without specifying “how”! Specify desired behavior. Promotes communication among: –End users –Domain experts –Architects –Developers –Information Modelers

Sung KimCS6359 Chapter 16 Slide 5 Use Cases (cont’d) Represents a set of functional requirements on a system. Achieve/mencapai a tangible/ nyata amount/ jumlah of work. Provide a starting point for test cases. Process loan actor use case name LoanOfficer

Sung KimCS6359 Chapter 16 Slide 6 Actor Coherent/saling berlengketan set of roles that users assume when interacting with a system. Human or automated systems. Represents an individual interacting with the system in a specific way. Live outside the system. Connected to use cases through associations. automated system >

Sung KimCS6359 Chapter 16 Slide 7 Use Cases and Flow/aliran of Events Typical Course of Events Usually described in informal text or formal structured text. Visualized in interaction diagrams; commonly system sequence diagram. Exceptional flows or variations depicted separately. Identifies when the use case begins and ends.

Sung KimCS6359 Chapter 16 Slide 8 Use Cases and Scenarios Scenarios describe a particular/ keterangan sequence through a use case. Real or prototypical values are used. Each sequence defines a set of system operations. System operation: –System level function. –A single interaction between an actor and the system.

Sung KimCS6359 Chapter 16 Slide 9 Use Cases and Collaborations Collaboration—a society of classes and other elements that work together to implement the behavior of a use case. Realization of a use case. Place order Order management use case collaborationrealization

Sung KimCS6359 Chapter 16 Slide 10 Organizing Use Cases Use packages. Factor common behavior through/dalam relationships. –Generalization –Extend –Include

Sung KimCS6359 Chapter 16 Slide 11 Generalized Use Case Child inherits behavior and meaning from parent. Child may be substituted any place for a parent. Rendered/sama same as class generalization.

Sung KimCS6359 Chapter 16 Slide 12 Use Case Inclusion Base use case explicitly incorporates/gabung the behavior of another use case. The included use case cannot stand alone. Example of delegation. Rendered as a stereotyped dependency.

Sung KimCS6359 Chapter 16 Slide 13 Extending a Use Case Base use case incorporates the behavior of another use case. The extending use case indicates where the extended behavior occurs in the base use case. Base use case only extended through extension points. Used to model optional behavior. Rendered as a stereotyped dependency.

Sung KimCS6359 Chapter 16 Slide 14 Use Case Organization Example Track order generalization Validate user Retinal scan Check password Place rush order Place order Extension points: set priority extension inclusion extension point > (set priority) >

Sung KimCS6359 Chapter 16 Slide 15 Example (cont’d) Track Order Main flow of control : Obtain and verify the order number. Include (Validate user). For each part in the order, query its status, then report back to the user. Place Order Main flow of control: Include (Validate user). Collect the user’s order items. (set priority). Submit the order for processing.

Sung KimCS6359 Chapter 16 Slide 16 Modeling the Behavior of an Element Element could represent –The system as a whole/ keseluruhan. –A subsystem. –An individual class. Important reasons: –Allows domain experts to specify external view to sufficient/ cukup details for developers to continue. –Provides a means for developers to approach mendekatnya and understand an element. –Provides a basis for testing.

Sung KimCS6359 Chapter 16 Slide 17 Modeling Behavior (steps) Identify actors that interact with the element. Organize actors by generalized and more specialized roles. Consider/ mempertimbangkan the primary ways actors interact with the element. Consider the exceptional ways actors interact with an element. Organize the behaviors as use cases.

Sung KimCS6359 Chapter 16 Slide 18 Hints & Tips on Use Cases Well structured use case: –Names a single, identifiable and atomic behavior. –Factors common behavior through inclusion. –Factors variants by pushing behavior through extension. –Describes the flow of events such/supaya that a non-technical person can follow. –Clarified by a minimal set of scenarios that specify the normal and variant semantics/yg berhub..

Sung KimCS6359 Chapter 16 Slide 19 Hints & Tips on Use Cases (cont’d) Depicting a use case: –Show only the use cases that are important to understand the behavior in a particular/kusus context. –Show only the actors related to those use cases.

Sung KimCS6359 Chapter 16 Slide 20 Use Case Diagrams Use case diagram—diagram that shows a set of use cases and actors and their relationships. Used to visualize the behavior of a system. Allows users to comprehend/ mengerti the interactions with the system.

Sung KimCS6359 Chapter 16 Slide 21 Use Case Diagram (an example) system boundary Place phone call extension actor «extend» Use scheduler Receive phone call Receive additional call Place conference call «extend» Cellular Network use case association Cellular Telephone

Sung KimCS6359 Chapter 16 Slide 22 Use Case Diagram Contents Use cases Actors Relationships –Dependencies –Generalizations –Associations Notes and constraints

Sung KimCS6359 Chapter 16 Slide 23 Common Uses Model the context of a system. –Identifying the system border. –Defining what is inside the system. –Defining what is outside the system. Model the requirements of a system. –What the system should do. –Independent of how the system will do it!

Sung KimCS6359 Chapter 16 Slide 24 Modeling the System Context Identify the actors that surround the system. –Which groups need help from the system. –Which groups are needed to execute system functions. –Which groups interact with external hardware. –Which groups perform secondary functions. Organize actors using generalization if appropriate/ sesuai. Use stereotypes for actors to aid/ bantu understanding. Populate a use case diagram with actors and associate with system use cases.

Sung KimCS6359 Chapter 16 Slide 25 Context Example Perform card transaction Customer Credit Card Validation System Process customer bill Reconcile transactions Manage customer account Corporate Customer Retail Institution

Slide 26 Modeling System Requirements Establish the system context. Consider/mempertimbangkan the behavior that each actor expects/ menyangka from the system. Name common/ biasa behaviors as use cases. Factor common behavior; extensions, inclusions, and generalizations. Model the actors, use cases, and relationships into a use case diagram. Adorn/ menghiasi with notes for non- functional requirements.

Sung KimCS6359 Chapter 16 Slide 27 Modeling System Test Cases For each use case, identify its flow of events. Generate a test script for each flow. –Obtain/ mendapatkan initial state from preconditions/mempersiapkan. –Test success against post conditions. Build necessary/ kebutuhan test drivers to simulate scenarios using test scripts. Use tools to regression/ kemunduran test using the tests.

Sung KimCS6359 Chapter 16 Slide 28 Hints & Tips on Use Case Diagrams Well-structured use case diagrams: –Focused on communicating a single aspect of a system’s static use case view. –Contains only actors and use cases essential/yg perlu to that aspect. –Should contain sufficient detail to inform a reader of important system semantics /yg berhub..

Sung KimCS6359 Chapter 16 Slide 29 Hints & Tips on Use Case Diagrams (cont’d) Depicting a use case diagram: –Choose a name that communicates purpose. –Minimize crossing of lines. –Physically co-locate semantically related elements. –Use notes and colors for necessary/perlu emphasis. –Only show what is more or less useful!

Sung KimCS6359 Chapter 16 Slide 30 Summary Use cases & Actors Typical course of events. Scenarios Collaborations. Organizing use cases. Modeling behavior. Use case diagrams –Definition –Example –Contents –Common uses Modeling system context Modeling system requirements Modeling system test cases