UML – Unified Modeling Language Use-Case Diagrams.

Slides:



Advertisements
Similar presentations
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Advertisements

Use Case Model. C-S 5462 Use case model describes what the user expects the system to do –functional requirements may describe only the functionalities.
Systems development life cycle & development methodologies
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Chapter Extension 19 Alternative Development Techniques © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Uml and Use Cases CS 414, Software Engineering I Mark Ardis Rose-Hulman Institute January 9, 2003.
Use Cases & Requirements Analysis By: Mostafa Elbarbary.
Documenting Requirements using Use Case Diagrams
1 Lecture 1: Processes, Requirements, and Use Cases.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Use Case Modeling.
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Unified Modeling Language
Object-Oriented Analysis and Design
CMPT 275 Software Engineering
Chapter 7: The Object-Oriented Approach to Requirements
USE Case Model.
RUP Requirements RUP Artifacts and Deliverables
Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
CS499 Use Cases References From Alistair Cockburn Writing Effective Use Cases (Book) - Use Case.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Rational Unified Process (Part 1) CS3300 Fall 2015.
Understanding User Requirements. Documenting Use Cases 2 At this stage of the exploration, the participants should be thinking of essential use cases.
Unified Modeling Language, Version 2.0
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Key Takeaway Points A use case is a business process; it begins with an actor, ends with the actor, and accomplishes a business task for the actor. Use.
1 © 2005 course technology1 1 1 University Of Palestine Chapter 5 (Cont.) Scoping the IT Project with System Use Cases.
Definitions Priority terms: Use case User story Scenario Public Health event Participant / Actor Public Health report Public Health Reporting Trigger Data.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
UML-1 8. Capturing Requirements and Use Case Model.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
IS3320 Developing and Using Management Information Systems Lecture 9: Use Cases and Scenarios Rob Gleasure
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
UOFS Information System Version 0.9 Yaodong Bi Copyright 2009, Yaodong Bi.
Week IV in SOS  Tuesday Project Time -- 4:15pm-5pm URL for project(s) due to Judy by Friday 5pm  Friday Paper  OOAD Handouts thru last Thursday (see.
Systems Analysis and Design in a Changing World, Fourth Edition
A Well Designed Web Application The Benefits of Object Oriented Analysis and Design Simone Becker
1 Unified Modeling Language, Version 2.0 Chapter 2.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
UML (Unified Modeling Language)
Beyond Scenarios: Generating State Models from Use Cases An approach for the synthesis of State transition graphs from Use Cases Supporting Use Cases Based.
Basic Characteristics of Object-Oriented Systems
By Mashael AlDayel Introduction to UML. What is UML? UML (Unified Modeling Language) is a graphical language that is suit-able to express software or.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
Use Case Diagrams A Detailed Description. Use Case Diagrams Use case diagrams describe relationships between users and use cases A use case is a (usually.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Storyboarding and Game Design SBG, MBG620 Full Sail University
Use Case Model.
SafeHome Product.
Concepts, Specifications, and Diagrams
Unified Modeling Language
Informatics 43 Discussion, April 8, 2016
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Engineering Quality Software
Use Case Modeling Part of the unified modeling language (U M L)
Presentation transcript:

UML – Unified Modeling Language Use-Case Diagrams

What is UML? UML  unified modeling language Mainly used for development of OO Used in conjunction with UP  Unified process

What is UP? Inception Elaboration Construction Transition Production

What is a use-case diagram? Depicts the software or system from the end user’s point of view Steps  Define the actors  Define the goals  Determine who is primary and secondary actors

Use-case (cont) Basic use-case presents a high-level story that describes the interaction between the actor and the system

Use-Case Scenarios

Use-case template Use-case Primary actor Goal in context Pre-conditions Trigger Scenario Exceptions Priority When available Frequency of use Channel to actor Secondary actors Channels to secondary actors Open issues

Users use-case example Use-case: UsersUseColiseumManagementSystem Primary actor(s):Coliseum Administration Staff, Web-users, Coaches, Students Goal in context: To provide users the correct interfaces so that they may use the system Pre-conditions: Users are not logged in and users are in the database Trigger: User decides to use the system Scenario: 1) users observe the interface; 2) the user enteres usrn/pwd 3) the user selects submit 4) observes system to indicate he/she is logged in Exceptions: 1) user is already logged in; user would just use the system 2) usrn/pwd pair is not recognized and user would try to login again; if user cannot login then it is reported to the helpdesk for a pwd reset 3) usrn/pwd pair is not in the system; Helpdesk would add user to the system 4) user is logged in the next interface is shown 5)user would make selection from possible dashboard options

Use-case example (cont) Priority: essential, must be implemented When available: first increment Frequency of use: many times per day Channel to actor: intranet/internet interface through web browser Secondary actors: Helpdesk Channels to secondary actors: Helpdesk  telephone, live web chat and Open issues: 1) should there be a way to log into the system without usrn/pwd 2) should there be any other messages given to the user 3) how many attempts does the user get to login 4) is there a way to logout 5) do all users have to login

Use-case diagram

Requirements Definitions

Purpose Target Audience Template