Summary

Writing the requirements specification is not a separate activity, but one that is done in conjunction with other parts of the requirements process. Requirements analysts write requirements, or parts of requirements, whenever they find them. Not all requirements are completed at the same time.

This does not mean that writing the specification is a random activity. Business events, business use cases, product use cases, the template, and the shell make it possible to measure the degree of completion, and more importantly the areas in need of completion, at any time.

A requirements knowledge model is an abstract view of your filing system for managing your requirements knowledge. The model provides the basis for keeping track of the effect of one piece of knowledge on another.

Writing a good requirements specification is important. A well-written specification pays for itself many times overthe construction is more precise, the maintenance costs are lower, and the finished product accurately reflects what the customer needs and wants.