Use Case Analysis Chapter 5.

Slides:



Advertisements
Similar presentations
Ver 1,12/09/2012Kode :CIA-230 Anal-Perc.SistemFASILKOM PERTEMUAN-4 Chapter 4. Use Case Analysis.
Advertisements

© Copyright 2011 John Wiley & Sons, Inc.
Scenarios: The missing link or – “ Some Stuff About Use Cases and Testing”
Lecture 9 Descriptors, Events & Event Tables INFO1409 Systems Analysis & Design Module HND Year /9.
Object-Oriented Analysis and Design
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 7 Descriptors Events Events Tables.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
Lecture 8 – USE CASE ANALYSIS
Systems Analysis and Design in a Changing World, Fourth Edition
Process Modeling Chapter 6. Key Definitions A process model is a formal way of representing how a business operates Data flow diagramming shows business.
Chapter 7 Using Data Flow Diagrams
Use Case Analysis Chapter 6.
© 2005 Prentice Hall3-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Process.
Requirements
Chapter 9 Using Data Flow Diagrams
Use Cases.
© Copyright 2011 John Wiley & Sons, Inc.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 7: The Object-Oriented Approach to Requirements
USE Case Model.
Modeling System Requirements:Events and Things
Use Case Diagrams – Functional Models Chapter 5. Objectives Understand the rules and style guidelines for activity diagrams. Understand the rules and.
Systems Analysis and Design in a Changing World, 6th Edition
Copyright © 2012 Pearson Education, Inc. Publishing as Pearson Addison-Wesley C H A P T E R 6 Value- Returning Functions and Modules.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Systems Analysis and Design in a Changing World, 6th Edition
U SE C ASE A NALYSIS Chapter K EY I DEAS Use cases are a text-based method of describing and documenting complex processes Use cases add detail.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
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.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Systems Analysis and Design in a Changing World, 6th Edition
1 Modeling System Requirements with Use Cases. 2 Why Do We Need Use Cases? Primary challenge in a system design process –ability to elicit correct and.
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
IFS310: Module 7 Business Requirements Statement Interpersonal Skills and Communications.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 5 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH CHAPTER.
Lecture 6: Test-based Use case & Process Modeling December 7, 2014.
Systems Analysis and Design in a Changing World, Fourth Edition
Lecture 6: Chapter 4:Test-based Use case Process Modeling Dr. Taysir Hassan Abdel Hamid November 17, 2013.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Program Design. Simple Program Design, Fourth Edition Chapter 1 2 Objectives In this chapter you will be able to: Describe the steps in the program development.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
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.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Use Case Analysis Chapter 6.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 4: Business Process and Functional Modeling, continued
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 5 – System Modeling
Recall The Team Skills Analyzing the Problem (with 5 steps)
Architecture Concept Documents
Systems Analysis and Design Third Edition
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
SYSTEMS ANALYSIS Chapter-2.
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design in a Changing World, 6th Edition
System analysis and design
Lesson Objectives Aims Key Words
Topics Introduction to Value-returning Functions: Generating Random Numbers Writing Your Own Value-Returning Functions The math Module Storing Functions.
Chapter 11 Describing Process Specifications and Structured Decisions
Engineering Quality Software
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Use Case Modeling Part of the unified modeling language (U M L)
Chapter 4 System Modeling.
M3 D2 Effectively lead a team & evaluate your leadership abilities
Presentation transcript:

Use Case Analysis Chapter 5

Key Ideas Use cases are a text-based method of describing and documenting complex processes Use cases add detail to the requirements outlined in the requirement definition Systems analysts work with users to develop use cases Systems analysts develop process and data models later based on the use cases

Use Cases

Roles of Use Cases A use case is a set of activities that produce some output result Describes how the system reacts to an event that triggers the system Trigger -- event that causes the use case to be executed Event-driven modeling – everything in the system is a response to some triggering event

Role of Use Cases All possible responses to the event are documented Use cases are helpful when the situation is complicated

Elements of a Use Case Basic information Major inputs and outputs Name, number and brief description Trigger – event that causes the use case to being External trigger – some from outside the system Temporal triggers – time-based occurrences Viewpoint of the use cases should be consistent Major inputs and outputs Sources and destinations Goal is to be all inclusive Details Steps performed and the data inputs and outputs

Sample Use Case

Building Use Cases

Process of Developing Use Cases Identify the major use cases Identify the major steps within each use case Identify elements within steps Confirm the use case Cycle through the above steps iteratively

Step 1: Identify the major use cases Activities Typical Questions Asked Start a use case form for each use case If more than nine, group into packages Ask who, what, and where about the tasks and their inputs and outputs: What are the major tasks performed? What triggers this task? What tells you to perform this task? What information/forms/reports do you need to perform this task? Who gives you these information/forms/reports? What information/forms/reports does this produce and where do they go?

Step 2: Identify the major steps within each use case Activities Typical Questions Asked For each use case, fill in the major steps needed to process the inputs and produce the outputs Ask how about each use case: How do you produce this report? How do you change the information on the report? How do you process forms? What tools do you use to do this step (e.g., on paper, by email, by phone)?

Step 3: Identify elements within steps Activities Typical Questions Asked For each step, identify its triggers and its inputs and outputs Ask how about each step How does the person know when to perform this step? What forms/reports/data does this step produce? What forms/reports/data does this step need? What happens when this form/report/data is not available?

Step 4: Confirm the use case Activities Typical Questions Asked For each use case, validate that it is correct and complete Ask the user to execute the process using the written steps in the use case – that is, have the user role-play the use case

Summary Use cases contain all the information needed for process modeling, but are easier for users to comprehend Use cases are created in an iterative cycle of steps until they are considered accurate and complete