Courses

Eliciting and Documenting User Requirements with Use Cases

$1,495.00

Categories: ,

Description

The two day 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.

What you will learn:

  • Facilitate requirements-gathering sessions with Business and System Use-Cases.
  • Examine the impact of the project on the enterprise through business use-case analysis.
  • Create detailed textual requirements using a Use-Case Description Template.
  • Decrease software bugs and omissions introduced in the analysis phase of your project – by employing advanced use-case techniques that reduce redundancies and inconsistencies in the documentation.
  • Facilitate communication of user requirements between business stakeholders and the solution provider.
  • Model who-does-what with use-case diagrams.
  • Understand how use-cases are used in the context of iterative development.
  • Link other relevant material to use-cases – such as business entities, non-functional requirements and activity diagrams.

Audience 

  • 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.

Prerequisites: none