For example, suppose you have a requirement that your information manager application display a Dilbert cartoon each morning. In this case, the low dissatisfaction rating indicates that this is a gold-plated requirement. We have found that, to be successfully measured and tested, each requirement must have a number of elements. The requirement gatherer gradually completes each part of the shell as the information becomes known. This is not intended to reduce requirements gathering to a clerical task, but to provide a convenient way of ensuring that the requirements are complete.
Traceable Requirements Assign a unique identifier to each requirement.
The type is followed by a unique number. Thus R9.246 is a functional requirement, and it happens to be the 246th requirement that you have gathered to date. The event, or use case, number is attached to the requirement to provide a pointer to its origin. The requirement should also carry references to supporting materials and anything that may be useful to understand more about this requirement. It is particularly useful to reference dependencies.