On "Future" Requirements

Few development efforts have the luxury of either a stable set of requirements or the ability to build a system that satisfies all desired requirements. During any process of requirements elicitation , requirements will arise that are deemed appropriate for the next release of the product.

It may not be appropriate to include such requirements in the requirements set since we cannot afford to create any confusion about what requirements are and are not to be implemented in a particular release. On the other hand, it's unwise to discard them because they represent value-added work products, and we will want to harvest requirements from them for future releases. More important, the system designers may well have designed the system differently had they known that future requirements of a certain type were desired. So it makes sense to record both types of requirements but to clearly identify those requirements that are planned for the current release .


Managing Software Requirements[c] A Use Case Approach
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
Year: 2003
Pages: 257

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