Print this Page

Use Cases for Requirements Definition

Use Cases for Requirements Definition teaches how to gather business system requirements, including business rules, into concise Use Case Models.  In this intensive 2-day workshop, participants will learn several approaches for identifying use cases that are situation dependent.  The workshop will cover approaches for identifying use cases, describing user expectations, and capturing data requirements, as well as non-functional requirements.

Use Cases for Requirements Definition teaches how to achieve effective communications with non-technical people about system requirements.  The classic method of defining screen and report layouts is not sufficient for today’s integrated applications.  Complete system requirements covering all application aspects must be defined accurately and effectively early in a project to achieve project success.

Use Cases for Requirements Definition uses a comprehensive case study to give practical application to the principles discussed.  Participants work in teams on the case study that simulates actual work experience.  Using notation of the Unified Modeling Language (UML), participants learn how to identify use cases, write the course of events and capture the details that define the requirements for the use case.  In addition, participants learn how to test their use case models for validity, correctness, and completeness.

Use Cases for Requirements Definition shows the wide variety of requirements expression available with the Use Case technique and how to tailor the technique to different types of project situations.

What You Will Learn

• How and why Use Cases form a key component of business and systems analysis

• How to employ Use Cases to surface business and systems requirements

  • Functionality

  • Key business rules

  • Inter-system collaborations

• How to draw out the details typically missed in requirements

• How to integrate Use Cases with other techniques

  • Data Modeling/Domain Modeling

  • Business Process Mapping

  • Requirements Lists

• How to avoid the traps of poor Use Case application

• How to tailor the style of the Use Cases to the needs of the project

Who Should Attend

• Business Analysts

• Systems Analysts

• Programmer/analysts

• Project managers

• Developers

• Functional managers

Seminar Outline

Introduction: What is a Use Case?

• The Problem – Surfacing Requirements

• Use Case – A Focusing Technique

• History Of Use Case

• A Spectrum Of Applications For Use Case

• A Spectrum Of Styles Of Use Cases

Stakeholders, Actors, Interests, and Goals

• Stakeholder Analysis

• Actor Classification

• Developing the Actor-Goal List

• Exercise/Case Study

Use Cases from a Business Process

• Intro to Business Process Improvement

• Intro to Business Process Mapping

• Business Use Case – to define Business Process

• System Use Case – to define System Requirements

• Exercise/Case Study

Writing the Main Use Case

• The Use Case Template

• Detailing the Use Case Actions

• Handling Exceptions and Alternates

• Dealing with Failure

Associating Use Cases

• Use Case “uses” another Use Case

• Use Case “extends” another Use Case

• Diagramming Use Case associations

• Exercise/Case Study

Integrating Use Cases with Data Modeling

• Data Model as Glossary for Use Case

• Linking Use Cases to Requirements

• Exercise/Case Study

Integrating Use Cases with Requirements

• Use Case as a Requirements Statement

• Linking Use Cases to Requirements

• Exercise/Case Study

Integrating Use Cases with Object Modeling

• Linking Use Cases to Objects

Use Cases Beyond Requirements

• Use Cases in Interface Design

• Use Cases to Test Cases

• Use Case Management

• Use Case Tools