Requirement tracking: a streamlined approach
J.E. Archer · Journal of Lightwave Technology · 2004
The streamlined approach is a midrange approach to requirement tracking that rejects both a high degree of formality (such as requirements matrices) and informal techniques (such as "user stories"). The basic requirement unit is the requirement statement, not the document, or the use case. Typically, requirements statements are from one to four sentences long. The key concept of the streamlined approach is that of the concrete software requirement. The two primary characteristics are: 1) The requirement is linked to a single software deliverable which it specifies. 2) There exists a well defined completion criterion for determining when the deliverable satisfies the requirement.