1 Use Cases 1 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 17, 2004.

Slides:

Advertisements

Similar presentations

CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:

Advertisements

Systems Analysis and Design 8th Edition

1 Use Cases 2 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 20, 2004.

1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004.

1 Brainstorming CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 16, 2004.

1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2002] February 8, 2007.

Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,

Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.

1 Team Skill 4 - Team Skill 5 - Scope Refining the Systems Definition (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.

Uml and Use Cases CS 414, Software Engineering I Mark Ardis Rose-Hulman Institute January 9, 2003.

Chapter 10 System Sequence Diagrams. What is a System Sequence Diagram? A way of modeling input and output events related to systems It is a picture that.

1 Usability Testing Roles CSSE 376 Software Quality Assurance Rose-Hulman Institute of Technology April 23, 2006.

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.

1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,

Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.

Use Case Systems Analysis & DesignUse Case1 Use case refers to A system’s behavior (functionality) A set of activities that produce some output.

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.

CSCI928 Software Engineering Requirements & Specifications Modeling System Interactions Tri A. Kurniawan, M.Eng. Ph.D Candidate

1 PrototypingPrototyping CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 28, 2004.

A use case describes one “case” of how a user can use the system.

Team Skill 6 - Building The Right System Part 1: Applying Use Cases (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.

Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.

1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.

1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2005] February 5, 2009.

Functional Requirements – Use Cases Steve Chenoweth & Chandan Rupakheti (Chapters 14, 21 – Requirements Text)  Quiz question 9 relates to this, when you’ve.

TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.

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.

RUP Requirements RUP Artifacts and Deliverables

UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University

UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.

 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.

Chapter 5 Models and UML Notation for The Object-Oriented Approach.

Systems Analysis & Design 7 th Edition Chapter 5.

Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.

Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.

PRJ566 System Sequence Diagrams.  A system sequence diagram …. Illustrates input and output events related to the system under discussion.  Larman,

® 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.

1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.

♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.

Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'

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

Drawing System Sequence Diagrams

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.

 Relate Use Cases to  MVC and Application Architecture  CRC  Recap distinctions : Language, Process, Tool  Detail a Use Case  Elements of a Use Case.

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.

System sequence diagrams

Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.

CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.

Unit-3 Identifying use cases Object Analysis Classification

OOAD (part 2) diagrams CSCI577a TAs: Alexey. Outline UML diagrams: – Use case diagrams – Robustness diagrams – Sequence diagrams – Artifacts diagrams.

Summary from previous lectures

High Level Design Use Case Textual Analysis SE-2030 Dr. Mark L. Hornick 1.

Team Skill 3 - Defining the System (Chapters of the requirements text ) Sriram Mohan 1.

SYSTEM-LEVEL SEQUENCE DIAGRAMS Sys466. System-Level Sequence Diagrams  Use cases describe how external actors interact with the software system…  An.

1. In an activity diagrams, a Boolean test which shows how flow betweenactivities occur and represents in [], is called: pre-condition post-condition an.

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.

System sequence diagrams

BTS430 Systems Analysis and Design using UML

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.

How do we convince people that in programming simplicity and clarity —in short: what mathematicians call "elegance"— are not a dispensable luxury, but.

Sequence Diagrams Lecture 6.

Unified Modeling Language

UML Diagrams: Sequence Diagrams Dynamic Analysis Model

CS 425 Software Engineering

CS 425/625 Software Engineering

Presentation transcript:

1 Use Cases 1 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 17, 2004

2 What is a Use Case?  Sequences of actions  Performed by system of interest  Observable result of value to a particular actor

3 Use Case Method 1. Identify the actors 2. Identify the use cases 3. Identify actor/use case relationships 4. Outline use cases 5. Refine use cases

4 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?

5 2. Identify the Use Cases  What are the intentions of each actor with respect to the system?  Give a descriptive name: Start with an action verb Describes goal or intent  Give a one-sentence description

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

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

8 5. Refine Use Cases (more later)