1. Requirements

2.1.5.15 The Center Director or designee shall ensure that the Government has clear rights in the software, a Government purpose license, or other appropriate license or permission from third party owners prior to providing the software for internal NASA software sharing or reuse.

1.1 Notes

NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement.

1.2 History

Click here to view the history of this requirement: SWE-215 History

SWE-215 - Last used in rev NPR 7150.2D

Rev	SWE Statement
A
Difference between A and B	N/A
B
Difference between B and C	NEW
C	2.1.5.15 The Center Director or designee shall ensure that the Government has clear rights in the software, a Government purpose license, or other appropriate license or permission from third party owners prior to providing the software for internal NASA software sharing or reuse.
Difference between C and D	No Change
D	2.1.5.13 The Center Director or designee shall ensure that the Government has clear rights in the software, a Government purpose license, or other appropriate license or permission from third party owners prior to providing the software for internal NASA software sharing or reuse.

2. Rationale

Legal requirements to ensure that NASA has the appropriate software rights in place to be able to share software internal to NASA. The only way to determine if NASA has the proper ownership rights is to have and maintain a list of all contributors to the software product.

3. Guidance

This requirement applies to all NASA centers and all software classifications.

If you are not sure, contact your Center’s Legal office.

The only way to determine if NASA has the proper ownership rights is to have a list of all contributors to the software product. Make sure that you and the project also know if the software component or software product uses and contains any commercial software components or any open source software components.

If the software was developed by NASA Civil servants and software does not include any open source or commercial software, you can share the software. If a contractor helped develop the software, then contact the Center legal office about the rights to the software. Before any software can be shared, the Civil servant POC has to have a list of all contributors to the software product (see SWE-217).

You also have to ensure that the Proprietary rights, usage rights, ownership, warranty, licensing rights, and transfer rights have been addressed for the software components being shared. (see SWE-027).

NASA needs to avoid software license issues associated with sharing software. Make sure that you have clear rights in the software, a Government purpose license, or other appropriate license or permission from third party owners before providing the software for internal NASA software sharing or reuse.

SWE-027 - Use of Commercial, Government, and Legacy Software

SWE-217 - List of All Contributors and Disclaimer Notice

4. Small Projects

This requirement applies to all NASA centers and all software classifications.

5. Resources

5.1 References

Click here to view master references table.

(SWEREF-197)
Software Processes Across NASA (SPAN)
Software Processes Across NASA (SPAN) web site in NEN SPAN is a compendium of Processes, Procedures, Job Aids, Examples and other recommended best practices.

5.2 Tools

Tools to aid in compliance with this SWE, if any, may be found in the Tools Library in the NASA Engineering Network (NEN).

NASA users find this in the Tools Library in the Software Processes Across NASA (SPAN) site of the Software Engineering Community in NEN.

The list is informational only and does not represent an “approved tool list”, nor does it represent an endorsement of any particular tool. The purpose is to provide examples of tools being used across the Agency and to help projects and centers decide what tools to consider.

Content

Space Tools