NPR 7150

The project manager shall track the actual results and performance of software activities against the software plans.

1. Corrective actions are taken, recorded, and managed to closure.
2. Changes to commitments (e.g., software plans) that have been agreed to by the affected groups and individuals are taken, recorded, and managed.

The project manager shall require the software developer(s) to periodically report status and provide insight into software development and test activities; at a minimum, the software developer(s) will be required to allow the project manager and software assurance personnel to:

1. Monitor product integration.
2. Review the verification activities to ensure adequacy.
3. Review trades studies and source data.
4. Audit the software development processes and practices.
5. Participate in software reviews and technical interchange meetings.

The project manager shall satisfy the following conditions when a COTS, GOTS, MOTS, OSS, or reused software component is acquired or used:

1. The requirements to be met by the software component are identified.
2. The software component includes documentation to fulfill its intended purpose (e.g., usage instructions).
3. Proprietary rights, usage rights, ownership, warranty, licensing rights, transfer rights, and conditions of use (e.g., required copyright, author, and applicable license notices within the software code, or a requirement to redistribute the licensed software only under the same license (e.g., GNU GPL, ver. 3, license)) have been addressed and coordinated with Center Intellectual Property Counsel.
4. Future support for the software product is planned and adequate for project needs.
5. The software component is verified and validated to the same level required to accept a similar developed software component for its intended use.
6. The project has a plan to perform periodic assessments of vendor reported defects to ensure the defects do not impact the selected software components.

To better estimate the cost of development, the project manager shall establish, document, and maintain:

1. Two cost estimate models and associated cost parameters for all Class A and B software projects that have an estimated project cost of $2 million or more.
2. One software cost estimate model and associated cost parameter(s) for all Class A and Class B software projects that have an estimated project cost of less than $2 million.
3. One software cost estimate model and associated cost parameter(s) for all Class C and Class D software projects.
4. One software cost estimate model and associated cost parameter(s) for all Class F software projects.

The project manager’s software cost estimate(s) shall satisfy the following conditions:

1. Covers the entire software life cycle.
2. Is based on selected project attributes (e.g., programmatic assumptions/constraints, assessment of the size, functionality, complexity, criticality, reuse code, modified code, and risk of the software processes and products).
3. Is based on the cost implications of the technology to be used and the required maturation of that technology.
4. Incorporates risk and uncertainty, including end state risk and threat assessments for cybersecurity.
5. Includes the cost of the required software assurance support.
6. Includes other direct costs.

The project manager shall document and maintain a software schedule that satisfies the following conditions:

1. Coordinates with the overall project schedule.
2. Documents the interactions of milestones and deliverables between software, hardware, operations, and the rest of the system.
3. Reflects the critical dependencies for software development activities.
4. Identifies and accounts for dependencies with other projects and cross-program dependencies.

The project manager shall evaluate software for potential reuse by other projects across NASA and contribute reuse candidates to the NASA Internal Sharing and Reuse Software systems, however, if the project manager is a contractor, then a civil servant must pre-approve all such software contributions; all software contributions should include, at a minimum, the following information:

1. Software Title.
2. Software Description.
3. The Civil Servant Software Technical Point of Contact for the software product.
4. The language or languages used to develop the software.
5. Any third party code contained therein and the record of the requisite license or permission received from the third party permitting the Government’s use, if applicable.

The project manager shall establish and maintain:

1. Software test plan(s).
2. Software test procedure(s).
3. Software test(s), including any code specifically written to perform test procedures.
4. Software test report(s).

The project manager shall establish and implement procedures to:

1. Designate the levels of control through which each identified software configuration item is required to pass.
2. Identify the persons or groups with authority to authorize changes.
3. Identify the persons or groups to make changes at each level.