Managing Software Requirements: A Use Case Approach, Second Edition

Chapter 28. Managing Change

Key Points

• A process to manage requirements can be useful only if it recognizes and addresses the issue of change.

• Internal change factors include failing to ask the right people the right questions at the right time and failing to create a practical process to help manage changes to requirements.

• In order to have a reasonable probability of success, requirements leakage must be stopped or at least reduced to a manageable level.

Why Do Requirements Change?

If it were possible to create a definitive set of requirements for a system once and only once, life would be much simpler, and there would be no need for this chapter. We could simply create a perfect Vision document, use-case model, and supplementary specification; freeze ...