© Telelogic AB
Scope Levels Are Important
A typical mistake when writing requirements specifications is to mix scope levels:
A requirements specification shall have exactly one scope level
It shall not contain requirements for a higher or lower scope level => those shall be in separate artifacts
Best choice is to identify owners for all requirements artifacts on all different scope levels
Even if a sub-system team has to write system specifications those shall be separate system level artifacts and not mixed into the sub-system artifacts.
A sub-system specification shall not talk about system product versions.