[176] in Project_DB
Notes on requirements traceability
daemon@ATHENA.MIT.EDU (Tim McGovern)
Thu Jul 31 14:27:51 1997
Date: Thu, 31 Jul 1997 14:22:38 -0400
To: project-db@MIT.EDU
From: Tim McGovern <tjm@MIT.EDU>
I submit this for background purposes only...the text is copyrighted by
Gartner...do not post outside of MIT!
Tim
-----
Rigorous traceability ensure[s] that user needs are fully met and that no
unintended system behavior occurs: Each documented user requirement must be
traced to a software function; and each software function must be traceable
to a user requirement, or it will yield unspecified behavior. Traceability
links requirement attributes to show that user needs are met and that the
system will not work in unexpected ways (see Note 1 for examples of
requirement attributes).
Note 1
Examples of Requirement Attributes
* Reason for requirement
* Resource to meet requirement
* Time created or updated
* Version number, as requirement is revised
* Status (e.g., proposed, in progress or tested)
* Parent and child requirements, dependencies, including links to non-IS
projects
* Priority of requirement (in function, budget or schedule)
* Owner, person or team to work on requirement
Copyright 1995-1996 by Gartner Group, Inc. All rights reserved.
