Mastering Use Cases
 

Code:

 IS130-051

Series:

 Information Management

Duration:

 2 days

Introduction
Hierarchy of Requirements
Business Needs
Application Features
Software Requirements
Requirements From a Systems Engineering Perspective
What is a System?
Requirements Context
Characteristics of Human Activity
Object-Oriented
Supported By Tools
Achieves Goals
Performed by Actors
Involves stakeholders
Conforms to Rules
Allocated Responsibilities

Use Case Concepts
Use Case & Activity Theory
Naming Use Cases
Importance of a Glossary

Use Case Diagrams
Elements of a Use Case Diagram
System Boundary
Actor
Use Case
Pre- and Post-Conditions
Relating Use Cases
Include
Generalise and Specialise
Introduction to Use Case Steps
Refining Actors
Human Actors
Other Systems as Actors
Secondary Actors

Use Cases & Business Processes
Use Cases and Business Processes
Showing Sequences of Use Cases
Showing Flow of Control Between Use Cases
Use Cases and UML Activity Diagrams
Use Cases and Workflow Between Actors
Showing Interaction Between Actors
Use Cases and UML Sequence Diagrams

Use Case Descriptions
Use Case Steps
The subject...verb...object template
Actor as the Subject
System as the Subject
Time as a Trigger
How to Handle "Actorless" Use Cases
Repetition
Repeating Steps
Concurrent Steps
Use Case Scenarios
Main Scenario
Alternate Scenarios
Handling Business Rules
Handing Functional and Non-Functional Requirements
Dealing With System Wide Functional Requirements
Interface Requirements
Handling Interface Requirements
Data Dictionary
Prototype

Organising Use Cases
Functional Areas
Decomposing Use Cases
Extending Use Cases
Specialisation
External Scenarios

Mastering Use Cases

Many project teams have embraced use cases as a tool for documenting software requirements only to be disappointed with the final results. Many have discovered that while a well-written use case is easy to read and can clearly describe the author’s intent; actually writing effective use cases is far from easy. Often this is because of a deep-seated misunderstanding about what use cases are and the best way to use them as a tool for describing software requirements. This two-day workshop is designed to help participants master use cases and become more productive use case authors.

Outcomes:

  • a clear understanding of use case concepts
  • ability to identify and describe actors and use cases
  • ability to document use cases using use case diagrams and use case descriptions based on a standard template

Prerequisites:

Familiarity with business environments and business information systems. Suitable for:

Business Analysts, Business Systems Analysts, Systems Analysts, Functional Analysts, Software Development Managers, Software Engineers, Software Architects, Developers, Requirements Engineers, Requirements Analysts, Users, User Representatives, Stakeholders, Project Sponsors, Project managers, Program Managers, Consultants, technical writers, educators and trainers.