We want to be able to prove that the system that we build meets each one of
the specified requirements. We need to identify each requirement so that we can
trace its progress through detailed analysis, design and eventual
implementation. Each stage of system development shapes, repartitions and
organises the requirements to bring them closer to the form of the new system.
To insure against loss or corruption, we need to be able to map the original
requirements to the solution for testing purposes.
Requirements Test 9
Is each requirement uniquely identifiable?
In the micro spec in Figure 1 we see that each requirement must have a unique
identifier. We find the best way of doing this is simply to assign a number to
each requirement. The only significance of the number is that it is that
requirement's identifier. We have seen schemes where the requirements are
numbered according to type or value or whatever, but these make it difficult to
manage changes. It is far better to avoid hybrid numbering schemes and to use
the number purely as an identifier. Other facts about the requirement are then
recorded as part of the requirements micro spec.
