Requirements Gathering With Use Cases and the UML

Requirements Gathering With Use Cases and The Unified Modeling Language (UML) workshop teaches attendees to fully define the scope and requirements of an application using practical object analysis techniques using the Unified Modeling Language as the notation. Although the UML is comprised of nine diagrams and different views of the recently standardized UML (Unified Modeling Language), this course focuses more on the Requirements phase and the use of UML Use Cases. Categorization and capturing of business rules are also thoroughly explored.

This course is targeted at the "business user" as well as the Information Technology analyst. It is ideal for bridging the communications gap many times encountered when Information Technology (IT) staff work with the user to gather, detail, and confirm requirements.

The UML Use Case diagram and supporting documentation will be the primary mechanism for specifying the project’s requirements. An extended case study is used to demonstrate the approaches along with several templates. There will also be a project plan distributed used to show a plan indicative of a project that employs Use Cases.

Section One: Introduction

A. Definitions
B. Introduction of Instructor
C. Logistics
D. Target Audience
E. Expectations
F. Course Objectives
G. Requirements: Too Many Meanings
H. Use Cases and Functional Requirements
I. A Use Case is a Transaction
J. The Use Case Diagram
K. Use Case Template
L. Activity Diagram
M. UML Components
N. Where do Use Cases fit in
O. The UML Means Traceability
P. How does the team attack the problem?

Section Two: Requirements and the Project Vision

A. Sound Familiar
B. Source of Errors
C. Symptoms of Project that Fail
E. What is a Requirement
F. Levels of Requirements
G. User and System Requirements
H. Functional Requirement
I. Non-Functional Requirement
J. Requirements Artifacts
K. Ways to Test Requirements
L. The Vision
M. Defining Stakeholders
N. Features List

Section Three: Getting to Use Cases

A. What is a Use Case?
B. Use Case Actors
C. Kinds of Actors
D. Different Ways to get to Use Cases
E. Use Case Scenarios
F. Getting to Use Cases
G. The Event List
H. How Granular are Events?
I. Use Case Packages
J. Levels of Use Cases
K. Granularity is Subjective
L. Use Case Relationships
M. Use Case Includes
N. Use Case Extends
O. Use Case Generalizes
P. Summary-level Use Case
Q. Shadow Use Cases

Section Four: Detailing Use Cases

A. Happy Paths
B. Alternative Paths
C. Exception Paths
D. Use Case Template
E. Iterating through Use Cases
F. Pre-Conditions
G. Post-Conditions
H. Pathway Detail
I. A Use Case Metaphor
J. Activity Diagram
K. How to handle conditional logic
L. How can alternates end?
M. Business Rules
N. Types of Business Rules
O. Rules in the Use Case Template
P. Business Rules Catalog
Q. Other Rule Capture Techniques
R. Use Case Heuristics

Section Five: State Diagrams, Activity Diagrams, and the User Interface

A. State Diagram
B. Life Cycle of an Order
C. State Chart
D. Activity Diagram
E. Synchronization
F. Validate User Interface Flow with Use Cases
G. User Interface Structure Chart
H. Screen Dialogues

Section Six: Summary

A. What happens next with the use cases?
B. Elaboration and Use Case Realizations
C. Dynamic View
D. Architectural Prototype
E. Use Cases – Next Steps

Who Should Attend

Business users, Information Technology analysts, and Managers.

Prerequisites

This course has no prerequisites.

Seminar Length

2 days

Federal Reserve Bank of San Francisco

VISA USA

VISA International

GE Engines

Ford Motor Company

Eli Lilly

Sallie Mae

US Department of the Treasury

Safeco Insurance

PEMCO Insurance

Pacific Gas and Electric

PayPal