Developing Use Cases

Introduction

• What is a use case? What is use case modeling?
• Where do use cases fit in the requirements package?
• Review the 7 characteristics of excellent requirements
• What are the differences between business and functional requirements?

Translating Business Requirements to Functional Requirements

• Define the design area scope. Once the analysis is complete and the business requirements have been documented, the project team must decide which business processes will be automated.
• Learn a six-step approach to defining the design area scope:
• Document the functional design of each process.
• Document business priority.
• Document technical priority and estimated cost.
• Break project into phases.
• Workshop: Document design area using a use case diagram:
• Define actors involved with the application.
• Identify actor interactions.
• Learn multiple techniques to derive use cases from essential business processes.
• Obtain signoff

Documenting System Functionality

• Learn to identify use cases.
• Outline each use case for a high-level understanding of broad behavior.
• Identify primary path, alternate path, and exception paths.
• Decompose large use cases into smaller sub-sets, identifying reusable use cases where possible.
• Learn how and where to document system user messages.
• Learn 8 steps for excellent use case generation.
• Learn to create detailed use case descriptions.
• Workshop: Learn to document detailed use case descriptions using the B2T template.