Mastering Use Cases and Scenarios

Many project teams have embraced use cases and scenarios as tools for documenting software requirements only to be disappointed with the final results. Many have discovered that while a well-written scenario is easy to read and can clearly describe the author's intent; actually writing effective scenarios is far from easy.

Often this is because of a deep-seated misunderstanding of use cases and scenarios; 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 scenarios to become more productive.

The course commences with a session that clarifies the underlying concepts behind use cases. The course then moves on to show how to draw effective use case diagrams and write clear scenarios based on a standard template.

The course concludes with discussions of how to organise a large number of use cases and the relationship between use cases and business processes.

During the course, participants are given ample opportunity to apply what they have learnt to a variety of practical exercises. Where appropriate, participants are also encouraged to work with actual use cases drawn from their business area.

Course Features

  • Clear discussion of the underlying concepts behind use cases
  • Ample time for practicing what has been learnt during the course
  • Based on latest version of the UML standard
  • Approach suitable for many different types of projects and modeling tools

Participant Benefits

  • 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

Who Should Attend

  • 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

Course Duration

  • 2 days

Course Agenda


  • Software Requirements
    • What Are Requirements?
    • Business Needs
    • Application Features
    • Software Requirements
    • Hotel Requirements
  • Systems Engineering Perspective
    • What is a System?
    • Requirements Need a Context
  • Activity Theory
    • Activity Theory Human Activities
    • Activity Theory Object-Oriented
    • Activity Theory Supported By Tools
    • Activity Theory Achieves Goals
    • Activity Theory Performed by Actors
    • Activity Theory Hierarchical

Use Case Concepts

  • Activity Theory and Use Cases
  • Benefits of Use Cases

Use Case Diagrams

  • Use Case Diagrams
    • UML Use Case Diagram Swiss Army Knife
    • Pre- and Post-Conditions
    • Include
    • Include
    • Generalise and Specialise
    • Use Case Steps
    • UML Use Case Diagram Hotel
  • Naming Use Cases
    • Naming Use Cases
  • Glossary
    • Glossary

Use Cases and Business Processes

  • Activity Diagrams
    • Use Cases and Business Processes
    • "To Be" WorkflowUML Activity Diagram
  • Interaction Between Actors
    • "To Be" Workflow UML Sequence Diagram

Use Case Descriptions

  • Use Case Steps
    • Use Case Steps
    • Use Case Steps subject...verb...object
    • Use Case Steps subject...verb...object
    • Repetition
    • Repetition
    • Concurrent Steps
  • Use Case Scenarios
    • Use Case Scenarios
    • Use CaseRecord Reservation Check In
    • Main Scenario
  • Business Rules
    • Business RulesTraditional Approach
    • Business RulesBetter Approach
    • Business RulesAuthorisations
  • Functional and Non-Functional Requirements
    • Functional and Non-Functional Requirements
    • System Wide Functional Requirements
  • Interface Requirements
    • Interface RequirementsPoor Approach
    • Interface RequirementsBetter Approach
    • Interface RequirementsBest Approach
    • Interface RequirementsData Dictionary
    • Interface RequirementsPrototype
  • Use Case Templates
    • Use Case Templates
    • Levels of Use Case Description
    • Use Case Narrative

Organising Use Cases

  • Functional Areas
    • Decomposing Use Cases
    • Functional Areas
  • Extending Use Cases
    • Extending Use Cases
    • Extending Use CasesSpecialisation
    • Extending Use Cases External Scenarios