X hits on this document

100 views

0 shares

0 downloads

0 comments

12 / 30

12

© 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.

Bernd@Grahlmann.net

©

Document info
Document views100
Page views100
Page last viewedTue Jan 17 01:57:00 UTC 2017
Pages30
Paragraphs489
Words2426

Comments