Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake1 Use Case Diagrams What are they? What do they look like?

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

Karolina Muszyńska Based on:
CT1404 Lecture 2 Requirement Engineering and Use Cases 1.
Systems Analysis and Design in a Changing World, Fourth Edition
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.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
1 CS 501 Spring 2005 CS 501: Software Engineering Lecture 8 Requirements II.
Topics Creating DFD Physical and logical DFD Event driven modeling
Requirements Analysis 2. 1 Req. Capture b502.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Requirements.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
© Pearson Education Limited, Chapter 6 Fact-finding Transparencies.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Systems Analysis I Data Flow Diagrams
Data Flow Diagrams "Business process flow" not a Flow Chart.
Use Case Diagram (UCD) Yong Choi BPA.
IS0514 Lecture Week 3 Use Case Modelling.
Chapter 7: The Object-Oriented Approach to Requirements
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
USE Case Model.
Data Flow Diagrams (DFDs)
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Requirements – Scenarios and Use Cases
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Fact-finding Transparencies 1. ©Pearson Education 2009 Objectives When fact-finding techniques are used in the database system development lifecycle.
SYSTEMS ANALYSIS AND DESIGN TOOLS DATA FLOW DIAGRAMS.
Originated by K.Ingram, J.Westlake.Edited by N.A.Shulver Use Case Scripts What is a Use Case Script? The text to describe a particular Use Case interaction.
1 SYS366 Business Use Case Descriptions. 2 Today Identifying Business Use Cases Documenting Business Use Cases.
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.
1 Structuring Systems Requirements Use Case Description and Diagrams.
University of Sunderland ISIC 1 Data Flow Diagrams - Part 2 Hierarchical DFDs.
Systems Analysis and Design in a Changing World, 6th Edition
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Drawing System Sequence Diagrams
Use Case Diagrams.
INFORMATION X INFO425: Systems Design Systems Design Project Deliverable 2.
Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake1 Use Case Scripts The text to describe a particular Use Case.
Systems Analysis and Design in a Changing World, Fourth Edition
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
1 SYS366 Business Use Cases. 2 Today Business Use Cases Identifying Stakeholders & Actors.
Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake1 Special Relationships between Use Cases Normally it is not.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 37 C System Process Modeling DATA Flow Diagrams.
Business Processes A business process describes a set of activities that are necessary to complete a response to a stimulus applied to an organization.
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Introduction to Rational Rose 2000 Create Use Case Model.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Use Cases Discuss the what and how of use cases: Basics Examples Benefits Parts Stages Guidelines.
Is 581 assist Inspiring Minds/is581assistdotcom FOR MORE CLASSES VISIT
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Advanced Higher Computing Science
Use Case Analysis Chapter 6.
Welcome to M301 P2 Software Systems & their Development
Chapter 5 System modeling
CMPE 280 Web UI Design and Development August 29 Class Meeting
Use Cases Discuss the what and how of use cases: Basics Benefits
Chapter 5 – System Modeling
Use Case Model.
The Next Stage in Analysis: Systems Use Case Diagrams
Week 10: Object Modeling (1)Use Case Model
System Process Modeling
Systems Analysis and Design
Requirements: Use Case Models and Narratives
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
What is a Relationship Map?
IS0514 Lecture Week 3 Use Case Modelling.
Presentation transcript:

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake1 Use Case Diagrams What are they? What do they look like? How to develop a Use Case Diagram in Visio Tips and techniques Assignment context

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake2 What are they? The 1 st stage of our OOM lifecycle –One of the many techniques within UML –Used at the Feasibility and early Analysis stages of a project - to specify WHAT the system should do (not How - this comes later) Supported by many software CASE tools Encourage the user to get involved –Provide a catalyst for discussion with users –Easy to do (much easier than data flow diagrams) –Show Processes – users understand this

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake3 What do they look like? Report Sales Review Individual’s Sales Review Regional Sales Salesperson Regional Sales Manager Accounting system Inventory system Watson’s SalesWeb System (From Understanding UML, Harmon & Watson)

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake4 What does the diagram show? Describe the functions-of / processes-within a system - the “Cases” Identify the boundary of a system Identify who and/or what uses the system - the Actors “are used to describe the outwardly visible requirements of a system” Schneider & Winters (2001) “A use case achieves a discrete goal for the user” Fowler with Scott (1997)

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake5 Use Cases - approach Iteration - initially take a broad, top level view, then later add lower level detail (called the Top Down approach) –as your investigation reveals more facts –as you concentrate on specific areas Refinement - enable the Use Cases to evolve by correcting/improving previous iterations Document however little you know, then add to it.

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake6 Example of the Top-down approach Using Visio – done in the tutorial –Program files Office –Visio »Software Development diagrams »Click on UML diagram »Click on Activity Diagrams »Select Use Case Diagram

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake7 Use Cases - format Diagrams are easy to assimilate –Processes in ellipses –Actors as stick-people –Interactions as lines Text descriptions provide detail –Use Case Scripts discussed next week

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake8 Actors Include users and other systems an actor on a diagram = a role –1 person/system may have 1 or more roles (i.e. in different interactions) –1 role may comprise 1 or more people by convention people are on left, systems on right

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake9 Use Cases (Processes) Functions (initially the major ones only) within the system So the name must be a verb NOT departments in the organisation Some processes may be time-triggered system responses and have no actor involved

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake10 Interactions Where some exchange occurs between an actor and a process may be in either direction the detail of the interaction need not be known at this stage can be labelled/named

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake11 Finding the Actors and Use Cases Use appropriate fact-finding techniques (interviewing, questionnaires, observation, document inspection, …) Identify all users, then the processes they initiate or participate in. Identify all external events to which the system must respond, then relate to actors and processes.

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake12 PSPStock ControllerLogistics Provider Tuneswarehouse Sales Order Processing Stock Control Outbound logistics Inbound logistics Customer Example – top level These lines between Use cases are the subject Of week 2

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake13 Example - 2 nd level Sales Order Processing Create Order Update Order Delete Order Find Order CustomerStock Controller Uses Customer

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake14 Summary Questions You have already been given the answers to these…… 1.What is the purpose of a Use Case diagram? 2.Who needs to be involved with use case diagrams? 3.How many levels of diagram can there be? 4.What is the maximum number of use cases on any diagram? 5.What is a Use Case? an Actor? an Interaction? 6.What does the System Boundary tell us? 7.Why bother having a broad, top-level diagram if we are going to add more detail to lower levels?

Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake15 Use Case Tutorial Task 2 Using Visio draw a top level Use Case Diagram, then all the 2 nd level Use Case Diagrams for a Hire Shop renting out building equipment. See HSS website for understanding of what can be hired out at one of their shopsHSS Show your work to the tutor