Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

Leave blank if none exists

This is the text which will be hyperlinked, if a link exists

Software Requirements Engineering: Practices and Techniques,

SWE or Topic

SWE-049, SWE-050, SWE-051, SWE-052, SWE-053, SWE-055, SWE-109, Topic 5.09, Topic 7.18, SRS,

This contains additional information, which will appear after the title, separated by a comma

JPL Document D-24994, NASA Jet Propulsion Laboratory, 2003.

More specific directions where to look in the resource for relevant content

See Page 20.
Approved for U.S. and foreign release.

Example Reference as it will appear to end user:

  1. Title, Citation


Quotes used in SWEs and Topics

3.5. Management Practices - Control how requirements are introduced, changed, and removed.
"The average project experiences about a twenty-five percent change in requirements after the requirements have been defined for the first system release, which causes at least a twenty-five percent schedule slip. Several studies also have shown that volatility in requirements contributes to the inefficient production of low-quality software (11, 13). Consequently, requirements should be managed using a defined configuration management process that uses change control boards and automated change control tools that manage each requirement as a separate configuration item (10, 27).1 Using a configuration management tool permits personnel to identify which requirements have been added, removed, or changed since the last baseline, who has made these changes when they were made, and the reason for making them. In addition, by maintaining requirements in a configuration management tool, they can be traced to the artifacts that realize them."