View this section on the website
See edit history of this section
Post feedback on this section
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
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.
4. Small Projects
This requirement applies to all NASA centers and all software classifications.
5. Resources
5.1 References
- (SWEREF-083) NPR 7150.2D, Effective Date: March 08, 2022, Expiration Date: March 08, 2027 https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=7150&s=2D Contains link to full text copy in PDF format. Search for "SWEREF-083" for links to old NPR7150.2 copies.
- (SWEREF-186) Federal Acquisition Requirements (FAR) clause 52.227-14
- (SWEREF-197) Software Processes Across NASA (SPAN) web site in NEN SPAN is a compendium of Processes, Procedures, Job Aids, Examples and other recommended best practices.
- (SWEREF-373) NPR 2210.1C, Space Technology Mission Directorate, Effective Date: August 11, 2010, Expiration Date: January 11, 2022
- (SWEREF-551) Public Lessons Learned Entry: 1370.
- (SWEREF-556) Public Lessons Learned Entry: 1481.
- (SWEREF-700) Federal Acquisition Requirements (FAR) clause 52.227-11
- (SWEREF-701) Federal Acquisition Requirements (FAR) clause 52.227-16
- (SWEREF-702) NPR 7500.2A, Effective Date: June 16, 2022, Expiration Date: June 16, 2027 https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=7500&s=2 Contains link to full text copy in PDF format.
- (SWEREF-703) NPR 2092.1B, Effective Date: August 22, 2014, Expiration Date: December 31, 2026.
5.2 Tools
6. Lessons Learned
6.1 NASA Lessons Learned
No Lessons Learned have currently been identified for this requirement.
6.2 Other Lessons Learned
No other Lessons Learned have currently been identified for this requirement.
