Managing Software Requirements: A Unified Approach

Chapter 16. Organizing Requirements Information

Key Points

• For nontrivial applications, requirements must be captured and recorded in a document database, model, or tool.

• Different types of projects require different requirements organization techniques.

• Complex systems entail requirements specification for each subsystem.

Requirements must be captured and documented. If you were the sole developer for a system on which you will also be the sole user and maintainer, you might consider designing and coding it immediately after identifying your needs. However, few system developments have such simplicity. More likely, developers and users are mutually exclusive, and stakeholders, users, developers, analysts, testers, architects, and other team members ...