Functional Requirements – Use Cases (Chapters 14, 21) Sriram Mohan 1.

Slides:



Advertisements
Similar presentations
State Patrol Ticket System
Advertisements

Use-Cases.
Use Case Diagrams Damian Gordon.
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
Use Case & Use Case Diagram
Scenarios: The missing link or – “ Some Stuff About Use Cases and Testing”
Information System Engineering
1 Use Cases 2 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 20, 2004.
1 Use Cases 1 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 17, 2004.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Use-case Modeling.
Systems Analysis and Design in a Changing World, Fourth Edition
Use Case modelling How to go from a diagram to a further definition.
1 Team Skill 4 - Team Skill 5 - Scope Refining the Systems Definition (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Use Case Modeling Written by: Zvika Gutterman Adam Carmi.
WEEK 4 Material Lecture 4a (Wed.). Use Cases/Actors o What is a use case ? l A sequence of actions performed by a system that yields an observable result.
Written by: Zvika Gutterman Adam Carmi
Use Case Modelling.
Functional Requirements – Use Cases Sriram Mohan/Steve Chenoweth (Chapters 14, 21 – Requirements Text) 1.
1 Team Skill 3 - Defining the System (Chapters of the requirements text) CSSE 371 Software Requirements and Specification Don Bagert, Rose-Hulman.
Chapter 6 Functional Modeling
Rose-Hulman Institute of Technology Sriram Mohan 18.September.2008 CSSE 497 Requirements Review.
Functional Requirements – Use Cases Steve Chenoweth & Chandan Rupakheti (Chapters 14, 21 – Requirements Text)  Quiz question 9 relates to this, when you’ve.
Functional Modeling Chapter 6.
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.
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.
System Sequence Diagrams
RUP Requirements RUP Artifacts and Deliverables
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Interaction Modeling. Introduction (1) Third leg of the modeling tripod. It describes interaction within a system. The class model describes the objects.
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.
1 Source: IBM Academic Program IBM Software Group ® Mastering Requirements Management with Use Cases Module 3: Introduction to Use-Case Modeling.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
Use Cases 7/09. lnot part of the system lrepresents roles a user can play lrepresents a human, a machine or another system lactively exchanges information.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
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.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
1 Use-Case Modeling Chapter 6 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman Edited by Solomon Negash.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
Revision.
Refining the Use Cases 1. How Use Cases Evolve  Early efforts typically define most of the major use cases.  The refining stages complete the process.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Team Skill 3 - Defining the System (Chapters of the requirements text ) Sriram Mohan 1.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
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.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Requirements and the Requirements Engineering Process
Systems Analysis and Design in a Changing World, 6th Edition
Recall The Team Skills Analyzing the Problem (with 5 steps)
Storyboarding and Game Design SBG, MBG620 Full Sail University
Unified Modeling Language
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Systems Analysis and Design in a Changing World, 6th Edition
Object Oriented Analysis and Design
Using Use Case Diagrams
Use Case Modeling.
Interaction Modeling Extracted from textbook:
Presentation transcript:

Functional Requirements – Use Cases (Chapters 14, 21) Sriram Mohan 1

What is a Functional Requirement? Functional requirements specify particular behaviors of a system. 2

What is a Use Case? A sequence of actions a system performs that yield and observable result of value to a particular actor Sequences of actions Performed by system of interest Observable result of value to a particular actor 3

Benefits Easy to write and read Think from the perspective of an user Provides a clear idea of the “what” and the “how” User involvement Use cases tell a better requirement story Typically developers are encouraged and required to write use cases. Why ? 4

Use Case Template A. Name B. Brief description C. Actors D. Basic flow E. Alternate flows F. Pre-conditions G. Post-conditions H. Other stakeholders I. System/sub-system J. Special requirements 5

Use Case Model - Development Steps 1. Identify the actors 2. Identify the use cases 3. Identify actor/use case relationships 4. Outline use cases 5. Refine use cases 6

1. Identify the Actors Who uses the system? Who gets/provides information from/to system? Who supports the system? What other systems interact with this system? 7

2. Identify the Use Cases What are the intentions of each actor with respect to the system? ◦ What are they going to use the system for? ◦ Does the actor provide some information? ◦ Does the actor need to be informed of something? 8

2. Identify the Use Cases Give a descriptive name: ◦ Start with an action verb ◦ Describes goal or intent Give a one-sentence description 9

3. Identify Actor/Use Case Relationships Draw a diagram showing relationships between actors and use cases 10 Eat food Buy food Parent Child

4. Outline Use Cases Describe sequence of events in basic flow (sunny day scenario) Describe sequences of events in alternate flows (rainy day scenarios) 11

5. Refine Use Cases Describe sequences of events for flows Describe pre-conditions Describe post-conditions Fill in special requirements 12

Pre and Post Conditions What is a pre-condition? What is a post-condition? 13

A. Name B. Brief description C. Actors D. Basic flow E. Alternate flows F. Pre-conditions G. Post-conditions H. Other stakeholders I. System/sub-system J. Special requirements Use Case Template 14

Microwave Example 15 User Cook Food

Cook Food Use Case – Slide 1 of 4 A. Name: Cook Food B. Brief description: User places food in microwave and cooks it for desired period of time at desired power level. C. Actors: User 16

Cook Food Use Case – Slide 2 of 4 D. Basic flow: 1.User opens door and places food in unit 2.User enters time for cooking 3.User pushes start button 4.Unit cooks food 5.Unit beeps 17

Cook Food Use Case – Slide 3 of 4 E. Alternate flows 1.User cancels time before starting 2.User cancels cooking before finished 3.User selects reduced power level before pushing start button 18

Cook Food Use Case – Slide 4 of 4 F. Pre-conditions ◦ Unit is plugged in ◦ Unit is in ready state G. Post-conditions ◦ Food is cooked or user cancelled operation H. Special requirements ◦ Timer should display remaining time to finish while cooking ◦ Default power setting should be "high" 19

How do the use case and the storyboard fit? 20

How do you know you have collected enough use cases? 21

22 Extending Use Cases Extend an existing use case instead of redefining it

23 Microwave Extension User Cook Food Slice Food >

24 Including Use Cases Frequent sequences of events may be defined as use cases Including a use case is like calling a subroutine

25 Microwave Inclusion User Cook Food Set Timer >

26 Cook Food Inclusion D. Basic flow: 1.User opens door and places food in unit 2.User performs Set Timer use case 3.User pushes start button 4.Unit cooks food 5.Unit beeps

Extra Credit Can all functional requirements be specified using use cases? Explain Turn in your Answer using Angel(Lessons – Extra Credit – Week 03- Use Case Extra Credit) 27

Exam 1 Managing Software Requirements(Second Edition) ◦ Chapters 1 – 14 ◦ Chapter 21 Interaction Design – Beyond Human Computer Interaction ◦ Chapter 11 28