Docstoc

Task4_NPR 7150 traced to NPR 7123 and NPR 7120_20100716

Document Sample
Task4_NPR 7150 traced to NPR 7123 and NPR 7120_20100716 Powered By Docstoc
					Related NPD 7120.4D policy                                                                                                                                                              Related NPR 7120.5D requirements
and responsibilities                                                                                                                           Related NPR 7123.1A requirements         (NID: NM_7120-81)

                              NPR 7150.2A requirements                                                                               ID

                              This NPR shall be applied to software development, maintenance, retirement, operations,
5.h.2                         management, acquisition, and assurance activities started after its initial date of issuance.          SWE-001   2.1.1.4

                              The NASA Headquarters Office of the Chief Engineer shall lead, maintain, and fund a NASA
5.b.1; 5.b.18                 Software Engineering Initiative to advance software engineering practices.                             SWE-002


                              Each Center shall maintain, staff, and implement a plan to continually advance its in-house
                              software engineering capability and monitor the software engineering capability of NASA's
5.h.5                         contractors, as per NASA's Software Engineering Initiative Improvement Plan.                           SWE-003


                              The NASA Headquarters' Chief Engineer shall periodically benchmark each Center's software
5.b.3; 7.a; 5.h.3; 5.j.8      engineering capability against its Center Software Engineering Improvement Plan.                       SWE-004

5.h.1                         Each Center shall establish, document, execute, and maintain software processes.                       SWE-005


                              To support compliance with NASA policy and facilitate the application of resources to mitigate
                              risk, the NASA Headquarters' Chief Engineer, in coordination with the Chief, Safety and Mission
5.h.8; 5.b.5                  Assurance shall maintain a reliable list of the Agency's programs and projects containing software. SWE-006

                                The project shall develop software plan(s).
                                These include, but are not limited to:
                                a. Software development or management plan.
                                b. Software configuration management plan.                                                                                                              4.4.2.c.2 (Appendix F)
                                c. Software test plans.                                                                                                                                 4.5.2.c.1 (Appendix F)
General SW Engineering (1.f.1 & d. Software maintenance plans.                                                                                 3.2.10.1 (C.3.1.3.c, C.3.1.4.d)          4.1.2.a.3 (Appendix E)
5.j.3)                          e. Software assurance plans.                                                                         SWE-013   General link; specific plans not named   (not all plans noted here are included)

                                                                                                                                                                                        4.4.2.c.2 (Appendix F, Section 3.2)
                                                                                                                                                                                        4.5.2.c.1 (Appendix F, Section 3.2)
1.g; 5.c.1                    For safety-critical software, the project shall develop a software safety plan.                        SWE-130                                            (compliance with NASA-STD-8719.13)

                              If a project is selected for software Independent Verification and Validation (IV&V) by the NASA
                              Chief, Safety and Mission Assurance, the NASA IV&V program shall develop an IV&V Project
5.c.5                         Execution Plan (IPEP).                                                                                 SWE-131

                                                                                                                                                                                        4.5.2.b.1 (implement)
                                                                                                                                                                                        4.6.2.a.1 (implement)
                                                                                                                                                                                        4.6.2.b.4 (mature = maintain?)
5.j.6; and General SW                                                                                                                                                                   4.7.2.b.1 (implement)
Engineering (1.f.1)           The project shall implement, maintain, and execute the software plan(s).                               SWE-014                                            4.8.2.a.1 (implement)

                              The project shall establish, document, and maintain at least one software cost estimate and
                              associated cost parameter(s) that satisfies the following conditions:
                              a. Covers the entire software life cycle.
                              b. Is based on selected project attributes (e.g., assessment of the size, functionality, complexity,
                              criticality, and risk of the software processes and products).                                                                                            4.3.2.c.1.i
                              c. Is based on the cost implications of the technology to be used and the required maturation of                 3.2.10.1 (C.3.1.3.a, C.3.1.4.c)          4.4.2.c.5.ii-iii,v
1.b                           that technology.                                                                                       SWE-015   Specific detail not included             4.5.2.c.5.ii-iii,v
                                 The project shall document and maintain a software schedule that satisfies the following
                                 conditions:
                                 a. Coordinates with the overall project schedule.
                                 b. Documents the interactions of milestones and deliverables between software, hardware,                                                              4.3.2.c.1.i
                                 operations, and the rest of the system.                                                                          3.2.10.1 (C.3.1.3.a, C.3.1.4.c)      4.4.2.c.5.ii
5.j.6                            c. Reflects the critical path for the software development activities.                                 SWE-016   Specific detail not included         4.5.2.c.5.ii

                                                                                                                                                                                       4.3.2.c.1.iii (assessment of workforce needs
                                                                                                                                                  3.2.10.1 (C.3.1.4.a2i, C.3.1.4.c)    versus plans)
1.l                              The project shall plan, track, and ensure project specific software training for project personnel.    SWE-017   Tracking and ensuring not included   (no specific mention of training)

                                                                                                                                                                                       4.3.2.b.2-3
                                                                                                                                                                                       4.4.2.b.6-7
                                                                                                                                                                                       4.5.2.b.12-13
                                                                                                                                                                                       4.6.2.a.11-12
                                                                                                                                                                                       4.7.2.b.9-10
General SW Engineering (1.f.1 & The project shall regularly hold reviews of software activities, status, and results with the project             5.2.1.2                              4.8.2.a.3-4
5.j.6)                          stakeholders and track issues to resolution.                                                            SWE-018   5.3.1.8                              4.9.2.a.2-3

                                                                                                                                                                                       4.3.2.b.3 (project life cycle reviews)
                                                                                                                                                                                       4.4.2.b.7 (project life cycle reviews)
                                                                                                                                                                                       4.5.2.b.13 (project life cycle reviews)
                                                                                                                                                                                       4.6.2.a.12 (project life cycle reviews)
                                                                                                                                                                                       4.7.2.b.10 (project life cycle reviews)
                                 The project shall select and document a software development life cycle or model that includes                   5.2.1.6                              4.8.2.a.4 (project life cycle reviews)
                                 phase transition criteria for each life-cycle phase (e.g., formal review milestones, informal                    5.3.1.5                              4.9.2.a.3 (project life cycle reviews)
                                 reviews, software requirements review (SRR), preliminary design review (PDR), critical design                    5.3.1.6                              (no mention of choosing a s/w development
5.j.6                            review (CDR), test readiness reviews, customer acceptance or approval reviews).                        SWE-019   5.3.1.8                              life cycle)


                                                                                                                                                                                       4.4.2.c.2 (Appendix F, Section 3.7)
                                                                                                                                                                                       4.5.2.c.1 (Appendix F, Section 3.7)
                                                                                                                                                                                       (calls for SMP to meet content required by
                                 The project shall classify each system and subsystem containing software in accordance with the                                                       NPR 7150.2; SWE-102 includes classification
5.j.1                            software classification definitions for Classes A, B, C, D, E, F, G, and H software in Appendix E.     SWE-020                                        of systems and subsystems)

                                 The project's software assurance organization shall perform an independent classification
5.c.4                            assessment.                                                                                            SWE-132


                                                                                                                                                                                       4.4.2.c.2 (Appendix F, Section 3.7)
                                                                                                                                                                                       4.5.2.c.1 (Appendix F, Section 3.7)
                                                                                                                                                                                       (calls for SMP to meet content required by
                                 The project, in conjunction with the Safety and Mission Assurance organization, shall determine                                                       NPR 7150.2 and NASA-STD-8739.8; SWE-102
5.j.1; 5.c.1                     the software safety criticality in accordance with NASA-STD-8739.8.                                    SWE-133                                        includes safety criticality)

                                 If a system or subsystem evolves to a higher software classification as defined in Appendix E, then
                                 the project shall update its plan to fulfill the added requirements per the Requirements Mapping
5.j.6                            Matrix in Appendix D.                                                                               SWE-021
                                                                                                                                                                  4.4.2.c.2 (Appendix F, Sections 3.2 & 3.7)
                                                                                                                                                                  4.5.2.c.1 (Appendix F, Sections 3.2 & 3.7)
                                                                                                                                                                  (calls for SMP to meet content required by
                                                                                                                                                                  NASA-STD-8739.8 and for SMA Plan to
                                                                                                                                                                  address s/w assurance per NASA-STD-
                                                                                                                                                                  8739.8)
                                                                                                                                                                  4.1.2.a.3 (Appendix E, Section 3.2)
                                The project shall implement software assurance per NASA-STD-8739.8, NASA Software Assurance                                       (calls for SMA Plan to address s/w assurance
5.c.1                           Standard.                                                                                   SWE-022                               per NASA-STD-8739.8)

                                                                                                                                                                  4.4.2.c.2 (Appendix F, Section 3.2)
                                                                                                                                                                  4.5.2.c.1 (Appendix F, Section 3.2)
                                                                                                                                                                  (calls for SMA Plan to address SMA
                                                                                                                                                                  disciplines including s/w safety per NASA-
                                                                                                                                                                  STD-8719.13)
                                                                                                                                                                  4.1.2.a.3 (Appendix E, Section 3.2)
                                When a project is determined to have safety-critical software, the project shall ensure that the                                  (calls for SMA Plan to address SMA
                                safety requirements of NASA-STD-8719.13, Software Safety Standard, are implemented by the                                         disciplines including s/w safety per
5.c.1; 5.j.1                    project.                                                                                           SWE-023                        NASA_STD-8719.13)

                                When a project is determined to have safety-critical software, the project shall ensure the
                                following items are implemented in the software:
                                a. Safety-critical software is initialized, at first start and at restarts, to a known safe state.
                                b. Safety-critical software safely transitions between all predefined known states.
                                c. Termination performed by software of safety critical functions is performed to a known safe
                                state.
                                d. Operator overrides of safety-critical software functions require at least two independent
                                actions by an operator.
                                e. Safety-critical software rejects commands received out of sequence, when execution of those
                                commands out of sequence can cause a hazard.
                                f. Safety-critical software detects inadvertent memory modification and recovers to a known safe
                                state.
                                g. Safety-critical software performs integrity checks on inputs and outputs to/from the software
                                system.
                                h. Safety-critical software performs prerequisite checks prior to the execution of safety-critical
                                software commands.
                                i. No single software event or action is allowed to initiate an identified hazard.
                                j. Safety-critical software responds to an off nominal condition within the time needed to prevent
                                a hazardous event.
                                k. Software provides error handling of safety-critical functions.
                                l. Safety-critical software has the capability to place the system into a safe state.
                                m. Safety-critical elements (requirements, design elements, code components, and interfaces) are
1.g                             uniquely identified as safety-critical.                                                            SWE-134

                               The project shall ensure that actual results and performance of software activities are tracked
General SW Engineering (1.f.1) against the software plans.                                                                         SWE-024   3.2.16.1 (C.3.7.4)   4.5.2.c.1 (Appendix F, Section 3.1)

                               The project shall ensure that corrective actions are taken, recorded, and managed to closure
General SW Engineering (1.f.1) when actual results and performance deviate from the software plans.                                SWE-025   3.2.16.1 (C.3.7.4)

General SW Engineering (1.f.1 & The project shall ensure that changes to commitments (e.g., software plans) are agreed to by the
5.j.6)                          affected groups and individuals.                                                                 SWE-026
                                 The project shall ensure that when a COTS, GOTS, MOTS, reused, or open source software
                                 component is to be acquired or used, the following conditions are satisfied:
                                 a. The requirements that are to be met by the software component are identified.
                                 b. The software component includes documentation to fulfill its intended purpose (e.g., usage
                                 instructions).
                                 c. Proprietary, usage, ownership, warranty, licensing rights, and transfer rights have been
                                 addressed.
                                 d. Future support for the software product is planned.
General SW Engineering           e. The software component is verified and validated to the same level of confidence as would be
(1f; 1.f.1 & 5.j.6 )             required of the developed software component.                                                       SWE-027    3.2.5.1 (C.2.1.4.c)

General SW Engineering (1.f.1 & The project shall plan software verification activities, methods, environments, and criteria for the
5.j.3)                          project.                                                                                             SWE-028    3.2.7.1                                       4.7.2.b.3 (carry out the plan)

General SW Engineering (1.f.1 & The project shall plan the software validation activities, methods, environments, and criteria for
5.j.3)                          the project.                                                                                         SWE-029    3.2.8.1                                       4.7.2.b.3 (carry out the plan)

General SW Engineering (1.f.1 & The project shall record, address, and track to closure the results of software verification
5.j.6)                          activities.                                                                                          SWE-030    3.2.7.1 (C.2.3.3.c, C.2.3.4.c-e)              4.7.2.b.3 (document results)

General SW Engineering (1.f.1&
5.j.6)                         The project shall record, address, and track to closure the results of software validation activities. SWE-031   3.2.8.1 (C.2.4.3.c, C.2.4.4.c-e)              4.7.2.b.3 (document results)


                                 The project shall ensure that software is acquired, developed, and maintained by an organization
                                 with a non-expired Capability Maturity Model Integration® for Development (CMMI-DEV) rating as
                                 measured by a Software Engineering Institute (SEI) authorized or certified lead appraiser as
                                 follows:
                                 For Class A software:
                                 CMMI-DEV Maturity Level 3 Rating or higher for software, or CMMI-DEV Capability Level 3 Rating
                                 or higher in all CMMI-DEV Maturity Level 2 and 3 process areas for software.
                                 For Class B software:
                                 CMMI-DEV Maturity Level 2 Rating or higher for software, or CMMI-DEV Capability Level 2 Rating
                                 or higher for software in the following process areas:
                                 a. Requirements Management.
                                 b. Configuration Management.
                                 c. Process and Product Quality Assurance.
                                 d. Measurement and Analysis.
                                 e. Project Planning.
                                 f. Project Monitoring and Control.
                                 g. Supplier Agreement Management (if applicable).
                                 For Class C software:
                                 The required CMMI-DEV Maturity Level for Class C software will be defined per Center or project
5.j.2                            requirements.                                                                                    SWE-032




General SW Engineering (1.f.1 &
5.j.6 )                         The project shall assess options for software acquisition versus development.                        SWE-033    3.2.4.1 (C.1.4.4.b)                           4.3.2.c.1.ii


                                                                                                                                                4.4.1 (D.3.3)
General SW Engineering (1.f.1 & The project shall define and document or record the acceptance criteria and conditions for the                  Criteria not mentioned, requires review for
5.j.6)                          software.                                                                                            SWE-034    Gov't acceptance of contracted deliverables
                                                                                                                                                4.2.5
General SW Engineering (1.f.1    For new contracts, the project shall establish a procedure for software supplier selection,                    Procedure not mentioned; only evaluation of
& 5.j.6)                         including proposal evaluation criteria.                                                              SWE-035   offeror proposals

General SW Engineering (1.f.1 & The project shall determine which software processes, activities, and tasks are required for the                                                                4.3.2.c.1.i (create WBS)
5.j.6)                          project.                                                                                              SWE-036   4.2.3 (D.4.5.2)                                 4.4.2.c.2 (create Project Plan)

                                                                                                                                                4.2.4 (D.4.5.2)
General SW Engineering (1.f.1 & The project shall define the milestones at which the software supplier(s) progress will be reviewed             Milestones not specifically named, monitoring
5.j.3)                          and audited as a part of the acquisition activities.                                                SWE-037     contractor progress is noted

General SW Engineering (1.f.1                                                                                                                                                                   4.1.2.a.3 (Appendix E, Section 3.4)
& 5.j.3)                         The project shall document software acquisition planning decisions.                                  SWE-038                                                   4.5.2.c.1 (Appendix F, Section 3.4)

                                 The project shall require the software supplier(s) to provide insight into software development
                                 and test activities; at a minimum the following activities are required: monitoring integration,
                                 review of the verification adequacy, review of trade study data and results, auditing the software             4.2.3 (D.4.5.2)
                                 development process, participation in software reviews and systems and software technical                      4.2.4
5.j.5 & 5.j.12                   interchange meetings.                                                                              SWE-039     These items not specified directly

                                 The project shall require the software supplier(s) to provide NASA with all software products and
                                 software process tracking information, in electronic format, including software development and
5.j.5 & 5.j.12                   management metrics.                                                                               SWE-040

                                 The project shall require the software supplier(s) to notify the project, in the response to the
                                 solicitation, as to whether open source software will be included in code developed for the
1.f                              project.                                                                                             SWE-041


                                 The project shall require the software supplier(s) to provide NASA with electronic access to the
                                 source code developed for the project, including MOTS software and non-flight software (e.g.,
                                 ground test software, simulations, ground analysis software, ground control software, science
5.j.5 & 5.j.12                   data processing software, and hardware manufacturing software).                                      SWE-042

                                 The project shall require the software supplier to track all software changes and non-
5.j.5 & 5.j.12                   conformances and provide the data for the project's review.                                          SWE-043

                                 The project shall require the software supplier(s) to provide software metric data as defined in
7.b                              the project's Software Metrics Report.                                                               SWE-044

                                                                                                                                                                                                4.1.2.a.3 (Appendix E, Section 3.12)
                                                                                                                                                                                                4.4.2.c.2 (Appendix F, Section 3.13)
                                                                                                                                                                                                4.5.2.c.1 (Appendix F, Section 3.13)
                                 The project shall participate in any joint NASA/contractor audits of the software development                                                                  (CM audits and how contractor CM will
5.j.8                            process and software configuration management process.                                               SWE-045                                                   integrate with program CM)

                                 The project shall require the software supplier(s) to provide a software schedule for the project's
5.j.3 & 5.j.5                    review and schedule updates as requested.                                                           SWE-046

                                 The project shall require the software supplier(s) to make available, electronically, the software
5.j.5 & 5.j.12                   traceability data for the project's review.                                                          SWE-047

                                 The project shall document in the solicitation the software processes, activities, and tasks to be
5.j.12                           performed by the supplier.                                                                           SWE-048   4.2.2 - 4.2.4
                                                                                                                                                                                                   4.4.2.b.1
1.e.1                            The project shall document the software requirements.                                               SWE-049      3.2.2.1                                          4.5.2.b.2

                                                                                                                                                                                                   4.1.2.a.5 (trace to Agency needs, goals,
                                                                                                                                                                                                   objectives)
                                                                                                                                                                                                   4.1.2.a.3 (Appendix E, Section 2.1)
                                 The project shall identify, develop, document, approve, and maintain software requirements                                                                        4.4.2.c.2 (Appendix F, Section 2.1)
1.e.1                            based on analysis of customer and other stakeholder requirements and the operational concepts. SWE-050           3.2.2.1 (3.2.2.2, C.1.2.2, C.1.2.4.a-b)          4.5.2.c.1 (Appendix F, Section 2.1)

                                 The project shall perform software requirements analysis based on flowed-down and derived
                                 requirements from the top-level systems engineering requirements and the hardware
1.e.1                            specifications and design.                                                                          SWE-051      3.2.3.1 (C.1.3.4.a)


                                 The project shall perform, document, and maintain bidirectional traceability between the                                                                          4.1.2.a.5 (trace to Agency needs, goals,
1.e.1                            software requirement and the higher-level requirement.                                              SWE-052      3.2.3.1 (C.1.3.4.d)                              objectives; bidirectional not mentioned)

1.e.1                            The project shall collect and manage changes to the software requirements.                          SWE-053      3.2.3.1 ( C.1.3.4.e)

                                                                                                                                                  3.2.3.1 (C.1.3.4.c)
                                 The project shall identify, initiate corrective actions, and track until closure inconsistencies among           Project plans and software products not
1.e.1                            requirements, project plans, and software products.                                                    SWE-054   specifically called out


                                 The project shall perform requirements validation to ensure that the software will perform as                    3.2.4.1 (C.1.4.3.f)
1.e.1                            intended in the customer environment.                                                               SWE-055      Requirements validation not specifically named

General SW Engineering (1.f.1 &
5.j.6 )                         The project shall document and maintain the software design.                                         SWE-056      3.2.4.1                                          4.5.2.b.3

General SW Engineering (1.f.1 & The project shall transform the allocated and derived requirements into a documented software
5.j.6 )                         architectural design.                                                                                SWE-057      3.2.4.1 (C.1.4.4.d)

                                The project shall develop, record, and maintain a detailed design based on the software
General SW Engineering (1.f.1 & architectural design that describes the lower-level units so that they can be coded, compiled, and
5.j.6 )                         tested.                                                                                            SWE-058        3.2.4.1 (C1.4.4.d)                               4.6.2.a.2

                                                                                                                                                                                                   4.6.2.a.2
                                 The project shall perform and maintain bidirectional traceability between the software                                                                            (requires compliance with NPR 7123.1 which
1.e.1                            requirements and the software design.                                                               SWE-059      3.2.4.1 (C.1.4.4.e)                              requires traceability)

5.j.6                            The project shall implement the software design into software code.                                 SWE-060      3.2.5.1

General SW Engineering (1.f.1 & The project shall ensure that software coding methods, standards, and/or criteria are adhered to
5.j.6 )                         and verified.                                                                                    SWE-061          3.2.5.1 (C.2.1.4.d.2)

General SW Engineering (1.f.1 & The project shall ensure that results from static analysis tool(s) are used in verifying and validating
5.j.6 )                         software code.                                                                                          SWE-135

General SW Engineering (1.f.1 &
5.j.6 )                         The project shall ensure that the software code is unit tested per the plans for software testing.   SWE-062

General SW Engineering (1.f.1 &
5.j.12 )                        The project shall provide a Software Version Description document for each software release.         SWE-063
General SW Engineering (1.f.1 & The project shall provide and maintain bidirectional traceability from software design to the
5.j.6 )                         software code.                                                                                      SWE-064

General SW Engineering (1.f.1 &
5.j.6 )                         The project shall validate and accredit software tool(s) required to develop or maintain software. SWE-0136

                                The project shall establish and maintain:
                                a. Software Test Plan(s).
General SW Engineering (1.f.1 & b. Software Test Procedure(s).
5.j.3 )                         c. Software Test Report(s).                                                                         SWE-065

General SW Engineering (1.f.1 &                                                                                                               3.2.7.1 (C.2.3.2.c -verification, c.2.4.2.c -
5.j.6 )                         The project shall perform software testing as defined in the Software Test Plan.                    SWE-066   validation)

General SW Engineering (1.f.1 & The project shall ensure that the implementation of each software requirement is verified to the
5.j.6 )                         requirement.                                                                                        SWE-067   3.2.7.1 (C.2.3.4.b)                             4.7.2.b.3 (carry out the V&V plan)

                                                                                                                                                                                              4.7.2.b.3
                                                                                                                                                                                              (requires compliance with NPR 7123.1 which
General SW Engineering (1.f.1 &                                                                                                                                                               requires results analysis and documentation
5.j.6 )                         The project shall evaluate test results and document the evaluation.                                SWE-068   3.2.7.1 (C.2.3.4.c-e)                           )

General SW Engineering (1.f.1 &
5.j.6 )                         The project shall document defects identified during testing and track to closure.                  SWE-069   3.2.7.1 (C.2.3.4.d-e)                           4.7.2.b.4

                                                                                                                                                                                              4.6.2.a.3 (where engineering models and
General SW Engineering (1.f.1 & The project shall verify, validate, and accredit software models, simulations, and analysis tools                                                             test beds can be considered s/w models,
5.j.6 )                         required to perform qualification of flight software or flight equipment.                           SWE-070                                                   sims and analysis tools)

General SW Engineering (1.f.1 & The project shall update Software Test Plan(s) and Software Test Procedure(s) to be consistent
5.j.6 )                         with software requirements.                                                                         SWE-071

                                 The project shall provide and maintain bidirectional traceability from the Software Test
1.e.1                            Procedures to the software requirements.                                                           SWE-072   3.2.7.1 (C.2.3.4.d)

General SW Engineering (1.f.1 & The project shall ensure that the software system is validated on the targeted platform or high-
5.j.6 )                         fidelity simulation.                                                                                SWE-073   3.2.8.1 (C.2.4.4.b)                             4.7.2.b.3 (carry out the V&V plan)

General SW Engineering (1.f.1 & The project shall document the software maintenance plans in a Software Maintenance Plan
5.j.6 )                         document.                                                                                           SWE-074                                                   4.7.2.b.11 (no specific mention of plan)

                                                                                                                                                                                              4.1.2.a.3 (Appendix E, Section 3.8)
                                                                                                                                                                                              4.4.2.c.2 (Appendix F, Section 3.9)
                                                                                                                                                                                              4.5.2.c.1 (Appendix F, Section 3.9)
                                                                                                                                                                                              4.7.2.b.11
General SW Engineering (1.f.1 &                                                                                                                                                               4.8.2.a.2
5.j.3)                          The project shall plan software operations, maintenance, and retirement activities.                 SWE-075                                                   (no mention of retirement)

General SW Engineering (1.f.1 & The project shall implement software operations, maintenance, and retirement activities as
5.j.6 )                         defined in the respective plans.                                                                    SWE-076                                                   4.8.2.a.2

                                                                                                                                                                                              4.6.2.a.9
General SW Engineering (1.f.1 & The project shall complete and deliver the software product to the customer with appropriate                                                                  4.7.2.b.7
5.j.6 )                         documentation to support the operations and maintenance phase of the software's life cycle.         SWE-077   3.2.9.1                                         (no mention of s/w delivery)
                                                                                                                                                                              4.6.2.a.9 (Operations Handbook)
                                                                                                                                                                              4.7.2.b.6 (Operations Handbook)
General SW Engineering (1.f.1 & The project shall deliver to the customer the as-built documentation to support the operations                                                4.7.2.b.7
5.j.6 )                         and maintenance phase of the software life cycle.                                                SWE-078     3.2.9.1 (C.2.5.2.a, C.2.5.3.a)   (no mention of delivery)

                                The project shall develop a Software Configuration Management Plan that describes the                                                         4.1.2.a.3 (Appendix E, Section 3.12)
General SW Engineering (1.f.1 & functions, responsibilities, and authority for the implementation of software configuration                                                   4.4.2.c.2 (Appendix F, Section 3.13)
5.j.3)                          management for the project.                                                                      SWE-079     3.2.14.1                         4.5.2.c.1 (Appendix F, Section 3.13)

                                                                                                                                                                              4.1.2.a.3 (Appendix E, Section 3.12)
                                                                                                                                                                              4.4.2.c.2 (Appendix F, Section 3.13)
                                                                                                                                                                              4.5.2.c.1 (Appendix F, Section 3.13)
                                                                                                                                                                              (calls for consistency with NPR 7123.1 which
General SW Engineering (1.f.1 &                                                                                                                                               calls out recording and evaluating of
5.j.6 )                         The project shall track and evaluate changes to software products.                               SWE-080     3.2.14.1 (C.3.5.4.c)             changes)

                                                                                                                                                                              4.1.2.a.3 (Appendix E, Section 3.12)
                                                                                                                                                                              4.4.2.c.2 (Appendix F, Section 3.13)
                                                                                                                                                                              4.5.2.c.1 (Appendix F, Section 3.13)
                                                                                                                                                                              (calls for consistency with NPR 7123.1 which
General SW Engineering (1.f.1 & The project shall identify the software configuration items (e.g., software documents, code, data,                                            calls for identifying items under
5.j.6 )                         tools, models, scripts) and their versions to be controlled for the project.                       SWE-081   3.2.14.1 (C.3.5.4.a-b)           configuration control)

                                                                                                                                                                              4.1.2.a.3 (Appendix E, Section 3.12)
                                The project shall establish and implement procedures designating the levels of control each                                                   4.4.2.c.2 (Appendix F, Section 3.13)
                                identified configuration item must pass through; the persons or groups with authority to                                                      4.5.2.c.1 (Appendix F, Section 3.13)
                                authorize changes and to make changes at each level; and the steps to be followed to request                                                  (calls for consistency with NPR 7123.1 which
General SW Engineering (1.f.1 & authorization for changes, process change requests, track changes, distribute changes, and                                                    calls for criteria, procedures,
5.j.6 )                         maintain past versions.                                                                          SWE-082     3.2.14.1 (C.3.5.4.c)             responsibilities, approvals, etc.)

                                                                                                                                                                              4.1.2.a.3 (Appendix E, Section 3.12)
                                                                                                                                                                              4.4.2.c.2 (Appendix F, Section 3.13)
                                                                                                                                                                              4.5.2.c.1 (Appendix F, Section 3.13)
                                                                                                                                                                              (calls for consistency with NPR 7123.1 which
General SW Engineering (1.f.1 &                                                                                                                                               calls for maintaining item status
5.j.6 )                         The project shall prepare and maintain records of the configuration status of configuration items. SWE-083   3.2.14.1 (C.3.5.4.d)             information)

                                                                                                                                                                              4.1.2.a.3 (Appendix E, Section 3.12)
                                                                                                                                                                              4.4.2.c.2 (Appendix F, Section 3.13)
                                The project shall ensure that software configuration audits are performed to determine the                                                    4.5.2.c.1 (Appendix F, Section 3.13)
General SW Engineering (1.f.1 & correct version of the configuration items and verify that they conform to the documents that                                                 (calls for consistency with NPR 7123.1 which
5.j.6 )                         define them.                                                                                     SWE-084     3.2.14.1 (C.3.5.4.e)             calls for configuration audits)

General SW Engineering (1.f.1 & The project shall establish and implement procedures for the storage, handling, delivery, release,
5.j.6 )                         and maintenance of deliverable software products.                                                  SWE-085




                                                                                                                                                                              4.5.2.b.8
                                The project shall identify, analyze, plan, track, control, communicate, and document software                                                 4.1.2.a.3 (Appendix E, Section 3.3, 3.4.d)
1.c                             risks in accordance with NPR 8000.4, Agency Risk Management Procedural Requirements.             SWE-086     3.2.13.1                         4.4.2.c.2 (Appendix F, Section 3.3, 3.4.d)
                                The project shall perform and report on software peer reviews/inspections for:
                                a. Software requirements.
                                b. Software Test Plan.
                                c. Any design items that the project identified for software peer review/inspections according to
General SW Engineering (1.f.1 & the software development plans.                                                                                 3.2.16.1 (C.3.7.4)
5.j.6 )                         d. Software code as defined in the software and or project plans.                                     SWE-087   No specific work products are named   4.6.2.a.7

                                The project shall perform and report on software peer reviews/inspections for:
                                a. Software Development or Management Plan.
                                b. Software Configuration Management Plan.
                                c. Software Maintenance Plan.
General SW Engineering (1.f.1 & d. Software Assurance Plan.                                                                                     3.2.16.1 (C.3.7.4)
5.j.6 )                         e. Software Safety Plan.                                                                              SWE-137   No specific work products are named   4.6.2.a.7

                                The project shall, for each planned software peer review/inspections:
                                a. Use a checklist to evaluate the work products.
                                b. Use established readiness and completion criteria.
General SW Engineering (1.f.1 & c. Track actions identified in the reviews until they are resolved.
5.j.6 )                         d. Identify required participants.                                                                    SWE-088   3.2.16.1 (C.3.7.4.d)


7.b                             The project shall, for each planned software peer review/inspection, record basic measurements. SWE-089         3.2.16.1 (C.3.7.4.e)


7.b                             The project shall establish and document specific measurement objectives for their project.           SWE-090   3.2.16.1


                                The project shall select and record the selection of specific measures in the following areas:
                                a. Software progress tracking.
                                b. Software functionality.
                                c. Software quality.
                                d. Software requirements volatility.
7.b                             e. Software characteristics.                                                                          SWE-091   3.2.16.1 (C.3.7.4.b-c)

                                The project shall specify and record data collection and storage procedures for their selected
7.b                             software measures and collect and store measures accordingly.                                         SWE-092

                                The project shall analyze software measurement data collected using documented project-
7.b                             specified and Center/organizational analysis procedures.                                              SWE-093

                                The project shall report measurement analysis results periodically and allow access to
7.b                             measurement information by Center-defined organizational measurement programs.                        SWE-094

                                Each NASA Mission Directorate shall establish its own software measurement system to include
7.b & 5.f.2                     the minimum reporting requirements in SWE-091.                                                        SWE-095


                                Each NASA Mission Directorate shall identify and document the specific measurement objectives,
7.b & 5.f.2                     the chosen specific measures, the collection procedures, and storage and analysis procedures.  SWE-096

                                The NASA Headquarters' Office of the Chief Engineer shall maintain an Agency-wide process asset
5.b.9; 5.b.13; & 5.b.16         library of applicable best practices.                                                           SWE-098

                                Each Center shall review the contents of the process asset library to identify those practices that
5.h.1                           may have direct applicability and value to its software activities.                                   SWE-099
                                The NASA Headquarters' Office of the Chief Engineer and Center training organizations shall
1.l, 5.b.8, & 5.h.5             provide and fund training to advance software engineering practices and software acquisition.      SWE-100

                                Each Center shall maintain and implement Software Training Plan(s) to advance its in-house
1.l & 5.h.5                     software engineering capability and as a reference for its contractors.                            SWE-101

                                The Software Development or Management Plan shall contain:
                                a. Project organizational structure showing authority and responsibility of each organizational
                                unit, including external organizations (e.g., Safety and Mission Assurance, Independent
                                Verification and Validation (IV&V), Technical Authority, NASA Engineering and Safety Center,
                                NASA Safety Center).
                                b. The safety criticality and classification of each of the systems and subsystems containing
                                software.
                                c. Tailoring compliance matrix for approval by the designated Engineering Technical Authority, if
                                the project has any waivers or deviations to this NPR.
                                d. Engineering environment (for development, operation, or maintenance, as applicable),
                                including test environment, library, equipment, facilities, standards, procedures, and tools.
                                e. Work breakdown structure of the life-cycle processes and activities, including the software
                                products, software services, non-deliverable items to be performed, budgets, staffing, acquisition
                                approach, physical resources, software size, and schedules associated with the tasks.
                                f. Management of the quality characteristics of the software products or services.
                                g. Management of safety, security, privacy, and other critical requirements of the software
                                products or services.
                                h. Subcontractor management, including subcontractor selection and involvement between the
                                subcontractor and the acquirer, if any.
                                i. Verification and validation.
                                j. Acquirer involvement.
                                k. User involvement.
                                l. Risk management.
                                m. Security policy.
                                n. Approval required by such means as regulations, required certifications, proprietary, usage,
General SW Engineering (1.f.1 & ownership, warranty, and licensing rights.                                                                     3.2.6.1 (integration process)
5.j.3)                          o. Process for scheduling, tracking, and reporting.                                                SWE-102     6.2.6                           4.5.2.c.1 (Project Plan)
                                p. Training of personnel, including project unique software training needs.
                                The Software Configuration Management Plan shall contain:
                                a. The project organization(s).
                                b. Responsibilities of the software configuration management organization.
                                c. References to the software configuration management policies and directives that apply to the
                                project.
                                d. All functions and tasks required to manage the configuration of the software, including
                                configuration identification, configuration control, status accounting, and configuration audits and
                                reviews.
                                e. Schedule information, which establishes the sequence and coordination for the identified
                                activities and for all events affecting the plan's implementation.
                                f. Resource information, which identifies the software tools, techniques, and equipment
                                necessary for the implementation of the activities.
                                g. Plan maintenance information, which identifies the activities and responsibilities necessary to
General SW Engineering (1.f.1 & ensure continued planning during the life cycle of the project.                                                                                4.1.2.a.3 (Appendix E, Section 3.12)
5.j.3)                          h. Release management and delivery.                                                                  SWE-103   3.2.14.1 (C.3.5.4)              4.5.2.c.1 (Appendix F, Section 3.13)
                                The Software Test Plan shall include:
                                a. Test levels (separate test effort that has its own documentation and resources, e.g.,
                                component, integration, and system testing).
                                b. Test types:
                                (1) Unit testing.
                                (2) Software integration testing.
                                (3) Systems integration testing.
                                (4) End-to-end testing.
                                (5) Acceptance testing.
                                (6) Regression testing.
                                c. Test classes (designated grouping of test cases).
                                d. General test conditions.
                                e. Test progression.
                                f. Data recording, reduction, and analysis.
                                g. Test coverage (breadth and depth) or other methods for ensuring sufficiency of testing.
                                h. Planned tests, including items and their identifiers.
                                i. Test schedules.
General SW Engineering (1.f.1 & j. Requirements traceability (or verification matrix).                                                         3.2.7.1
5.j.3)                          k. Qualification testing environment, site, personnel, and participating organizations.            SWE-104     3.2.8.1

                                The Software Maintenance Plan shall include:
                                a. Plan information for the following activities:
                                (1) Maintenance process implementation.
                                (2) Problem and modification analysis.
                                (3) Modification implementation.
                                (4) Maintenance review/acceptance.
                                (5) Migration.
                                (6) Software Retirement.
                                (7) Software Assurance.
                                (8) Software Risk Assessment for all changes made during maintenance and operations.
                                b. Specific standards, methods, tools, actions, procedures, and responsibilities associated with the
                                maintenance process. In addition, the following elements are included:
                                (1) Development and tracking of required upgrade intervals, including implementation plan.
                                (2) Approach for the scheduling, implementation, and tracking of software upgrades.
                                (3) Equipment and laboratories required for software verification and implementation.
                                (4) Updates to documentation for modified software components.
                                (5) Licensing agreements for software components.
                                (6) Plan for and tracking of operational backup software (e.g., backup flight software, backup to
                                the primary operational software).
                                (7) Approach for the implementation of modifications to operational software (e.g., testing of
                                software in development laboratory prior to operational use).                                                            4.1.2.a.3 (Appendix E, Section 3.10; Logistics
                                (8) Approach for software delivery process, including distribution to facilities and users of the                        Plan includes maintenance)
                                software products and installation of the software in the target environment (including, but not                         4.5.2.c.1 (Appendix F, Section 3.11; Logistics
                                limited to, spacecraft, simulators, Mission Control Center, and ground operations facilities).                           Plan includes maintenance)
General SW Engineering (1.f.1 & (9) Approach for providing NASA access to the software version description data (e.g., revision                          4.7.2.b.11 (systems maintenance as part of
5.j.3)                          number, licensing agreement).                                                                        SWE-105             the Logistics Plan)

General SW Engineering (1.f.1,   The Software Assurance Plan(s) shall be developed and documented per NASA-STD-8739.8, NASA                              4.1.2.a.3 (Appendix E, Section 3.2)
5.j.4, & 5.c)                    Software Assurance Standard.                                                               SWE-106                      4.5.2.c.1 (Appendix F, Section 3.2)
              The Center Software Training Plan shall include:
              a. Responsibilities.
              b. Implementation.
              c. Records and forms.
              d. Training resources.
              e. Minimum training requirements for software personnel.
5.h.5 & 1.l   f. Training class availabilities.                                                                 SWE-107

              The Center Software Engineering Improvement Plans shall include:
              a. Process improvement goal(s).
              b. Scope of process improvement.
              c. All Center organizations responsible for the performance of mission-critical software
              development, management, and acquisition.
              d. The Center's tactic for phasing in improvements (e.g., domain phasing and organizational
              phasing).
              e. Ownership of Center Software Engineering Improvement Plan.
              f. The Center's tactic for monitoring Center Software Engineering Improvement Plan progress,
              including responsibilities.
              g. Strategies and objectives.
              h. The Center's tactic for supporting the implementation of all strategies of the NASA Software
              Engineering Initiative Implementation Plan.
              i. Schedule.
              j. The Center's tactic or approach for phasing in new and upgraded NASA Headquarters
5.h.5         requirements.                                                                                     SWE-108

                                                                                                                                               4.1.2.a.3 (Appendix E, Section 3.2)
                                                                                                                                               4.4.2.c.2 (Appendix F, Section 3.2)
5.c.1         The Software Safety Plan(s) shall be developed per NASA-STD-8719.13, Software Safety Standard. SWE-138                           4.5.2.c.1 (Appendix F, Section 3.2)
              The Software Requirements Specification shall contain:
              a. System overview.
              b. CSCI requirements:
              (1) Functional requirements.
              (2) Required states and modes.
              (3) External interface requirements.
              (4) Internal interface requirements.
              (5) Internal data requirements.
              (6) Adaptation requirements (data used to adapt a program to a given installation site or to given
              conditions in its operational environment).
              (7) Safety requirements.
              (8) Performance and timing requirements.
              (9) Security and privacy requirements.
              (10) Environment requirements.
              (11) Computer resource requirements:
              (a) Computer hardware resource requirements, including utilization requirements.
              (b) Computer software requirements.
              (c) Computer communications requirements.
              (12) Software quality characteristics.
              (13) Design and implementation constraints.
              (14) Personnel-related requirements.
              (15) Training-related requirements.
              (16) Logistics-related requirements.
              (17) Packaging requirements.
              (18) Precedence and criticality of requirements.
              c. Qualification provisions (e.g., demonstration, test, analysis, inspection).
              d. Bidirectional requirements traceability.
1.e.1         e. Requirements partitioning for phased delivery.                                                  SWE-109   3.2.2.1 (C.1.2.4)
                                The Software Data Dictionary shall include:
                                a. Channelization data (e.g., bus mapping, vehicle wiring mapping, hardware channelization).
                                b. Input/Output (I/O) variables.
                                c. Rate group data.
                                d. Raw and calibrated sensor data.
                                e. Telemetry format/layout and data.
                                f. Data recorder format/layout and data.
                                g. Command definition (e.g., onboard, ground, test specific).
General SW Engineering (1.f.1 & h. Effecter command information.
5.j.6)                          i. Operational limits (e.g., maximum/minimum values, launch commit criteria information).            SWE-110


                                The Software Design Description shall include:
                                a. CSCI-wide design decisions/trade decisions.
                                b. CSCI architectural design.
                                c. CSCI decomposition and interrelationship between components:
                                (1) CSCI components:
                                (a) Description of how the software item satisfies the software requirements, including
                                algorithms, data structures, and functional decomposition.
                                (b) Software item I/O description.
                                (c) Static/architectural relationship of the software units.
                                (d) Concept of execution, including data flow, control flow, and timing.
                                (e) Requirements, design and code traceability.
                                (f) CSCI's planned utilization of computer hardware resources.
                                (2) Rationale for software item design decisions/trade decisions including assumptions,
General SW Engineering (1.f.1 & limitations, safety and reliability related items/concerns or constraints in design documentation.
5.j.6)                          (3) Interface design.                                                                                SWE-111

                                The Interface Design Description shall include:
                                a. Priority assigned to the interface by the interfacing entity(ies).
                                b. Type of interface (e.g., real-time data transfer, storage-and-retrieval of data) to be
                                implemented.
                                c. Specification of individual data elements (e.g., format and data content, including bit-level
                                descriptions of data interface) that the interfacing entity(ies) will provide, store, send, access, and
                                receive.
                                d. Specification of individual data element assemblies (e.g., records, arrays, files, reports) that the
                                interfacing entity(ies) will provide, store, send, access, and receive.
                                e. Specification of communication methods that the interfacing entity(ies) will use for the
                                interface.
                                f. Specification of protocols the interfacing entity(ies) will use for the interface.
                                g. Other specifications, such as physical compatibility of the interfacing entity(ies).
                                h. Traceability from each interfacing entity to the system or CSCI requirements addressed by the
                                entity's interface design, and traceability from each system or CSCI requirement to the interfacing
                                entities that address it.
General SW Engineering (1.f.1 & i. Interface compatibility.
5.j.6)                          j. Safety-related interface specifications and design features.                                         SWE-112
                                The Software Change Request/Problem Report shall contain:
                                a. Identification of the software item.
                                b. Description of the problem or change to enable problem resolution or justification for and the
                                nature of the change, including: assumptions/ constraints and change to correct software error.
                                c. Originator of Software Change Request/Problem Report and originator's assessment of
                                priority/severity.
                                d. Description of the corrective action taken to resolve the reported problem or analysis and
                                evaluation of the change or problem, changed software configuration item, schedules, cost,
                                products, or test.
                                e. Life-cycle phase in which problem was discovered or in which change was requested.
                                f. Approval or disapproval of Software Change Request/Problem Report.
                                g. Verification of the implementation and release of modified system.
                                h. Date problem discovered.
                                i. Status of problem.
                                j. Identify any safety-related aspects/considerations/ impacts associated with the proposed
                                change and/or identified problem.
                                k. Configuration of system and software when problem is identified (e.g., system/software
General SW Engineering (1.f.1 & configuration identifier or list of components and their versions).
5.j.6)                          l. Any workaround to the problem that can be used while a change is being developed or tested.       SWE-113

                                The Software Test Procedures shall contain:
                                a. Test preparations, including hardware and software.
                                b. Test descriptions, including:
                                (1) Test identifier.
                                (2) System or CSCI requirements addressed by the test case.
                                (3) Prerequisite conditions.
                                (4) Test input.
                                (5) Instructions for conducting procedure.
                                (6) Expected test results, including assumptions and constraints.
                                (7) Criteria for evaluating results.
General SW Engineering (1.f.1 & c. Requirements traceability.
5.j.6)                          d. Identification of test configuration.                                                             SWE-114




                                The Software User Manual shall contain:
                                a. Software summary, including: application, inventory, environment, organization, overview of
                                operation, contingencies, alternate states, and modes of operation, security, privacy, assistance,
                                and problem reporting.
                                b. Access to the software: first-time user of the software, initiating a session, and stopping and
                                suspending work.
                                c. Processing reference guide: capabilities, conventions, processing procedures, related
                                processing, data back up, recovery from errors, malfunctions, emergencies, and messages.
                                d. Assumptions, limitations, and safety-related items/concerns or constraints.
General SW Engineering (1.f.1 & e. Information that is unique or specific for each version of the software (e.g., new and modified
5.j.6)                          features, new and modified interfaces).                                                              SWE-115
                                The Software Version Description shall identify and provide:
                                a. Full identification of the system and software (e.g., numbers, titles, abbreviations, version
                                numbers, and release numbers).
                                b. Executable software (e.g., batch files, command files, data files, or other software needed to
                                install the software on its target computer).
                                c. Software life-cycle data that defines the software product.
                                d. Archive and release data.
                                e. Instructions for building the executable software, including, for example, the instructions and
                                data for compiling and linking and the procedures used for software recovery, software
                                regeneration, testing, or modification.
                                f. Data integrity checks for the executable object code and source code.
                                g. Software product files (any files needed to install, build, operate, and maintain the software).
                                h. Open change requests and or problem reports, including any workarounds.
General SW Engineering (1.f.1 & i. Change requests and/or problem reports implemented in the current software version since the
5.j.6)                          last Software Version Description was published.                                                    SWE-116

                                The Software Metrics Report shall contain as a minimum the following information tracked on a
                                CSCI basis:
                                a. Software progress tracking measures.
                                b. Software functionality measures.
                                c. Software quality measures.
                                d. Software requirement volatility.
7.b                             e. Software characteristics.                                                                       SWE-117

                                The Software Test Report shall include:
                                a. Overview of the test results:
                                (1) Overall evaluation of the software as shown by the test results.
                                (2) Remaining deficiencies, limitations, or constraints detected by testing (e.g., including
                                description of the impact on software and system performance, the impact a correction would
                                have on software and system design, and recommendations for correcting the deficiency,
                                limitation, or constraint).
                                (3) Impact of test environment.
                                b. Detailed test results:
                                (1) Project-unique identifier of a test and test procedure(s).
                                (2) Summary of test results (e.g., including requirements verified).
                                (3) Problems encountered.
                                (4) Deviations from test cases/procedures.
                                c. Test log:
                                (1) Date(s), time(s), and location(s) of tests performed.
                                (2) Test environment, hardware, and software configurations used for each test.
                                (3) Date and time of each test-related activity, the identity of the individual(s) who performed the
General SW Engineering (1.f.1 & activity, and the identities of witnesses, as applicable.
5.j.6)                          d. Rationale for decisions.                                                                          SWE-118
                                The Software Peer Review/Inspection Report shall include:
                                a. Identification information (including item being reviewed/inspected, review/inspection type
                                (e.g., requirements inspection, code inspection, etc.) and review/inspection time and date).
                                b. Summary on total time expended on each software peer review/inspection (including total
                                hour summary and time participants spent reviewing/inspecting the product individually).
                                c. Participant information (including total number of participants and participant's area of
                                expertise).
                                d. Total number of defects found (including the total number of major defects, total number of
                                minor defects, and the number of defects in each type such as accuracy, consistency,
                                completeness).
General SW Engineering (1.f.1 & e. Peer review/inspection results summary (i.e., pass, re-inspection required).
5.j.6)                          f. Listing of all review/inspection defects.                                                       SWE-119

                                For those cases in which a Center or project desires a general exclusion from requirement(s) in
                                this NPR or desires to generically apply specific alternate requirements that do not meet or
                                exceed the requirements of this NPR, the requester shall submit a waiver for those exclusions or
                                alternate requirements for approval by the NASA Headquarters' Chief Engineer with appropriate
1.k.1 &5.b.21                   justification.                                                                                     SWE-120

                                Where approved, the requesting Center or project shall document the approved alternate
                                requirement in the procedure controlling the development, acquisition, and/ or deployment of
1.k.1                           the affected software.                                                                             SWE-121

                                The designated Engineering Technical Authority(s) for requirements in this NPR, which can be
1.k.1 & 5.h.10                  waived at the Center level, shall be approved by the Center Director.                              SWE-122

                                The designated Center Engineering Technical Authority(s) for this NPR shall comply with NASA
                                Headquarters' Office of the Chief Engineer's direction on roles and responsibilities for Engineering
1.k.1 & 5.h.10                  Technical Authority.                                                                                 SWE-124


                                Each project with software components shall maintain a compliance matrix against requirements
1.k & 5.j.8                     in this NPR, including those delegated to other parties or accomplished by contract vehicles. SWE-125


                                The Engineering Technical Authority(s) for this NPR shall consider the following information when
                                assessing waivers and deviations from requirements in this NPR:
                                a. The NASA software inventory data on the project.
                                b. The classification of systems and subsystems containing software, as defined in Appendix E.
                                c. Applicable Center-level software directives that meet the intent of this NPR.
                                d. Applicable contractor and subcontractor software policies and procedures that meet the intent
                                of this NPR.
                                e. Potential impacts to NASA missions.
1.k.1, 5.b.21 & 5.h.11          f. Potential impacts to health, medical concerns, or safety.                                      SWE-126

                                Centers and projects shall fully comply with the "shall" statements in this NPR that are marked
5.h.2, 5.j.6 & 5.j.1            with an "X" in Appendix D consistent with their software classification.                           SWE-139


                                The NASA Headquarters' Office of the Chief Engineer shall review and have concurrence approval
                                when a Center defines subsets of requirements denoted by "P (Center)" in the Requirements
7.a, 1.k.4, 5.b.12 & 5.b.11     Mapping Matrix in Appendix D for the indicated classes of software.                            SWE-127
                 The Center-level Engineering Technical Authority shall keep records of projects' compliance
1.k.1 & 5.h.10   matrices, waivers, and deviations against this NPR.                                               SWE-128


                 The NASA Headquarters' Office of the Chief Engineer shall authorize appraisals against selected
                 requirements in this NPR (including NASA Headquarters' Office of the Chief Engineer approved
1.k.4 & 5.b.11   subsets and alternative sets of requirements) to check compliance.                                SWE-129
NPR 7123.1A requirements                                                                           ID

The OCE, under the authority of this SE NPR, shall ensure compliance with this SE NPR.             2.1.1.2

For programs and projects involving more than one Center, the lead organization shall develop
documentation to describe the hierarchy and reconciliation of Center plans implementing this
NPR.                                                                                               2.1.1.3

For systems that contain software, the technical team shall ensure that software developed
within NASA or acquired complies with NPD 2820.1, NASA Software Policy, and NPR 7150.2, NASA
Software Engineering Requirements.                                                           2.1.1.4


The OCE shall be the clearinghouse for systems engineering policies to ensure compatibility
across NASA. In the event of differences between program or project offices and the OCE staff,
the conflict will ultimately reach the NASA Chief Engineer or mission director level.              2.1.1.5

Center Directors shall perform the following activities or delegate them to the appropriate Center
organization:
a. Develop the SE NPR Implementation Plan per the template in Appendix H-1 describing how the
requirements of this SE NPR will be applied to the programs and projects under their cognizance
or authority.                                                                                      2.1.2.2a


Center Directors shall perform the following activities or delegate them to the appropriate Center
organization:
b. Establish policies, procedures, and processes to execute the requirements of this SE NPR.       2.1.2.2.b

Center Directors shall perform the following activities or delegate them to the appropriate Center
organization:
c. Assess and take corrective actions to improve the execution of the requirements of this SE
NPR.                                                                                               2.1.2.2.c


Center Directors shall perform the following activities or delegate them to the appropriate Center
organization:
d. Perform the SE NPR Center Survey in accordance with Appendix H-2 for the purpose of
providing feedback on the SE NPR. The initial Center Survey will be submitted five months from
the effective date of this SE NPR. Subsequent updates will be upon the request of the OCE, no
earlier than nine months after the initial submission. The Center Survey will use the common
survey tool in Appendix H-2 and will be submitted through the Center System Engineering
Working Group (SEWG) representative.                                                               2.1.2.2d
Center Directors shall perform the following activities or delegate them to the appropriate Center
organization:
e. Select appropriate standards applicable to projects under their control.                        2.1.2.2.e

Each technical team shall execute the Center processes intended to implement this SE NPR under
the oversight of the Center Directors in accordance with the SEMP.                             2.1.3

The Center Directors shall submit their SE NPR Implementation Plan to the OCE within three
months after the effective date of this NPR.                                                       2.2.1.2


The Center Directors shall develop and document in the SE NPR Implementation Plan how the
particular Center will assess compliance to the SE NPR and provide regular updates to the OCE.     2.2.1.3

The appropriate DGA shall have responsibility to approve or disapprove any SE NPR requirement
that is either tailored or waived.                                                            2.3.1.1

The assigned technical teams shall define in the project SEMP how the required 17 common
technical processes, as implemented by Center documentation, will be applied to the various
levels of project WBS model system structure during each applicable life-cycle phase and have
their approach approved by the DGA.                                                                3.1.3

The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for the definition of stakeholder expectations for
the applicable WBS model.                                                                          3.2.1.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for definition of the technical requirements from
the set of agreed upon stakeholder expectations for the applicable WBS model.                      3.2.2.1

The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for logical decomposition of the validated
technical requirements of the applicable WBS model.                                                3.2.3.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for designing product solution definitions within
the applicable WBS model that satisfy the derived technical requirements.                          3.2.4.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for implementation of a design solution definition
by making, buying, or reusing an end product of the applicable WBS model.                       3.2.5.1
The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation for the integration of lower level products into an
end product of the applicable WBS model in accordance with its design solution definition.        3.2.6.1

The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for verification of end products generated by the
product implementation process or product integration process against their design solution
definitions.                                                                                      3.2.7.1

The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for validation of end products generated by the
product implementation process or product integration process against their stakeholder
expectations.                                                                                     3.2.8.1

The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for transitioning end products to the next higher
level WBS-model customer or user.                                                                 3.2.9.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for planning the technical effort.                   3.2.10.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for management of requirements defined and
baselined during the application of the system design processes.                                  3.2.11.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for management of the interfaces defined and
generated during the application of the system design processes.                                  3.2.12.1

The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for management of the technical risk identified
during the technical effort.                                                                      3.2.13.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for configuration management.                        3.2.14.1

The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for management of the technical data generated
and used in the technical effort.                                                                 3.2.15.1
The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for making assessments of the progress of planned
technical effort and progress toward requirements satisfaction.                                 3.2.16.1


The Center Directors or designees shall establish and maintain a process to include activities,
requirements, guidelines, and documentation, for making technical decisions.                       3.2.17.1

The assigned NASA technical team shall prepare a SEMP that covers the periods before contract
award, during contract performance, and upon contract completion in accordance with content
contained in the annotated outline in Appendix D.                                                  4.2.1

The assigned technical team shall use common technical processes, as implemented by the
Center's documentation, to establish the technical inputs to the Request for Proposal (RFP)
appropriate for the product to be developed, including product requirements and Statement of
Work tasks.                                                                                        4.2.2


The technical team shall determine the technical work products to be delivered by the offeror or
contractor, to include a contractor SEMP that specifies their systems engineering approach for
requirements development; technical solution definition; design realization; product evaluation;
product transition; and technical planning, control, assessment, and decision analysis.          4.2.3

The technical team shall provide to the contracting officer, for inclusion in the RFP, the
requirements for technical oversight activities planned in the NASA SEMP. [4.2.4]                  4.2.4

The technical team shall participate in the evaluation of offeror proposals following applicable
NASA and Center source selection procedures.                                                       4.2.5

The assigned technical team, under the authority of the cognizant contracting officer, shall
perform the technical oversight activities established in the NASA SEMP.                           4.3.1

The assigned technical team shall participate in scheduled milestone reviews to finalize
Government acceptance of the deliverables.                                                         4.4.1

The assigned technical team shall participate in product transition to the customer and/or
disposal as defined in the NASA SEMP.                                                              4.4.2

Technical teams shall monitor technical effort through periodic technical reviews.                 5.2.1.2


The technical team shall ensure that system aspects represented or implemented in software are
included in all technical reviews to demonstrate that project technical goals and progress are
being achieved and that all NPR 7150.2 software review requirements are implemented.           5.2.1.6
The technical team shall develop and document plans for technical reviews for use in the project
planning process. The technical review schedule, as documented in the SEMP, will be reflected in
the overall project plan described in NPR 7120.5.                                                5.2.2

The technical team shall address the entrance and success criteria listed in Appendix G for
applicability to the respective reviews.                                                           5.3.1.2

The technical team shall execute the required Program/System Requirements Review (P/SRR) and
Program Approval Review (PAR) in accordance with the review entry and success criteria defined
in tables G-1 and G-2 of Appendix G.                                                           5.3.1.3

The technical team shall execute the required program technical reviews in accordance with the
following timeline: P/SRR before KDP 0 and PAR before KDP 1.                                       5.3.1.4




For human FS&GS projects, the technical team shall execute the following required minimum set
of technical reviews in accordance with the review entry and success criteria defined in tables G-
3, G-4, G-6, G-7, G-8, and G-10 through G-18 of Appendix G: Mission Concept Review (MCR),
System Requirements Review (SRR), System Definition Review (SDR), Preliminary Design Review
(PDR), Critical Design Review (CDR), System Integration Review (SIR), Test Readiness Review
(TRR), System Acceptance Review (SAR), Operational Readiness Review (ORR), Flight Readiness
Review (FRR), Post-Launch Assessment Review (PLAR), Critical Event Readiness Review (CERR),
Post-Flight Assessment Review (PFAR), and Decommissioning Review (DR).                             5.3.1.5


For robotic FS&GS projects, the technical team shall execute and document the following
minimum required technical reviews: the MCR, SRR, Mission Definition Review (MDR), PDR, CDR,
SIR, TRR, ORR, FRR, PLAR, CERR, and DR in accordance with the review entry and success criteria
given in tables G-3, G-4, G-5, G-7, G-8, G-10, G-11, G-13 through G-16, and G-18 of Appendix G.
Robotic projects can combine the SRR and MDR based on size and level of risk.                   5.3.1.6


The technical team shall also execute a Production Readiness Review (PRR) as an additional
technical review for both human and robotic FS&GS projects developing or acquiring multiple or
similar systems greater than three (or as determined by the project) in accordance with the
review entry and success criteria defined in Table G-9 of Appendix G.                              5.3.1.7
The technical team shall execute the required FS&GS project technical reviews in accordance with
the following timelines:
a. MCR prior to KDP A.
b. Human FS&GS project SRR prior to SDR and robotic missions SRR and MDR prior to KDP B.
c. Human FS&GS project SDR prior to KDP B.
d. PDR prior to KDP C.
e. CDR prior to starting fabrication of system end products and SIR.
f. PRR prior to starting fabrication of system end products for projects requiring multiple units.
g. SIR prior to KDP D.
h. TRR prior to starting product verification and product validation testing.
i. Human FS&GS project SAR after completion of KDP D.
j. ORR after SAR or KDP D and before FRR.
k. FRR prior to KDP E.
l. PLAR after system end product launch.
m. CERR after PLAR and before KDP F.
n. Human FS&GS project PFAR at end of flight and before KDP F.
o. DR after KDP F.                                                                                 5.3.1.8

The assigned technical team shall accomplish the monitoring function for flight-related ATD
projects using appropriately defined and conducted periodic technical reviews (PTRs) and
continuation reviews (CRs).                                                                        5.3.1.9


The assigned technical team shall accomplish the monitoring function for IPs using PTR and SAR.    5.3.1.10


Working with the program/project manager, the technical team shall determine the appropriate
level within the system structure at which SEMPs are developed, taking into account factors such
as number and complexity of interfaces, operating environments, and risk factors.                6.2.1

The technical team shall baseline the SEMP per the Center?s Implementation Plan incorporating
the content of Appendix D, Systems Engineering Management Plan, prior to completion of Phase
A in the program life cycle or the equivalent milestone.                                      6.2.2

The DGA shall review and approve or disapprove the SEMP at each major milestone review or its
equivalent.                                                                                   6.2.3


The assigned technical team shall establish the initial SEMP early in the Formulation phase and
update it as necessary to reflect changes in scope or improved technical development.              6.2.4

The technical team shall ensure that any technical plans and discipline plans describe how the
technical activities covered in the plans are consistent with the SEMP and are accomplished as
fully integrated parts of the technical effort.                                                    6.2.5
The technical team shall ensure that the project's software development/management plan
describes how the software activities are consistent with the SEMP and are accomplished as fully
integrated parts of the technical effort.                                                        6.2.6
Mapped to 7150.2 Requirement?




Yes
Yes




Yes




Yes




Yes
Yes




Yes




Yes




Yes




Yes




Yes




Yes
Yes




Yes




Yes


Yes


Yes




Yes




Yes




Yes
Yes




Yes
Yes
Yes
NPR 7120.5D (7120-81) requirements                                                                 ID

Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(1) Plan, prepare for, and support the Acquisition Strategy Meeting (ASM) prior to partnership
commitments and obtain the ASM minutes.                                                            4.1.2.a.1


Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(2) Support the MDAA in developing and obtaining approval of the FAD, PCA, and appropriate
annual budget submissions.                                                                         4.1.2.a.2




Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(3) Prepare and obtain approval of the Program Plan that follows the template in Appendix E.
(See Table 4-2 for a list of required Program Plan Control Plans and their required maturity.)     4.1.2.a.3




Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(4) Support the MDAA and the NASA HQ Office of External Relations in obtaining approved inter-
agency and international agreements (including the planning and negotiation of agreements and
recommendations on joint participation in reviews, integration and test, and risk management). 4.1.2.a.4


Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(5) Document the traceability of program requirements on individual projects to Agency needs,
goals, and objectives, as described in the NASA Strategic Plan.                                    4.1.2.a.5




Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(6) Initiate the development of technologies that cut across multiple projects within the program. 4.1.2.a.6
Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(7) Prior to the program life cycle formulation reviews shown in Figure 2-3, conduct internal
reviews in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                           4.1.2.a.7




Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(8) Plan, prepare for, and support the program life cycle formulation reviews shown in Figure 2-3
in accordance with NPR 7123.1, Center practices, and the requirements of this document.           4.1.2.a.8


Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(9) If required by the DA, obtain KDP 0 readiness products as shown in Table 4-1.                   4.1.2.a.9


Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(10) If required by the DA, plan, prepare for, and support the governing PMC review prior to KDP
0.                                                                                               4.1.2.a.10


Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(11) Obtain KDP I readiness products as shown in Table 4-1.                                         4.1.2.a.11


Requirements: During program formulation, the program manager and the program team shall:
a. For all programs—
(12) Plan, prepare for, and support the governing PMC review prior to KDP I.                        4.1.2.a.12




Requirements: During program formulation, the program manager and the program team shall:
b. For single-project and tightly coupled programs, implement the requirements in paragraphs
4.3.2 and 4.4.2 (Pre-Phase A and Phase A) with the following stipulations:
(1) In single-project programs, the Project Plan may serve as the Program Plan and KDP 0 (if
required by the DA) and KDP I serve in lieu of KDP A and KDP B, respectively. In keeping with this,
single-project programs are approved for implementation at KDP II. (At the discretion of the
MDAA, there may also be a Project Plan separate from the Program Plan. In either case, all
content required in Program and Project Plan templates must be included.)                           4.1.2.b.1
Requirements: During program formulation, the program manager and the program team shall:
b. For single-project and tightly coupled programs, implement the requirements in paragraphs
4.3.2 and 4.4.2 (Pre-Phase A and Phase A) with the following stipulations:
(2) In tightly coupled programs, separate Project Plans are prepared for projects during their
formulation. The program manager may allocate portions of the Program Plan to these individual
Project Plans.                                                                                 4.1.2.b.2

During program implementation, the program manager and the program team shall:
a. For all programs—
(1) Execute the Program Plan.                                                                       4.2.2.a.1

During program implementation, the program manager and the program team shall:
a. For all programs—
(2) Support the MDAA in updating the PCA, as appropriate.                                           4.2.2.a.2

During program implementation, the program manager and the program team shall:
a. For all programs—
(3) Update the Program Plan at KDP II and other KDPs, as appropriate. See Table 4-2 for a list of
required Program Plan Control Plans and their required maturity.                                    4.2.2.a.3

During program implementation, the program manager and the program team shall:
a. For all programs—
(4) Support the MDAA and the NASA HQ Office of External Relations in obtaining updated inter-
agency and international agreements (including the planning and negotiation of updated
agreements and recommendations on joint participation in reviews, integration and test, and risk
management).                                                                                     4.2.2.a.4

During program implementation, the program manager and the program team shall:
a. For all programs—
(5) Conduct planning, program-level systems engineering, and integration, as appropriate, to
support the MDAA in initiating the project selection process.                                       4.2.2.a.5

During program implementation, the program manager and the program team shall:
a. For all programs—
(6) Support the MDAA in the selection of projects, either assigned or through a competitive
process.                                                                                            4.2.2.a.6

During program implementation, the program manager and the program team shall:
a. For all programs—
(7) Approve project FADs and Project Plans.                                                         4.2.2.a.7

During program implementation, the program manager and the program team shall:
a. For all programs—
(8) Prior to the program life cycle implementation reviews shown in Figure 2-3, conduct internal
reviews in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                           4.2.2.a.8
During program implementation, the program manager and the program team shall:
a. For all programs—
(9) Plan, prepare for, and support the program life cycle implementation reviews shown in Figure
2-3 in accordance with NPR 7123.1, Center practices, and the requirements of this document.      4.2.2.a.9

During program implementation, the program manager and the program team shall:
a. For all programs—
(10) Maintain programmatic and technical oversight of the projects within the program and
report their status periodically.                                                                4.2.2.a.10

During program implementation, the program manager and the program team shall:
a. For all programs—
(11) Review and approve annual project budget submission inputs and prepare annual program
budget submissions.                                                                              4.2.2.a.11


During program implementation, the program manager and the program team shall:
a. For all programs—
(12) Continue to develop technologies that cut across multiple projects within the program.      4.2.2.a.12

During program implementation, the program manager and the program team shall:
a. For all programs—
(13) Obtain KDP readiness products as shown in Table 4-1.                                        4.2.2.a.1.3

During program implementation, the program manager and the program team shall:
a. For all programs—
(14) Conduct program-level completion activities for each project in accordance with the project
life cycle for Phase F (see paragraph 4.9.2).                                                    4.2.2.a.14

During program implementation, the program manager and the program team shall:
b. For single-project programs—
(1) For KDP II, implement the requirements in paragraph 4.5.2 (Phase B).                         4.2.2.b.1

During program implementation, the program manager and the program team shall:
b. For single-project programs—
(2) For KDP III, implement the requirements of paragraph 4.6.2 (Phase C).                        4.2.2.b.2

During program implementation, the program manager and the program team shall:
b. For single-project programs—
(3) For KDP IV, implement the requirements of paragraph 4.7.2 (Phase D).                         4.2.2.b.3

During program implementation, the program manager and the program team shall:
b. For single-project programs—
(4) For KDP V, implement the requirements of paragraph 4.8.2 (Phase E).                          4.2.2.b.4
During program implementation, the program manager and the program team shall:
c. For tightly coupled programs—
(1) For KDP II, implement the requirements in paragraph 4.5.2 (Phase B) in the manner
documented in the Program Plan (except those requirements allocated to specific projects and
documented in their Project Plans).                                                                 4.2.2.c.1

During program implementation, the program manager and the program team shall:
c. For tightly coupled programs—
(2) For KDP III, implement the requirements in paragraph 4.6.2 (Phase C) in the manner
documented in the Program Plan (except those requirements allocated to specific projects and
documented in their Project Plans).                                                                 4.2.2.c.2

During program implementation, the program manager and the program team shall:
c. For tightly coupled programs—
(3) For KDP IV, implement the requirements of paragraph 4.7.2 (Phase D) in the manner
documented in the Program Plan (except those requirements allocated to specific projects and
documented in their Project Plans).                                                                 4.2.2.c.3

During program implementation, the program manager and the program team shall:
c. For tightly coupled programs—
(4) For KDP V, implement the requirements of paragraph 4.8.2 (Phase E) in the manner
documented in the Program Plan (except those requirements allocated to specific projects and
documented in their Project Plans).                                                                 4.2.2.c.4

During Pre-Phase A, the pre-project manager and team shall:
a. Support Headquarters and program activities, in particular —
(1) Obtain an approved project FAD.                                                                 4.3.2.a.1

During Pre-Phase A, the pre-project manager and team shall:
a. Support Headquarters and program activities, in particular —
(2) Support the program manager and the MDAA in the development of the draft program
requirements on the project.                                                                        4.3.2.a.2

During Pre-Phase A, the pre-project manager and team shall:
b. Perform technical activities—
(1) Develop and document preliminary mission concept(s).                                            4.3.2.b.1

During Pre-Phase A, the pre-project manager and team shall:
b. Perform technical activities—
(2) Prior to the project independent life cycle reviews shown in Figure 2-4 for this phase, conduct
internal reviews in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                           4.3.2.b.2
During Pre-Phase A, the pre-project manager and team shall:
b. Perform technical activities—
(3) Plan, prepare for, and support the project independent life cycle reviews shown in Figure 2-4
for this phase in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                            4.3.2.b.3

During Pre-Phase A, the pre-project manager and team shall:
c. Perform project planning, costing, and scheduling activities—
(1) Develop and document a draft Management Baseline for all work to be performed by the
project that includes the following:
(i) A high-level Work Breakdown Structure (WBS) consistent with the NASA standard space flight
project WBS (Appendix G), a schedule, and a rough-order-of-magnitude cost estimate and cost
range. Document the basis for the cost estimate and range.                                           4.3.2.c.1.i

During Pre-Phase A, the pre-project manager and team shall:
c. Perform project planning, costing, and scheduling activities—
(1) Develop and document a draft Management Baseline for all work to be performed by the
project that includes the following:
(ii) An assessment of potential technology needs versus current and planned technology
readiness levels, as well as potential opportunities to use commercial, academic, and other
Government agency sources of technology.                                                             4.3.2.c.1.ii

During Pre-Phase A, the pre-project manager and team shall:
c. Perform project planning, costing, and scheduling activities—
(1) Develop and document a draft Management Baseline for all work to be performed by the
project that includes the following:
(iii)An assessment of potential infrastructure and workforce needs versus current plans, as well as
opportunities to use infrastructure and workforce in other government agencies, industry,
academia, and international organizations.                                                          4.3.2.c.1.iii

During Pre-Phase A, the pre-project manager and team shall:
c. Perform project planning, costing, and scheduling activities—
(1) Develop and document a draft Management Baseline for all work to be performed by the
project that includes the following:
(iv) Identification of potential partnerships.                                                       4.3.2.c.1.iv


During Pre-Phase A, the pre-project manager and team shall:
c. Perform project planning, costing, and scheduling activities—
(1) Develop and document a draft Management Baseline for all work to be performed by the
project that includes the following:
(v) Identification of conceptual acquisition strategies for proposed major procurements.             4.3.2.c.1.v

During Pre-Phase A, the pre-project manager and team shall:
d. Conduct KDP readiness activities—
(1) Obtain KDP readiness products as shown in Table 4-3.                                             4.3.2.d.1
During Pre-Phase A, the pre-project manager and team shall:
d. Conduct KDP readiness activities—
(2) Plan, prepare for, and support the governing PMC review prior to KDP A.                      4.3.2.d.2

During Phase A, the project manager and project team shall:
a. Support Headquarters- and program-related activities—
(1) Support the program manager and the MDAA in the development of the baseline program
requirements on the project.                                                                     4.4.2.a.1

During Phase A, the project manager and project team shall:
a. Support Headquarters- and program-related activities—
(2) Plan, prepare for, and support the Acquisition Strategy Meeting (ASM) prior to partnership
agreements and obtain the ASM minutes.                                                           4.4.2.a.2

During Phase A, the project manager and project team shall:
a. Support Headquarters- and program-related activities—
(3) Support the program manager, the MDAA, and the NASA HQ Office of External Relations in
initiating inter-agency and international agreements (including the planning and negotiation of
agreements and recommendations on joint participation in reviews, integration and test, and risk
management).                                                                                     4.4.2.a.3

During Phase A, the project manager and project team shall:
b. Perform technical activities—
(1) Develop preliminary system-level (and lower level, as needed) requirements.                  4.4.2.b.1

During Phase A, the project manager and project team shall:
b. Perform technical activities—
(2) Develop and document a baseline mission concept (including key risk drivers and mitigation
options and mission descope options).                                                            4.4.2.b.2

During Phase A, the project manager and project team shall:
b. Perform technical activities—
(3) Develop a preliminary mission operations concept.                                            4.4.2.b.3

During Phase A, the project manager and project team shall:
b. Perform technical activities—
(4) Initiate technology developments, as required.                                               4.4.2.b.4

During Phase A, the project manager and project team shall:
b. Perform technical activities—
5) Develop an initial orbital debris assessment in accordance with NPR 8715.6, NASA Procedural
Requirements for Limiting Orbital Debris using the format and requirements contained in NASA-
STD-8719.14, Process for Limiting Orbital Debris.                                                4.4.2.b.5
During Phase A, the project manager and project team shall:
b. Perform technical activities—
(6) Prior to the project independent life cycle reviews shown in Figure 2-4 for this phase, conduct
internal reviews in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                           4.4.2.b.6

During Phase A, the project manager and project team shall:
b. Perform technical activities—
(7) Plan, prepare for, and support the project independent life cycle reviews shown in Figure 2-4
for this phase in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                           4.4.2.b.7

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(1) As early as practical, prepare and finalize Phase A work agreements.                            4.4.2.c.1

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(2) Prepare a preliminary Project Plan that follows the template in Appendix F.
See Table 4-4 for a list of the Control Plans and their required maturity by phase.                 4.4.2.c.2

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(3) For contracts requiring Earned Value Management (EVM) (refer to the NASA FAR
Supplement), conduct required Integrated Baseline Reviews (IBRs).                                   4.4.2.c.3


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(4) For all flight projects, provide a draft Cost Analysis Data Requirement (CADRe) (Parts A, B, C)
consistent with the NASA Cost Estimating Handbook (CEH) 60 days prior to the KDP B milestone
with a final version 30 days after the KDP event to reflect any decisions from the KDP. This CADRe
is based on the SDR/PNAR Management Baseline.                                                       4.4.2.c.4


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop and document a preliminary Management Baseline for all work to be performed by
the project, noting the following:
(i) The project’s preliminary Management Baseline is consistent with the NASA standard space
flight project WBS (see Appendix G) and has an associated WBS dictionary.                           4.4.2.c.5.i
During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop and document a preliminary Management Baseline for all work to be performed by
the project, noting the following:
ii) The project’s preliminary Management Baseline includes a preliminary integrated master
schedule, preliminary life cycle cost estimate, workforce estimates, and the project’s technical
baseline/mission concept, all consistent with the program requirements levied on the project.         4.4.2.c.5.ii

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop and document a preliminary Management Baseline for all work to be performed by
the project, noting the following:
(iii) The preliminary life cycle cost estimate is based on the project’s technical baseline/mission
concept and preliminary integrated master schedule.                                                   4.4.2.c.5.iii


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop and document a preliminary Management Baseline for all work to be performed by
the project, noting the following:
(iv) The preliminary life cycle cost estimate uses the latest accounting guidance and practices.      4.4.2.c.5.iv

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop and document a preliminary Management Baseline for all work to be performed by
the project, noting the following:
(v) The preliminary life cycle cost estimate including UFE, along with confidence level and a cost
and risk analysis.                                                                                    4.4.2.c.5.v

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop and document a preliminary Management Baseline for all work to be performed by
the project, noting the following:
(vi) The preliminary life cycle cost estimate is time-phased by Government Fiscal Year (GFY) to
WBS Level 2.                                                                                          4.4.2.c.5.vi


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(6) Complete a preliminary business case analysis for infrastructure for each proposed project
real property infrastructure investment consistent with NPD 8820.2, Design and Construction of
Facilities and NPR 8820.2, Facility Project Requirements, and for the acquisition of new aircraft
consistent with NPR 7900.3, NASA Aircraft Operations Management.                                      4.4.2.c.6
During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(7) Work with the appropriate NASA Headquarters offices to initiate thedevelopment of
MOUs/MOAs with external partners, as needed.                                                       4.4.2.c.7


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(8) Obtain a planetary protection certification for the mission (if required) in accordance with
NPD 8020.7, Biological Contamination Control for Outbound and Inbound Planetary Spacecraft,
and NPR 8020.12, Planetary Protection Provisions for Robotic Extraterrestrial Missions.            4.4.2.c.8


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(9) Develop a Nuclear Safety Launch Approval Plan (for missions with nuclear materials) in
accordance with NPR 8715.3, NASA General Safety Program Requirements.                              4.4.2.c.9

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(10) Prepare and finalize work agreements for Phase B.                                             4.4.2.c.10

During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(11) Prepare for approval by the program manager a list of long-lead procurements that need to
be procured in Phase B.                                                                            4.4.2.c.11


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(12) In accordance with NPR 2190.1, NASA Export Control Program, support the appropriate
NASA export control officials to identify and assess export-controlled technical data that
potentially will be provided to foreign partners and the approval requirements for release of that
data, all as a part of developing the project’s Export Control Plan.                               4.4.2.c.12


During Phase A, the project manager and project team shall:
c. Perform project planning, costing, and scheduling activities—
(13) In coordination with the OCFO and in accordance with NPR 9250.1, Property, Plant, and
Equipment and Operating Materials and Supplies complete the Alternative Future Use
Questionnaire (Form NF 1739), Section A, to determine the appropriate accounting treatment of
capital assets. Once completed, forward the questionnaire to the OCFO, Property Branch.       4.4.2.c.13

During Phase A, the project manager and project team shall:
d. Conduct KDP readiness activities—
(1) Obtain KDP readiness products as shown in Table 4-3.                                           4.4.2.d.1
During Phase A, the project manager and project team shall:
d. Conduct KDP readiness activities—
(2) Plan, prepare for, and support the governing PMC review prior to KDP B.                      4.4.2.d.2

During Phase B, the project manager and the project team shall:
a. Support Headquarters- and program-related activities:
(1) Obtain an update to the baseline program requirements on the project.                        4.5.2.a.1

During Phase B, the project manager and the project team shall:
a. Support Headquarters- and program-related activities:
(2) Complete the environmental planning process as explained in NPR 8580.1, Implementing the
National Environmental Policy Act, and Executive Order 12114.                                4.5.2.a.2


During Phase B, the project manager and the project team shall:
a. Support Headquarters- and program-related activities:
(3) In coordination with the program manager, the MDAA, and the NASA HQ Office of External
Relations, support the development of external agreements, such as inter-agency and
international agreements (including the planning and negotiation of agreements and
recommendations on joint participation in reviews, integration and test, and risk management).   4.5.2.a.3

During Phase B, the project manager and the project team shall:
a. Support Headquarters- and program-related activities:
(4) Coordinate with the Space Operations Mission Directorate (SOMD) if the project involves
space transportation services, space communication and
navigation capabilities, or launch services, in compliance with NPD 8610.7, Launch Services Risk
Mitigation Policy for NASA-Owned and/or NASASponsored Payloads/Missions, and NPD 8610.12,
Office of Space Operations (OSO) Space Transportation Services for NASA and NASA-Sponsored
Payloads.                                                                                        4.5.2.a.4

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(1) Implement the preliminary Project Plan.                                                      4.5.2.b.1

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(2) Baseline the system-level requirements and develop the subsystem and lowerlevel technical
requirements leading to the PDR baseline.                                                        4.5.2.b.2

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(3) Develop a set of system and associated subsystem preliminary designs, including interface
definitions, and document this work in a preliminary design report.                              4.5.2.b.3
During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(4) As part of baselining the interface control documents, document compliance with NPD
7120.4, NASA Engineering and Program/Project Management Policy, and/or obtain any necessary
waivers or deviations.                                                                      4.5.2.b.4

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(5) Develop and document a baseline mission operations concept.                                    4.5.2.b.5


During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(6) Complete development of mission-critical or enabling technology, as needed, with
demonstrated evidence of required technology qualification (i.e., component and/or breadboard
validation in the relevant environment) or execute off-ramps (i.e., substitution of more mature or
proven technologies) and document this work in a technology readiness assessment report.           4.5.2.b.6


During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(7) Plan and execute long-lead procurements in accordance with the Acquisition Plan.               4.5.2.b.7

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(8) Identify any risk drivers (and proposed mitigation plans for each risk).                       4.5.2.b.8

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(9) Develop a list of descope options.                                                             4.5.2.b.9

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(10) Develop a preliminary orbital debris assessment in accordance with NPR 8715.6, NASA
Procedural Requirements for Limiting Orbital Debris using the format and requirements
contained in NASA–STD-8719.14, Process for Limiting Orbital Debris.                                4.5.2.b.10

During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(11) Develop and document a preliminary Missile System Pre-Launch Safety Package (MSPSP) in
accordance with NPR 8715.7, Expendable Launch
Vehicle Payload Safety Program and Air Force Space Command Manual 91- 710, Range Safety
User Requirements Manual Volume 3 - Launch Vehicles, Payloads, and Ground Support Systems
Requirements.                                                                                      4.5.2.b.11
During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(12) Prior to the project life cycle reviews shown in Figure 2-4 for this phase, conduct internal
reviews in accordance with NPR 7123.1, Center practices, and the requirements of this NID.           4.5.2.b.12


During Phase B, the project manager and the project team shall:
b. Perform technical activities:
(13) Plan, prepare for, and support the project life cycle reviews shown in Figure 2-4 for this
phase in accordance with NPR 7123.1, Center practices, and the requirements of this document. 4.5.2.b.13


During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(1) Complete and obtain approval of the Project Plan that follows the template in Appendix F. See
Table 4-4 for a list of the Control Plans and their required maturity by phase.                   4.5.2.c.1


During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(2) For contracts requiring EVM (refer to the NASA FAR Supplement), conduct required IBRs.           4.5.2.c.2

During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(3) For all flight projects, provide a draft CADRe (Parts A, B, and C) consistent with the NASA Cost
Estimating Handbook 60 days prior to KDP C with a
final version 30 days after the event to reflect any changes from the KDP. This CADRe is based on
the PDR baseline.                                                                                    4.5.2.c.3

During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(4) Prepare and finalize Phase C and D work agreements.                                              4.5.2.c.4

During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop, document, and maintain a project Management Baseline for all work performed by
the project noting the following:
(i) The project’s Management Baseline is consistent with the NASA standard space flight project
WBS (see Appendix G) and has an associated WBS dictionary.                                           4.5.2.c.5.i
During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop, document, and maintain a project Management Baseline for all work performed by
the project noting the following:
(ii) The project’s Management Baseline includes the integrated master schedule, baseline life
cycle cost estimate, workforce estimates, and the
PDR-technical baseline, all consistent with the program requirements levied on the project. For
KDP C project baselines are to be based on a
joint cost and schedule confidence level consistent with the program confidence level approved
by the decision authority.                                                                           4.5.2.c.5.ii

During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop, document, and maintain a project Management Baseline for all work performed by
the project noting the following:
(iii)The baseline life cycle cost estimate is based on the PDR-technical baseline and integrated
master schedule and is expected to include a review of the entire scope of work with a series of
in-depth assessments of selected critical work elements of the WBS prior to and following the
project’s PDR/NAR preceding KDP C.                                                                   4.5.2.c.5.iii


During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop, document, and maintain a project Management Baseline for all work performed by
the project noting the following:
(iv) The baseline life cycle cost estimate uses the latest accounting guidance and practices.        4.5.2.c.5.iv

During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop, document, and maintain a project Management Baseline for all work performed by
the project noting the following:
(v) The baseline life cycle cost estimate including UFE, along with the level of confidence estimate
provided by a joint cost and schedule confidence level.                                              4.5.2.c.5.v

During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(5) Develop, document, and maintain a project Management Baseline for all work performed by
the project noting the following:
(vi) The baseline life cycle cost estimate is time-phased by Government Fiscal Year (GFY) to WBS
Level 2.                                                                                             4.5.2.c.5.vi


During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(6) When an Independent Cost Estimate is required or performed, explain any significant
differences with the project’s baseline life cycle independent cost estimate (ICE).                  4.5.2.c.6
During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(7) Complete a business case analysis for infrastructure for each of the project’s proposed real
property infrastructure investments consistent with NPD 8820.2, Design and Construction of
Facilities, and NPR 8820.2, Facility Project Requirements, and for the acquisition of new aircraft
consistent with NPR 7900.3, Aircraft Operations Management.                                          4.5.2.c.7


During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(8) Develop a baseline planetary protection plan (if required) in accordance with NPD 8020.7,
Biological Contamination Control for Outbound and Inbound Planetary Spacecraft, and NPR
8020.12, Planetary Protection Provisions for Robotic Extraterrestrial Missions.                      4.5.2.c.8

During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(9) Develop a preliminary Range Safety Risk Management Plan in accordance with NPR 8715.5,
Range Safety Program.                                                                                4.5.2.c.9


During Phase B, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities—
(10) In coordination with the OCFO, complete the Alternative Future Use Questionnaire (Form NF
1739), Section B, to identify the acquisition components of the project and to determine the
appropriate accounting treatment of the capital acquisitions within the project. Once completed,
forward the questionnaire to the OCFO, Property Branch.                                          4.5.2.c.10

During Phase B, the project manager and the project team shall:
d. Conduct KDP readiness activities:
(1) Obtain KDP readiness products as shown in Table 4-3.                                             4.5.2.d.1

During Phase B, the project manager and the project team shall:
d. Conduct KDP readiness activities:
(2) Plan, prepare for, and support the governing PMC review prior to KDP C.                          4.5.2.d.2

During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(1) Implement the baseline Project Plan.                                                             4.6.2.a.1


During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(2) Complete all requisite flight and ground designs/analyses through their respective CDRs in
accordance with NPR 7123.1 and document this work in detailed design report(s).                      4.6.2.a.2
During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(3) Develop and test all requisite engineering models (brass boards, breadboards, full-up models)
sufficiently prior to lower level CDRs to enable test results to affect detailed designs.         4.6.2.a.3

During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(4) Develop requisite system and subsystem test beds needed for qualification and acceptance
testing of flight articles.                                                                         4.6.2.a.4

During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(5) Following the appropriate lower level CDR, initiate fabrication/procurement of flight article
components, assemblies, and/or subsystems.                                                          4.6.2.a.5

During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(6) Initiate the qualification and acceptance testing of flight article components, assemblies,
and/or subsystems.                                                                                  4.6.2.a.6

During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(7) Hold peer reviews, as appropriate, prior to major project reviews in accordance with the
Project Review Plan.                                                                                4.6.2.a.7

During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(8) Develop a baseline orbital debris assessment a minimum of 45 days prior to the project CDR
in accordance with NPR 8715.6, NASA Procedural Requirements for Limiting Orbital Debris using
the format and requirements contained in NASA–STD-8719.14, Process for Limiting Orbital
Debris.                                                                                             4.6.2.a.8


During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(9) Develop a preliminary Operations Handbook that will be used to support the operations team. 4.6.2.a.9


During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(10) Develop and document a baseline Missile System Pre-Launch Safety Package (MSPSP) by the
project-level CDR in accordance with NPR 8715.7, Expendable Launch Vehicle Payload Safety
Program, and Air Force Space Command Manual 91-710, Range Safety User Requirements
Manual Volume 3 - Launch Vehicles, Payloads, and Ground Support Systems Requirements.        4.6.2.a.10
During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(11) Prior to the project independent life cycle reviews shown in Figure 2-4 for this phase,
conduct internal reviews in accordance with NPR 7123.1, Center practices, and the requirements
of this document.                                                                              4.6.2.a.11

During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(12) Plan, prepare for, and support the project independent life cycle reviews shown in Figure 2-4
for this phase in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                          4.6.2.a.12


During Phase C, the project manager and the project team shall:
a. Perform technical activities:
(13) Following the SIR and/or PRR (unless otherwise directed by the program manager), initiate
system assembly and integration and test activities even if KDP D has not occurred.                 4.6.2.a.13

During Phase C, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(1) Provide a draft CADRe (Parts A, B, and C) consistent with the NASA Cost Estimating Handbook
60 days prior to KDP D with a final version 30 days after the event to reflect any changes from the
KDP. This CADRe is based on the CDR baseline.                                                       4.6.2.b.1

During Phase C, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(2) Update work agreements for Phase D.                                                             4.6.2.b.2

During Phase C, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(3) Maintain the Management Baseline under configuration management with traceability to the
KDP C-approved baseline.                                                                     4.6.2.b.3

During Phase C, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(4) Mature preliminary Project Plan Control Plans, as required by Table 4-4.                        4.6.2.b.4

During Phase C, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(5) Develop a baseline Range Safety Risk Management Plan in accordance with NPR 8715.5,
Range Safety Program.                                                                               4.6.2.b.5

During Phase C, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(6) Develop a preliminary End of Mission Plan per NPR 8715.6.                                       4.6.2.b.6
During Phase C, the project manager and the project team shall:
c. Implement project cost and schedule control activities:
(1) Implement Earned Value Management (EVM) as documented in the Project Plan.                        4.6.2.c.1


During Phase C, the project manager and the project team shall:
c. Implement project cost and schedule control activities:
(2) For contracts requiring EVM (refer to the NASA FAR Supplement), conduct required IBRs.            4.6.2.c.2


During Phase C, the project manager and the project team shall:
c. Implement project cost and schedule control activities:
(3) Provide immediate written notice and a recovery plan to the program manager and the MDAA
if the latest Phase C through D Estimate at Completion (EAC) of the project exceeds by 15 percent
or more the KDP C-approved Management Baseline cost for Phases C through D.                       4.6.2.c.3

During Phase C, the project manager and the project team shall:
c. Implement project cost and schedule control activities:
(4) Provide immediate written notice and a recovery plan to the program manager and the MDAA
if a milestone listed for Phases C and D on the project life cycle chart (Figure 2-4) is estimated to
be delayed in excess of six months from the date scheduled in the KDP C-approved Management
Baseline.                                                                                             4.6.2.c.4


During Phase C, the project manager and the project team shall:
c. Implement project cost and schedule control activities:
(5) If the trigger points in (2) or (3) above are breached and upon written notice from the
program manager, update the Project Plan per direction received from the program manager.             4.6.2.c.5

During Phase C, the project manager and the project team shall:
d. Conduct KDP readiness activities:
(1) Obtain KDP readiness products as shown in Table 4-3.                                              4.6.2.d.1

During Phase C, the project manager and the project team shall:
d. Conduct KDP readiness activities:
(2) Plan, prepare for, and support the governing PMC review prior to KDP D.                           4.6.2.d.2

During Phase D, the project manager and the project team shall:
a. Support Headquarters- and program-related activities:
(1) Develop a Mishap Contingency Plan in accordance with NPR 8621.1, Mishap and Close Call
Reporting, Investigating, and Recordkeeping.                                                          4.7.2.a.1

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(1) Implement the Project Plan.                                                                       4.7.2.b.1
During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(2) Initiate system assembly, integration, and test.                                                4.7.2.b.2

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(3) As required by NPR 7123.1, execute and document the results of the project’s multi-tiered
Verification and Validation (V&V) Plan.                                                             4.7.2.b.3

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(4) Resolve all test, analysis, and inspection discrepancies.                                       4.7.2.b.4

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(5) Integrate payload/launch vehicle and test.                                                      4.7.2.b.5

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(6) Prepare “as-built” and “as-deployed” hardware and software documentation, including “close-
out” photographs.                                                                               4.7.2.b.6

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(7) Complete all operational support and other enabling developments (e.g., facilities,
equipment, and updated databases), including a baseline Operations Handbook to support the
operations team.                                                                                    4.7.2.b.7


During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(8) Conduct operational tests and training, including normal and anomalous scenarios.               4.7.2.b.8

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(9) Prior to the project independent life cycle reviews shown in Figure 2-4 for this phase, conduct
internal reviews in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                           4.7.2.b.9

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(10) Plan, prepare for, and support the project independent life cycle reviews shown in Figure 2-4
for this phase in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                          4.7.2.b.10
During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(11) Establish and maintain an integrated logistics support (ILS) capability, including spares,
ground support equipment, and system maintenance and operating procedures, in accordance
with the project’s Logistics Plan.                                                                 4.7.2.b.11

During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(12) Forty-five (45) days prior to delivery of the spacecraft to the launch facility, update the
Missile System Pre-Launch Safety Package (MSPSP) in
accordance with NPR 8715.7, Expendable Launch Vehicle Payload Safety Program, and Air Force
Space Command Manual 91-710, Range Safety User Requirements Manual Volume 3 - Launch
Vehicles, Payloads, and Ground Support Systems Requirements. Launch and perform system
checkout.                                                                                          4.7.2.b.12


During Phase D, the project manager and the project team shall:
b. Perform technical activities:
(13) Develop a final orbital debris assessment and a pre-launch End-of-Mission Plan a minimum
of 30 days prior to the project Safety and Mission Success (SMSR) review in accordance with NPR
8715.6, NASA Procedural Requirements for Limiting Orbital Debris using the format and
requirements contained in NASA-STD-8719.14, Process for Limiting Orbital Debris.                4.7.2.b.13

During Phase D, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities:
(1) Implement Earned Value Management (EVM) as documented in the Project Plan.                     4.7.2.c.1


During Phase D, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities:
(2) For contracts requiring EVM (refer to the NASA FAR Supplement), conduct required IBRs.         4.7.2.c.2

During Phase D, the project manager and the project team shall:
c. Perform project planning, costing, and scheduling activities:
(3) Prepare and finalize work agreements for Phase E.                                              4.7.2.c.3


During Phase D, the project manager and the project team shall:
d. Implement project cost and schedule control activities:
(1) Provide immediate written notice and a recovery plan to the program manager and the MDAA
if the latest Phase C through D Estimate at Completion (EAC) of the project exceeds by 15 percent
or more the KDP C-approved Management Baseline cost for Phases C through D.                       4.7.2.d.1
During Phase D, the project manager and the project team shall:
d. Implement project cost and schedule control activities:
(2) Provide immediate written notice and a recovery plan to the program manager and the MDAA
if a milestone listed for Phases C and D on the project life cycle chart (Figure 2-4) is estimated to
be delayed in excess of 6 months from the date scheduled in the KDP C-approved Management
Baseline.                                                                                             4.7.2.d.2


During Phase D, the project manager and the project team shall:
d. Implement project cost and schedule control activities:
(3) If the trigger points in (1) or (2) above are breached and upon written notice from the
program manager, update the Project Plan per direction received from the program manager.            4.7.2.d.3

During Phase D, the project manager and the project team shall:
e. Conduct KDP readiness activities:
(1) Obtain approved launch approval documents.                                                       4.7.2.e.1

During Phase D, the project manager and the project team shall:
e. Conduct KDP readiness activities:
(2) Obtain KDP readiness products as shown in Table 4-3.                                             4.7.2.e.2

During Phase D, the project manager and the project team shall:
e. Conduct KDP readiness activities:
(3) Plan, prepare for, and support the governing PMC review prior to KDP E.                          4.7.2.e.3

During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(1) Implement the Project Plan.                                                                      4.8.2.a.1

During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(2) Execute the mission in accordance with the Mission Operations Plan and document this work
in a Mission Report.                                                                          4.8.2.a.2

During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(3) Prior to the project life cycle reviews shown in Figure 2-4 for this phase, conduct internal
reviews in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                            4.8.2.a.3


During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(4) Plan, prepare for, and support the project life cycle reviews shown in Figure 2-4 for this phase
in accordance with NPR 7123.1, Center practices, and the requirements of this document.              4.8.2.a.4
During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(5) Monitor system incidents, problems, and anomalies, as well as system margins to ensure that
deployed project systems function as intended, and investigate system behavior that is observed
to exceed established operational boundaries or expected trends, and implement corrective
actions, as necessary.                                                                          4.8.2.a.5

During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(6) Provide sustaining engineering, as appropriate, to the mission to enhance efficiency, safety,
and accommodate obsolescence.                                                                       4.8.2.a.6


During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(7) Monitor for potential conjunctions with other space objects in accordance with paragraph 3.4
of NPR 8715.6, NASA Procedural Requirements for Limiting Orbital Debris.                         4.8.2.a.7

During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(8) Develop a final End-of-Mission Plan a minimum of 6 months prior to the system
decommissioning/disposal in accordance with NPR 8715.6, NASA
Procedural Requirements for Limiting Orbital Debris using the format and requirements
contained in NASA–STD-8719.14, Process for Limiting Orbital Debris.                                 4.8.2.a.8

During Phase E, the project manager and the project team shall:
a. Perform technical activities:
(9) Capture and archive mission results, including engineering data on system and subsystem
performance, in an MDAA-approved data depository.                                                   4.8.2.a.9


During Phase E, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(1) For all flight projects, provide an updated CADRe (Parts A, B, and C) consistent with the NASA
Cost Estimating Handbook within 60 days after the completion of spacecraft post-launch
checkout. This CADRe is based on the “as built” launched baseline.                                 4.8.2.b.1

During Phase E, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(2) As directed by the program manager, support the development of Project Plan revisions to
continue the mission into extended operations beyond the primary mission phase or beyond any
extension previously included in the plan.                                                   4.8.2.b.2

During Phase E, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(3) Prepare and document a baseline Systems Decommissioning/Disposal Plan.                          4.8.2.b.3
During Phase E, the project manager and the project team shall:
b. Perform project planning, costing, and scheduling activities:
(4) Prepare or update work agreements for Phase F.                                                   4.8.2.b.4

During Phase E, the project manager and the project team shall:
c. Conduct KDP readiness activities:
(1) Obtain KDP readiness products as shown in Table 4-3.                                             4.8.2.c.1

During Phase E, the project manager and the project team shall:
c. Conduct KDP readiness activities:
(2) Plan, prepare for, and support the governing PMC review prior to KDP F.                          4.8.2.c.2

During Phase F, the project manager and the project team shall:
a. Perform technical activities:
(1) Complete analysis and archiving of mission and science data and curation of any returned
samples, as well as archiving of project engineering and technical management data and
documentation, and lessons learned in accordance with agreements, the Project Plan and
Program Plan, and Center and Agency policies.                                                        4.9.2.a.1

During Phase F, the project manager and the project team shall:
a. Perform technical activities:
(2) Prior to the project life cycle reviews shown in Figure 2-4 for this phase, conduct internal
reviews in accordance with NPR 7123.1, Center practices, and the requirements of this
document.                                                                                            4.9.2.a.2


During Phase F, the project manager and the project team shall:
a. Perform technical activities:
(3) Plan, prepare for, and support the project life cycle reviews shown in Figure 2-4 for this phase
in accordance with NPR 7123.1, Center practices, and the requirements of this document.              4.9.2.a.3

During Phase F, the project manager and the project team shall:
a. Perform technical activities:
(4) Implement the Systems Decommissioning/Disposal Plan and safely dispose of project
systems.                                                                                             4.9.2.a.4

During Phase F, the project manager and the project team shall:
b. Provide a final CADRe (Parts A, B, and C) consistent with the NASA Cost Estimating Handbook
within 60 days after End of Planned Mission.                                                         4.9.2.b
Related NPR 7150.2A requirements




Yes




Yes
Yes
Yes




Yes




Yes
Yes
Yes




Yes




Yes
Yes




Yes




Yes
Yes




Yes




Yes
Yes
Yes




Yes




Yes
Yes




Yes




Yes
Yes




Yes
Yes




Yes
Yes




Yes




Yes
Yes
Yes




Yes




Yes




Yes




Yes




Yes
Yes
Yes




Yes




Yes




Yes
Yes




Yes

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:7
posted:10/25/2011
language:English
pages:77
xiaohuicaicai xiaohuicaicai
About