4.7 Summary

Start your requirements effort with the Facade iteration. This process gives you a high-level view of the system that you are going to build, and it organizes your efforts by giving you placeholders for the tasks that remain .

To create the Facade iteration, dig into the system and talk to the stakeholders. As you build a mental image of the system, describe its components in simple use cases. When you have Facade use cases written for the major parts of the system, the work remaining for other iterations is to increase the value of each one until you have documented sufficient detail to build the system.

Several tools are at your disposal to help keep this iteration on track. The verb, use case name , and actor filters will help you avoid classic use case traps. The supporting requirements documentation (see Chapter 3), together with the Facade use cases, immediately reduces the ambiguity of what the system must do for its users, and this is the central point of requirements gathering.



Use Cases. Requirements in Context
Use Cases: Requirements in Context (2nd Edition)
ISBN: 0321154983
EAN: 2147483647
Year: 2002
Pages: 90

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net