Roadmap: How to Adopt the Detailed Use-Case Requirements Analysis Practice
This roadmap describes how to adopt the Detailed Use-Case Requirements Analysis practice.
Main Description

Getting Started

Begin by reviewing Chapter 3 of the Redbook, Model Driven Systems Development with Rational Products. This drives home the importance of understanding context, how context drives usage, and how usage helps us discover requirements that ensure that the system meets the stakeholder needs. In short this practice is about the following:

  • Understanding context.
  • Understanding how the system is used, and who or what uses it.
  • Understanding the information exchanged with the system.

Common Pitfalls

Done in Order

Most of the activities/steps are done in an iterative fashion. They aren't meant to be done in an order, like the classical waterfall process shows.

Done out of Order

There's an importance to understanding "context" before trying to understand what the system needs to do. Experience has shown many times where a group that thought they were all on the same page, didn't agree on what was inside vs. outside of the system they were responsible for building.