Eliciting and Documenting Requirements with Use-Cases

#text-block-10 { margin-bottom:0px; text-align:left; }

1. Introduction to use-cases

History of use-cases
use-cases and the Business Requirements Document
Link to other technologies:
OO, Iterative development

2. Criteria for selecting projects
3. Facilitating Requirements – Gathering Sessions with use-cases:

Rules for conducting use-case workshop sessions
Preparation
Who should attend
Roles
Defining the Deliverables
When to best introduce and create:
Stakeholder Interest Table
use-case Packages
Role Maps
use-case Diagrams
use-case Text

4. Analyzing the impact on the Enterprise

Eliciting and documenting end-to-end business processes with business use-cases:
Business use-case diagrams
Documenting business use-cases
Modeling business use-case workflow with activity diagrams

5. Eliciting and documenting user requirements with system use-cases

use-case Description Template for textual documentation
Writing guidelines
How to number the requirements

6. Defining the users of the system:

Role Map
Defining actors, “generalized” and “specialized” actors

#text-block-11 { margin-bottom:0px; text-align:left; }

7. Working with stakeholders to discover and document system use-cases:

Triggers
Preconditions
Postconditions
Basic (Normal) Flow
Alternate and Exceptional Flows

8. Organizing the documentation for maximum reuse with inclusion, extension and generalized use-cases
9. Links to other documentation

Data dictionary
Entity classes and class diagrams
Activity Diagrams
Non-functional requirements

10. Avoiding common errors
11. Standard solutions for common situations, e.g.:

Customer IVR (Interactive Voice Response) identification
CRUD (Create/Read/Update/Delete a business object)
Login
Customer self-service
Geographical sub-sites within an e-commerce application

12. Job Aids containing:

Templates
Tips
Examples
Glossary of technical terms