The course provides hands-on experience with use cases, today’s most widely accepted method of requirements capture.  The clear style and organization of use cases makes them well suited as a source of test cases; for communicating with both business stakeholders and developers; and as a preferred choice for persistent requirements documentation on both Waterfall and agile projects that need to ‘persist’ requirements for communication with non-agile teams and for future product changes.

In this course, you’ll walk through the requirements elicitation and documentation process over the course of a project, implementing the ‘use-case’ approach used widely in the industry, methodologies and standards (e.g., the UML, RUP, MSF, Use-Case 2.0). You’ll learn that ‘use cases’ are about much more than the documentation – that they are also an effective tool for structuring and facilitating elicitation events over the course of an IT Project.  You’ll learn how to phase in the analysis the ‘use-case’ way – starting from business use-case interviews that focus on business processes and services through to system use-case interviews that focus on user-IT interactions. The course also provides practical guidance on handling common analysis situations – such as how to model user authentication requirements, business rules and functional requirements when using the use-case approach.


Inexperienced BAs are often unclear about what level of requirements to capture at each phase of a project. 
• This course provides clear guidance by pacing the trainee through the requirement-gathering process from high-level business use cases down to low-level requirements.
BAs are often confused about how best to divide up the requirements documentation for a large project.
• Trainees learn how to divide the project into end-to-end business process requirements as business use-cases and how best to decompose these into smaller units as  system use cases.
BAs need help in documenting the text of user requirements.
• This course provides explicit, detailed instruction in the writing, numbering and organization of the textual requirements.
Small changes to the business environment unfortunately often lead to big changes in the documentation.
• This course provides detailed instruction in the use of advanced documentation features (extensions, inclusions and generalizations) that reduce redundancies in the documentation, making it easier to revise.
BAs need experience to be effective facilitators of requirements-gathering sessions.
• Trainees gain practice acting as facilitators for their group as they advance the case-study project. 

What makes this course stand out from the competition?

The best course for learning what questions to ask when. 
• Learn what you need to find out from stakeholders at each stage of the project.
Trainees learn by doing - by developing a case study in ‘real time.’
Group facilitation sessions provide in-depth experience in using a team-based approach to development.
2 courses in one:
• Many of our competitors offer one course in requirements elicitation and another in use-cases.  Rather than teach you hard-to-apply general rules for requirements analysis that require a follow-up course, we teach the topic once – the right way. In one course you learn how to capture requirements with detailed guidance for doing it using today’s most popular approach - use cases.
Includes valuable take-home materials: Comprehensive printed material including valuable job aids, examples, glossaries, tips, the Noble Path, as well as agendas and lists of questions for each type of interview session.
In keeping with the practical nature of the course, the course content draws from direct experience working in a variety of sectors, including banking, accounting, call centers, education and NGOs.
Focused content: includes the practical tools and techniques most commonly used to get the job done.


IT Business Analysts 
Project Leaders
Facilitators who will be leading requirements gathering sessions 
Business Users who will be explaining business requirements to software developers
Systems Analysts expanding their role into the business realm.




2 Days

Outline for Eliciting and Documenting Requirements with Use Cases (BABOK 3)

Lesson 1: Introduction to Requirements Capture with Use Cases 
Lesson 2: The Kick-off Meeting 
Lesson 3: Analyze Business Use Cases 
Lesson 4:  Structure System Use Cases 
Lesson 5: Describe System Use Cases/ Context and Basic Flow 
Lesson 6: Describe System Use Cases/ Alternate and Exception Flows 
Lesson 7: Describe Special Use Cases 
Lesson 8: Map Use Cases to Other Project Models and Deliverables