Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” www.usecases.org - may be of use to you in the future “blackbox”

Slides:



Advertisements
Similar presentations
Writing Good Use Cases - Instructor Notes
Advertisements

Project Analysis Course ( ) Final Project Report Overview.
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Karolina Muszyńska Based on:
9/10/2004Use Case Workshop 1 CSC480 Software Engineering Workshop 1 Requirements Modeling.
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
Information System Engineering
Waterfall Development Process
September Ron McFadyen1 design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before.
January Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box.
Jan Ron McFadyen1 Consider a simple cash-only Process Sale scenario 1. Customer arrives at a POS checkout with goods and/or services to purchase.
Design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must.
Introduction To System Analysis and Design
Systems Analysis and Design in a Changing World, Fourth Edition
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” - may be of.
Use Cases & Requirements Analysis By: Mostafa Elbarbary.
Documenting Requirements using Use Case Diagrams
Copyright ©2004 Cezary Z Janikow 1 Use Cases n Within Requirements discipline/workflow n Verbal descriptions of important functional (behavioral, transactional,
Jan 8, Ron McFadyen1 Waterfall Spiral UP Case study UML Use Cases.
Jan R McFadyen1 Use Cases Widely used. Not just an OO technique. Diagramming defined in UML Each Use Case will meet one or more user goals;
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
חוזים – Contracts 1. Larman – Chapter 10 – SSDs 10.2 What are System Sequence Diagrams? (introduction) Use cases describe how external actors interact.
Chapter 7: The Object-Oriented Approach to Requirements
Software Engineering 2003 Jyrki Nummenmaa 1 USE CASES In this lecture: Use cases - What are use cases? - Why to use use cases? - How to write.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
SYS466: Analysis and Design Using OO Models
LECTURE 3 USE CASE DESCRIPTION. Use Cases grouped into system modules Note: Same actor interacts with different modules USE CASE DIAGRAM OF THE CUSTOMER.
Requirements Functional requirements  Use-cases
SOEN 6011 Software Engineering Processes Section SS Fall 2007 Dr Greg Butler
4 2009/10 Object Oriented Technology 1 Topic 4: The Object-Oriented Approach to Requirements Adopted from: Ch.7 The Object-Oriented Approach to Requirements.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: An Aside: The Quickest Tour through the UML that you will ever get.
Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
2. Inception 6. Use-Case Model: Writing Requirements in Context.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
1 Structuring Systems Requirements Use Case Description and Diagrams.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
Drawing System Sequence Diagrams
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
SYS466 Casual Use Case Specifications. Systems Use Case Diagrams and Specifications Based on the dialog metaphor Based on the dialog metaphor The process.
System sequence diagrams
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Phase 6 Start: Saturday14 April End: Saturday 21 April
Systems Analysis and Design in a Changing World, Fourth Edition
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.
1 What is the Software Life Cycle? The stages of developing a software application Requirements Analysis High-level Design Plan Low-level Design Implementation.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
UML - Development Process 1 Software Development Process Using UML.
Larman chapter 61 Use cases Larman chapter 6. 2 Fig. 6.1.
Use Case Model Use case description.
1 SYS366 Business Use Cases. 2 Today Business Use Cases Identifying Stakeholders & Actors.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
ACO 101: Use cases What do the users do?. When building a system You begin with the Use Case Analysis – When looking at the system as a whole, Use Case.
Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek.
Systems Analysis and Design in a Changing World, Fourth Edition
System sequence diagrams
UML Use Case Diagrams.
Start at 17th March 2012 end at 31th March 2012
Use Case Model Use case description.
UML: Unified Modeling Language
Software Design Lecture : 15.
Use Case Modeling.
Object-Oriented Software Engineering
Use cases Dr. X.
Presentation transcript:

Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” - may be of use to you in the future “blackbox” style is recommended - specify what the system must do, and not how it must do it. A project may begin with the definition of many “brief” or “casual” use case definitions. Later on, these can be become “fully dressed”

Use Cases Widely used. Not just an OO technique. Each Use Case will meet one or more user goals Collectively, Use Cases represent the functionality required by a system. Stories of using a system to meet goals

Use Cases Ch 6. Use Case example is very lengthy and fairly complete must read: pages 45-61, and sections 6.12, 6.13, 6.15 Ch 25 shows ways of managing Use Cases. Ch 25. The Use Case has been broken down into multiple Use Cases that are related via > and > must read: sections 25.1, 25.2, 25.3, 25.5 Ch 13. Contracts Ch 9. System Sequence Diagrams SSDs show the events that actors generate. The system is a black box and so the diagram emphasizes the events the system must respond to.

Use Cases a Use Case is initiated by an Actor Describes functional requirements from the user’s perspective illustrate actors & tasks forms: pictorial (defined in UML) textual not defined in UML recommended to leave UI details out and focus on the purpose of the use case focus on what the system does, not how it does it (black box)

Use Cases numerous textual forms brief, casual, fully dressed single- vs two-column form common format at Risks/dangers when using use cases: too much focus on functionality may lead to non- OO system

Actors An actor is anyone or thing that interacts with the system. These people or things are at the boundaries of the system. Suppose our system interacts with a billing system: Instructor Student Assign duties Assign grades Register for courses Browse enrollments Chair Billing Its common to place non-human roles on the RHS

Use Case Diagram

An Order-Processing System Place order Get Order status Send catalog Cancel order Return product Deliver product Send us product Calculate postage Customer Customer Rep Shipping company Supplier Clerk