


h1. 1. Requirements



NPR 7150.2 does not include any notes for this requirement.

h2. 1.2 Applicability Across Classes

This requirement applies to all classes and safety criticalities.



h1. 2. Rationale



h1. 3. Guidance


When approval is granted for an action from [SWE-120], the program/project also includes the results of the request, the rationale for the request, along with any approved alterations to the initial request, in the baselined program/project documentation (e.g. Constellation program Computing System Requirements). Typically, Center changes are reflected in the Center's local implementation of the flow down of NPR 7150.2 (e.g., Center Directives, Center Procedural Requirements covering software engineering, software assurance plans).  The Center-level procedure typically is stored in the Center's central documentation repository.  As the alternate requirements generally affect processes, related process assets are updated in the process asset library for future use by software development teams within scope of the generic waiver.


h1. 4. Small Projects



h1. 5. Resources

#  United Space Alliance, [PASS Software Management Plan|https://nen.nasa.gov/webconnector/ProxyServlet/nx.arc.nasa.gov/nx/dsweb/Get/Document-499373/USA_002859.pdf?url=https%3A%2F%2Fnx.arc.nasa.gov%2Fnx%2Fdsweb%2FGet%2FDocument-499373%2FUSA_002859.pdf&sid=9F1B9F044D1CABD716FCD5AB144F1205.jvm137&ns_prefix=javax.portlet.p.webconnector_WAR_webconnector_INSTANCE_PA7b_LAYOUT_198954%3F&ns_sufix=], USAD02859, March 27, 2003. Discusses configuration control activities within a Software Management Plan for an actual project.
#  [Software Configuration Management Technologies and Applications|http://stsc.hill.af.mil/resources/tech_docs/cm_reportv4.0.pdf], Software Technology Support Center, Hill AFB ( [www.stsc.hill.af.mil|http://www.stsc.hill.af.mil/] ).The document is a good discussion of basic CM practices and indicates the importance for documenting new and revised requirements.
#  [NASA Systems Engineering Handbook|http://education.ksc.nasa.gov/esmdspacegrant/Documents/NASA SP-2007-6105 Rev 1 Final 31Dec2007.pdf] , NASA/SP-2007-6105 Rev1, 2007
#  [NASA Directives Procedural Requirements, with Change 5 (11/19/2009)|http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=1400&s=1D], NPR 1400.1D, 2009
#  NASA Headquarters Office of the Chief Engineer [engineering deviations and waivers website|https://nen.nasa.gov/web/oce/ta]
#  [NASA Engineering and Program/Project Management Policy|http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPD&c=7120&s=4D], NPD 7120.4D, 2010
#  [NASA Space Flight Program and Project Management Requirements|http://nodis3.gsfc.nasa.gov/npg_img/N_PR_7120_005D_/NM_7120-81_.pdf], NPR 7120.5D (NM-7120.81), 2009.



h2. 6. Lessons Learned

A documented lesson from the NASA Lessons Learned database (http://www.nasa.gov/offices/oce/llis/imported_content/lesson_1715.html ) notes that without documenting and thereby capturing details of the rationale for decisions affecting systems designs (requirements) "...project staff found themselves repeatedly revisiting the same technical issues."Now why did we decide...'" This is a good indication that why it was done is as important, at times, as to what was done.  OCE personnel, future projects or Center personnel will be able to avoid reevaluating these general exclusion or alternate requirement approvals if they have appropriate access to the rationale so they can properly understand the basis on which the exclusions were granted in the first place.