1 Project Management Office Lunch & Learn Use Case.

Slides:



Advertisements
Similar presentations
Use-Cases.
Advertisements

CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Scenarios: The missing link or – “ Some Stuff About Use Cases and Testing”
Information System Engineering
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Lecture 8 – USE CASE ANALYSIS
Rational Unified Process
Documenting Requirements using Use Case Diagrams
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Modeling System Requirements with Use Cases
Use Cases.
This work is licensed under a Creative Commons Attribution 3.0 Unported LicenseCreative Commons Attribution 3.0 Unported License (CC-BY). Project Management.
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
USE Case Model.
Use Cases Why use ‘em? How do they work? UC diagrams Using them later in the software development cycle.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
Object-Oriented Analysis - Instructor Notes
Chapter 3 Use Cases.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Requirements Analysis
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Systems Analysis and Design in a Changing World, 6th Edition
Use Cases Ivar Jacobson - guru at Rational Corp., defined UML.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
MOHANA PRIYA TEST SCENARIO  Test scenario represent a powerful tool for test design and are a single event or a sequence of events that happen.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
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.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Object Oriented Methodologies
Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
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.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Information Systems Analysis and Management Modeling Sys. Requirements with Use Cases Arnie Lund, Jeffrey Kim May 5, 2009 INFO380.
Project Management Cross lifecycle Activity
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Understanding Requirements
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Application Analysis. Application Interaction Model The purpose of analysis is to understand the problem so.
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.
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.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
General Cost Center Planning
Chapter 4: Business Process and Functional Modeling, continued
Scope Planning.
Systems Analysis and Design in a Changing World, 6th Edition
Use Cases Discuss the what and how of use cases: Basics Benefits
Recall The Team Skills Analyzing the Problem (with 5 steps)
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
Dr. Samer Odeh Hanna (PhD)
Systems Analysis and Design in a Changing World, 6th Edition
Object Oriented Analysis and Design
Use Cases 1.
Using Use Case Diagrams
Use Case Document Example
Requirements Very High level specification of what system should do
Engineering Quality Software
Object-Oriented Software Engineering
Use Case Modeling Part of the unified modeling language (U M L)
CS 425 Software Engineering
Presentation transcript:

1 Project Management Office Lunch & Learn Use Case

2 Agenda Definition Benefits UCIT Methodology & Use Case Steps to develop use cases Use Case Body Parts References Questions

3 What is a use case? Describe goal-oriented set of interactions between the actor and the software A technique used to identify, detail, and clarify software requirements Focus on WHAT, not HOW Define the scope/boundary of the software

4 Use Case Diagram – Membership Sales

5

6 Benefits Put requirements in business context Easy to understand by business & IT community Validate scope and requirements Serve as a basis as scheduling and estimating Manage complexity −Break software into manageable parts Re-useable deliverable −Test Cases −User Manual −Future enhancements

7 UCIT Methodology & Use Case

8 Steps to develop use case 1.Identify actor 2.Identify use case goals for each actor 3.Identify re-use opportunity

9 Example – Membership Sales

10 Steps to develop use case 4.Create Use Case Index 5.Validate against requirements 6.Determine execution approach 7.Develop high level use case 8.Create detail use case 9.Walkthrough & Revise 10.Package into final document

11 Body Parts Summary Scenarios & Steps Exceptions

12 Body Parts - Summary Use Case Identifier −Unique identifier assigned to use case −Example MS-001, MS Goal/Name −Describe the BUSINESS goal that the use case is intended to achieve −Use active verb to describe the performing action on the goal −Example: Register in an event, Issue an ID Card, Renew a Membership Actor −Someone or something outside the system that acts on the system −Primary or secondary actors −Person/Role, System, or Time

13 Body Parts - Scope Pre & Post Conditions −Pre Conditions – set of criteria must be satisfied before the use can be initiated −Post Conditions – describes the states of the software when the use case ends Triggers −Event that causes the use case to be initiated −External, Internal, or Temporal Temporal - Send Payroll Deduction to PeopleSoft Internal – Apply Client Restriction Automatically Business vs. System Use case

14 Example – Renew a Membership

15 Body Parts - Scenario Main Scenario −Consists of steps required to achieve the business goals −Happy Day Scenario – most likely case Alternate Paths −Other possible scenarios −Branch from main scenario when the situation differs

16 Body Parts - Exceptions Steps taken to deal with failure System or human cause −Access to ID Core Service failed −Payment failed to go through Moneris

17 Example – Sell a Membership

18 Example – Sell a Membership

19 More Information Books −Writing Effective Use Cases −Patterns for Use Cases Websites − −en.wikipedia.org/use_case

20 Questions