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

NASA Systems Engineering Handbook

SWE or Topic

SWE-005, SWE-013, SWE-014, SWE-016, SWE-018, SWE-019, SWE-028, SWE-030, SWE-034, SWE-035, SWE-036, SWE-038, SWE-046, SWE-049, SWE-050, SWE-054, SWE-056, SWE-057, SWE-058, SWE-060, SWE-063, SWE-073, SWE-074, SWE-075, SWE-079, SWE-102, SWE-110, SWE-112, SWE-116, SWE-121, SWE-125, SWE-126, SWE-129, SWE-136, SWE-147, SWE-150, SWE-153, SWE-154, SWE-155, SWE-156, SWE-157, SWE-158, SWE-159, SWE-193, Topic 7.5, Topic 7.12, Topic 7.18, Topic 7.6, SRS, IDD, SDD, SDP, SVD,

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

NASA SP-2016-6105 Rev2 supersedes SP-2007-6105 Rev 1 dated December, 2007

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

Example Reference as it will appear to end user:

  1. Title, Citation


Quotes used in SWEs and Topics

"Scheduling is an essential component of planning and managing the activities of a project. The process of creating a network schedule provides a standard method for defining and communicating what needs to be done, how long it will take, and how each element of the project WBS might affect other elements. A complete network schedule may be used to calculate how long it will take to complete a project; which activities determine that duration (i.e., critical path activities); and how much spare time (i.e., float) exists for all the other activities of the project" Key Issues for Requirements Management - Requirements Changes
"Effective management of requirements changes requires a process that assesses the impact of the proposed changes prior to approval and implementation of the change." Analyze Product Validation Results - Validation Deficiencies
"Care should be exercised to ensure that the corrective actions identified to remove validation deficiencies do not conflict with the baselined stakeholder expectations without first coordinating such changes with the appropriate stakeholders."

"examines the functional characteristics of the configured product and verifies that the product has met, via test results, the requirements specified in its functional baseline documentation approved at the preliminary design review (PDR) and critical design review (CDR). FCAs will be conducted on both hardware or software configured products and will precede the PCA of the configured product."

"(also known as a configuration inspection) examines the physical configuration of the configured product and verifies that the product corresponds to the build-to (or code-to) product baseline documentation previously approved at the CDR. PCAs will be conducted on both hardware and software configured