


1 - Purpose
This information is intended to enhance project teams' understanding of the relationship between NPR 7150.2 requirements and other NASA software requirements.
For instance, software assurance activities require input, such as documents or process records, from projects. When project personnel understand the relationship of the software assurance requirements to the software engineering requirements, the requests from software assurance personnel are more likely to seem reasonable and the results software assurance personnel produce may be more acceptable to the project.
2 - Traceability to Other NASA Procedural Requirements (NPRs)
This spreadsheet identifies relationships between the requirements ("shall" statements) in NPR 7150.2 for Software Engineering, and the parent policy NPD 7120.4D3 addressing Engineering and Program/Project Management, NPR 7123.1A
1 addressing Systems Engineering, and NPR 7120.5
2 (NM 7120-18) addressing Program and Project Management.
Draft versions of this spreadsheet were reviewed by the NPR 7150.2 guidance handbook team as well as OCE representatives before being approved for use by the NASA community.
Because this spreadsheet was generated as a guidance tool for NPR 7150.2, the NPR 7150.2 requirements are listed in the chart along with their identifiers (SWE numbers). All requirements mapped to the NPR 7150.2 requirements are identified by the clause number in their respective document. Empty cells indicate no related requirement in that particular document. Clarifying phrases and references to appendices where explanatory details are found are noted throughout the spreadsheet.
2.1 NPRs Mapping Spreadsheet
The following spreadsheet is available for download from the web. Download here: [^NPR 7150 traced to NPR 7123 and NPR 7120_20100716_V2.xlsx]
This spreadsheet has multiple columns, as described below:
- Column A: 7120.4D Section # - This column lists each section of NPR 7120.4D and indicates which have mappings to NPR 7150.2.
- Column B/C: 7150 requirement & SWE-Number - These columns show the text of each of the NPR 7150.2 requirements (Column B) with the SWE requirement numbers (Column C)
- Column D: 7123.1A Section # - This column lists each section of NPR 7123.1A and indicates which have mappings to NPR 7150.2.
- Column E: 7120.5D Section # - This column lists each section of NPR 7120.5D and indicates which have mappings to NPR 7150.2.
3 - Traceability to Other NASA Standards (STDs)
This spreadsheet identifies relationships between the requirements ("shall" statements) in NPR 7150.2 for Software Engineering, and the engineering standards of NASA-STD-8739.84 addressing Software Assurance and NASA-STD-8719.13B
5 addressing Software Safety.
Because this spreadsheet was generated as a guidance tool for NPR 7150.2, the NPR 7150.2 requirements are listed in the chart along with their identifiers (SWE numbers). All requirements mapped to the NPR 7150.2 requirements are identified by the clause number in their respective document. Empty cells indicate no related requirement in that particular document. Clarifying phrases and references to appendices where explanatory details are found are noted throughout the spreadsheet.
3.1 STDs Mapping Spreadsheet
The following spreadsheet is available for download from the web. Download here: [^NPR 7150 traced to NASA-STD-8739 8 and NASA-STD-8719 13B_20100924.xls]
This spreadsheet has multiple columns, as described below:
- Column A: 7150 requirement & SWE-Number - These columns show the text of each of the NPR 7150.2 requirements with the SWE requirement numbers
- Column B: NASA-STD-8739.8 Section # - This column lists each section of NASA-STD-8739.8 and indicates which have mappings to NPR 7150.2.
- Column C: NASA-STD-8719.13B Section # - This column lists each section of NASA-STD-8719.13B and indicates which have mappings to NPR 7150.2.
References
- NPR-7123.1A (NASA Systems Engineering Processes and Requirements)
- NPR-7120.5D (NASA Space Flight Program and Project Management Requirements)
- NPR-7120.4D (NASA Engineering and Program/Project Management Policy)
- NASA Technical Standard, NASA Software Assurance Standard, NASA-STD-8739.8, 2004.
- NASA-STD-8719.13B (Software Safety Standard)
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. See Chapter 8. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. See Chapter 16. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. See Chapters 8 and 9.
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. See Chapter 12. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. See Chapters 16 and 17. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. See Chapter 13. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-001) Software Development Process Description Document, EI32-OI-001, Revision R, Flight and Ground Software Division, Marshall Space Flight Center (MSFC), 2010. See Chapter 9. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-002)
C/S2ESC - Software & Systems Engineering Standards Committee, Published Date:2014-06-13(SWEREF-003)
IVV 09-1, Revision P, NASA Independent Verification and Validation Program, Effective Date: February 26, 2016(SWEREF-004)
Software Engineering Institute, Carnegie Mellon University. Retrieved September 27, 2016 from https://www.securecoding.cert.org/confluence/display/seccode/SEI+CERT+Coding+Standards(SWEREF-004)
This site supports the development of secure coding standards for commonly used programming languages such as C, C++, Java, and Perl, and the Android™ platform. Top ten plus two bonus practices.(SWEREF-005)
AIAA-2008-2156 Blattnig, S.R.; Green, L.L.; Luckring, J.M.; Morrison, J.H.; Tripathi, R.K.; Zang, T.A. (2008). NASA users can access AIAA documents via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of AIAA documents.(SWEREF-006)
Twine, J.R. (2003).(SWEREF-007) WBS Checklist Tool, NASA Goddard Space Flight Center (GSFC), 2007. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-008)
580-CK-032-02, Software Engineering Division, NASA Goddard Space Flight Center, 2010.(SWEREF-009)
NPR 8000.4B, NASA Office of Safety and Mission Assurance, 2017. Effective Date: December 06, 2017 Expiration Date: December 06, 2022(SWEREF-009)
NPR 8000.4B, NASA Office of Safety and Mission Assurance, 2017. Effective Date: December 06, 2017 Expiration Date: December 06, 2022 See also the Risk Management Plan template.(SWEREF-010)
Software Engineering Institute, CMU, Feb. 2006.(SWEREF-011) Change Request Log Template, NASA Goddard Space Flight Center, 2015. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-012) Checklist for the Contents of Software Requirements Review (SRR), 580-CK-005-02, Software Engineering Division, NASA Goddard Space Flight Center, 2009. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-013) "Code and Unit Test," HOU-EGP-310, Boeing, 2002. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-014)
SSP 50038, Revision B, NASA International Space Station Program, 1995.(SWEREF-015)
COURSE SS-SD_AGSD_A01_IT_ENUS. System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://saterninfo.nasa.gov/. User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://saterninfo.nasa.gov/.(SWEREF-016)
James J. Marshall, editor, 2010. Prepared by NASA Earth Science Data Systems – Software Reuse Working Group. Marshall 2011 Retrieved July, 2016 from https://earthdata.nasa.gov/files/RRLs_v1.0.pdf.(SWEREF-017) Constellation Computing Safety Requirements, CxP 70065, Revision A, 2005.
(SWEREF-018)
NPR 2800.2A, Office of the Chief Information Officer, Effective Date: August 05, 2020, Expiration Date: August 05, 2025(SWEREF-019) FSW Testbed Validation Description, 582-2008-006, Version 1, Flight Software Systems Branch, NASA Goddard Space Flight Center (GSFC), 2008. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-020)
IEEE, Version 3.0 describes generally accepted knowledge about software engineering. Its 15 knowledge areas (KAs) summarize basic concepts and include a reference list pointing to more detailed information.(SWEREF-021)
Philippe B. Kruchten. 1995(SWEREF-022) Functional Configuration Audit Form, Form 0010 NASA Marshall Space Flight Center (MSFC), 2010. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-023)
NPR 8900.1B, NASA Office of the Chief Health & Medical Officer, 2008., Effective Date: December 16, 2016, Expiration Date: December 16, 2021(SWEREF-024)
NPR 8705.2C, NASA Office of Safety and Mission Assurance, 2008., Effective Date: July 10, 2017, Expiration Date: July 10, 2022(SWEREF-025)
DI-IPSC-81436A, Department of Defense, 1999.(SWEREF-026)
ISO/IEC TR 19759 was prepared by the IEEE Computer Society, 2005(SWEREF-027)
SMA-002-14, provides This course provides training on Root Cause Analysis (RCA) methodology that can be used in both general problem solving and mishap and close call investigations. NOTE: This course is one of five needed to fulfill the requirements for introductory training on NASA mishap investigations in accordance with NPR 8621.1B User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/.(SWEREF-028)
T2103, NASA Independent Verification and Validation Program, 2011.(SWEREF-029) JSC Software Engineering Improvement Plan, JSC 29542,rev A, NASA Lyndon B. Johnson Space Center (JSC), 2003. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-030)
NASA Office of Safety and Mission Assurance, NPR 8735.2C, Effective Date: March 12, 2021 Expiration Date: March 12, 2026(SWEREF-031)
SEL-84-101, Revision 1, Software Engineering Laboratory Series, NASA Goddard Space Flight Center, 1990.(SWEREF-032) Measurement and Analysis for Projects, 580-PC-048-04, NASA Goddard Space Flight Center (GSFC), 2019. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-033)
SMA-SA-WBT-100 SATERN. System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://saterninfo.nasa.gov/. User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://saterninfo.nasa.gov/.(SWEREF-034)
NASA-HDBK 8739.23A, Approved: 02-02-2016, Superseding: NASA-HDBK-8739.23 With Change 1,(SWEREF-035)
NPR 2830.1A, Office of the Chief Information Officer, Effective Date: December 19, 2013, Expiration Date: November 30, 2021(SWEREF-036)
NPD 8700.1E, NASA Office of Safety and Mission Assurance, 2008. Effective Date: October 28, 2008, Expiration Date: April 28, 2020(SWEREF-037)
NPR 1441.1E, NASA Office of the Chief Information Officer, Effective Date: January 29, 2015, Expiration Date: January 29, 2024(SWEREF-038)
Release 1.0, NASA Office of the Chief Engineer, 2002.(SWEREF-038)
Release 1.0, NASA Office of the Chief Engineer, 2002.(SWEREF-039) NASA Software Engineering Requirements, NID 7150-113 NASA Interim Directive for Software License Management - NPR 7150.2B, NASA Office of the Chief Engineer, 2014. Effective Date: November 19, 2014, Expiration Date: November 19, 2019 1/22/2020 NID 7150-113 no longer active . Formerly associated with: Intro, SWE-004, SWE-020, SWE-022, SWE-085, SWE-098, SWE-121, SWE-140, SWE-154, Topic 7.2, Topic 7.4, Topic 7.15,
(SWEREF-039) NASA Software Engineering Requirements, NPR 7150.2B, NASA Office of the Chief Engineer, 2014. Effective Date: November 19, 2014, Expiration Date: November 19, 2019 NID7150-113 no longer active replaced by SWEREF-083
(SWEREF-040)
Commissioned by the NASA Office of Chief Engineer, Technical Excellence Program, Adam West, Program Manager, and edited by Daniel L. Dvorak, Systems and Software Division, Jet Propulsion Laboratory, 2009.(SWEREF-041)
NPR 7123.1C, Office of the Chief Engineer, Effective Date: February 14, 2020, Expiration Date: February 14, 2025(SWEREF-041)
NPR 7123.1B, NASA Office of the Chief Engineer, Effective Date: April 18, 2013, Expiration Date: April 18, 2019 , Appendix C. Practices for Common Technical Processes(SWEREF-042)
IEEE - 1633-2016. The methods for assessing and predicting the reliability of software, based on a life-cycle approach to software reliability engineering (SRE), are prescribed in this recommended practice(SWEREF-043)
NASA Engineering & Safety Center. Retrieved July, 2016 from http://www.nasa.gov/content/nasa-engineering-network-communities-of-practice/index.html.(SWEREF-044) Physical Configuration Audit Form, Form 0011, NASA Marshall Space Flight Center (MSFC), 2010. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-045)
IVV 09-4, Version: AG, Effective Date: June 24, 2014(SWEREF-046) Project Requirements Development and Management, GLPR 7123.11, NASA Glenn Research Center, 2010. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-047)
SEL-81-305, Revision 3, Software Engineering Laboratory Series, NASA Goddard Space Flight Center, 1992.(SWEREF-048)
NPR 8705.4A, Office of Safety and Mission Assurance, Effective Date: April 29, 2021, Expiration Date: April 29, 2026(SWEREF-049) Software Requirements Development, 580-PC-020-002, NASA Goddard Space Flight Center, 2012. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook
(SWEREF-050)
SMA-SA-WBT-203 SATERN. System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/. User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/.(SWEREF-051) Software and Systems Engineering Process Implementation (SSEPI) Plan, KSC-PLN-2302, Revision A, NASA Kennedy Space Center (KSC). This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-052)
Introduction to Root Cause Analysis (SMA-002-10) (NASA Root Cause Analysis, combined with the four prerequisite courses, meets the Root Cause Analysis training requirements in NPR 8621.1B) User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/.(SWEREF-053)
NASA Root Cause Analysis (SMA-SAFE-OSMA-4003), combined with the five prerequisite courses, meets the Root Cause Analysis training requirements in NPR 8621.1B). User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/.(SWEREF-054)
NPR 8621.1C, Office of Safety and Mission Assurance, Effective Date: May 19, 2016, Expiration Date: May 19, 2021 Also see Mishap Investigation web site at https://sma.nasa.gov/sma-disciplines/mishap-investigation(SWEREF-055)
SMA-SA-WBT-320 SATERN. System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/. User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/.(SWEREF-056) Software Engineering Improvement Plan FY12, NASA Langley Research Center (LaRC), 2012. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-057) Software Management Plan (SMP) Template, GRC-SW-TPLT-SMP, NASA Glenn Research Center (GRC), 2009. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-058)
SATERN is NASA's Learning Management System (LMS) that provides web-based access to training and career development resources. Generic Reference to SATERN. User needs account to access SATERN courses. This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://satern.nasa.gov/.(SWEREF-059)
ISO/IEC 19770-5:2015(en), Information technology — IT asset management —(SWEREF-060)
NASA Engineering Network. Accessed September, 2016. Formerly Space Asset Protection, The NASA Engineering Network (NEN) is accessible only to NASA users.(SWEREF-061)
JPL Document D-24994, NASA Jet Propulsion Laboratory, 2003. See Page 20. Approved for U.S. and foreign release.(SWEREF-062) Software Supplier Agreement Management Plan (SSAMP) Template, NASA Jet Propulsion Laboratory, 2002. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-063) Software User Manual (SUM) Template, GRC-SW-TPLT-SUM, NASA Glenn Research Center (GRC), 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-064)
NIST SP 800-27, Revision A.(SWEREF-065)
NIST SP 800-64 Revision 2.(SWEREF-066)
NPD 1000.3E, Associate Administrator, April 15, 2015, Expiration Date: April 15, 2026(SWEREF-067) Trade Study Checklist, NASA Marshall Space Flight Center (MSFC), 2008. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-068) Trade Study Template, NASA Marshall Space Flight Center (MSFC), 2009. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-069) Transition of Software to a Higher Classification, GRC-SW-7150.10, Rev. C, Software Engineering Process Group, NASA Glenn Research Center, 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-070)
Version 3.0, NASA Office of the Chief Technology Officer, 2004.(SWEREF-071) Acceptance Review Checklist, NASA Marshall Space Flight Center (MSFC). This NASA-specific information and resource may be available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-072) Checklist for the Contents of Software Critical Design Review (CDR), 580-CK-008-02, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2010. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-073) Checklist for the Contents of Software Preliminary Design Review (PDR), 580-CK-007-02, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2010. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-074)
At www.information-management-architect.com. Retrieved May 17, 2011, from http://www.information-management-architect.com/software-testing-procedures.html.(SWEREF-075)
ISO/IEC 2382:2015, Information technology — Vocabulary, Replaces ISO/IEC 2382-20:1990,(SWEREF-076)
ISO/IEC 26514:2008(en), Systems and software engineering — Requirements for designers and developers of user documentation(SWEREF-077)
ESA PSS-05-05, Issue 1, Revision 1, ESA Board for Software Standardisation and Control, 1995. The PSS family of standards was the ESA internal set of standards which was replaced by ECSS. It inluded a software engineering standard and a set of guides. This page contains the cited resource as well as others in the collection.(SWEREF-078) SED Decision Analysis and Resolution, 580-SP-038-002, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2005. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-079) SED Inspections, Peer Reviews, and Walkthroughs, 580-SP-055-02, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2006. Updated title from "ISD Inspections, Peer Reviews, and Walkthroughs, 580-SP-055-01" to "SED Inspections, Peer Reviews, and Walkthroughs, 580-SP-055-02" to reflect updated version of document, and to reflect the new name (Software Engineering Division) of the GSFC organization that produced the document.) This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-080)
ISO/IEC/IEEE 26513:2017(en), Systems and software engineering — Requirements for testers and reviewers of information for users(SWEREF-081)
NPR 1600.1A, Office of Protective Services, Effective Date: August 12, 2013, Expiration Date: December 12, 2021(SWEREF-082)
NPR 7120.5F, Office of the Chief Engineer, Effective Date: August 03, 2021, Expiration Date: August 03, 2026,(SWEREF-082)
NPR 7120.5D (NID 7120-97), NASA Office of the Chief Engineer, 2010. See also NID 7120-97. NOTE: This SWEREF was created to document changes made to SWEREF-082. SWEREF-082 was updated to reflect the updated version of 7120.5 from version D to version E on 10-10-2012 by Lisa Dallas. SWEREF-082(old) was linked to these SWEs/Topics: SWE-001, SWE-002, SWE-004, SWE-005, SWE-014, SWE-017, SWE-018, SWE-019, SWE-024, SWE-025, SWE-026, SWE-028, SWE-036, SWE-037, SWE-039, SWE-041, SWE-043, SWE-044, SWE-046, SWE-060, SWE-063, SWE-079, SWE-100, SWE-101, SWE-103, SWE-107, SWE-112, SWE-116, SWE-120, SWE-121, SWE-122, SWE-124, SWE-125, SWE-126, SWE-127, SWE-128, SWE-129, SWE-131, SWE-136, SWE-140, Topic 7.4, Topic 7.8, Topic 7.16, Topic 7.15(SWEREF-082)
NPR 7120.5F, Office of the Chief Engineer, Effective Date: August 03, 2021, Expiration Date: August 03, 2026,(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-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-084)
ISO/IEC 19770-1:2017(en); Part 1: IT asset management systems — Requirements,(SWEREF-085)
NPD 2540.1I, Office of the Chief Information Officer, Effective Date: August 19, 2019, Expiration Date: August 19, 2024,(SWEREF-086)
5526_7-21-06_Req_RevA_generic-R1V0, 2006. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.(SWEREF-086)
5526_7-21-06_Req_RevA_generic-R1V0, 2006. See Section 4: Validate Requirements. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.(SWEREF-087)
NPD 1600.2E, Office of Protective Services, Effective Date: April 28, 2004, Expiration Date: May 28, 2022(SWEREF-088)
NIST Special Publication 800-53, Revision 5, September, 2020, U.S. Department of Commerce,(SWEREF-089) Project-Type/Goal/Metric Matrix, developed by NASA Software Working Group Metrics Subgroup, 2004. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-090)
NIST Special Publication 800-37, Revision 2, National Institute of Standards and Technology, December, 2018,(SWEREF-091) Requirements Management, 580-PC-024-04, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2016. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-092)
MIL-STD-1629A, (24 NOV 1980) This standard establishes requirements and procedures for performing a failure mode, effects, and criticality analysis (FMECA) to systematically evaluate and document, by item failure mode analysis, the potential impact of each functional or hardware failure on mission success, personnel and system safety, system performance, maintainability, and maintenance requirements.(SWEREF-093)
Special Publication 800-146, Badger, Grance, et. al., National Institute of Standards and Technology, May, 2012(SWEREF-094) Software Acquisition Statement of Work Guideline, GRC-SW-7150.14, Revision C, NASA Glenn Research Center (GRC), April, 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-095) Software Configuration Management Plan - Example 2a, NASA Langley Research Center (LaRC), 2000.
(SWEREF-096) Software Design Description Template, GRC-SW-TPLT-SDD, NASA Glenn Research Center (GRC), 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-097) Software Design Document Checklist, NASA Marshall Space Flight Center (MSFC), 2008.
(SWEREF-098) Software Development Plan (SDP) Checklist, NASA Marshall Space Flight Center (MSFC), 2008.
(SWEREF-099)
NFS 1852.237–73,(SWEREF-100) Software Management Plan / Product Plan (SMP/PP) For Class A, B & C Software, 580-TM-033-02, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2010.
(SWEREF-100) "Software Management Plan / Product Plan (SMP/PP) For Class A, B & C Software," 580-TM-033-02, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2010. See the Verification and Validation section of this document.
(SWEREF-101) Software Requirements Specifications (SRS) Checklist, NASA Marshall Space Flight Center (MSFC), 2008.
(SWEREF-102)
48 CFR § 1852.237-72,(SWEREF-103) Software Risk Identification, 580-SP-013-03, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2014. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-104) Software Risk Monitoring and Control, 580-SP-014-03, Software Engineering Division, NASA Goddard Space Flight Center (GSFC), 2014. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-105) Software System/Subsystem Requirements Specifications (SSRS) Checklist, NASA Marshall Space Flight Center (MSFC) , 2012. This NASA-specific information and resource may be available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-106)
NASA Marshall Space Flight Center (MSFC).(SWEREF-107)
(SWEREF-108)
Revision 2.0, SQI Process and Product Definition Group, Jet Propulsion Lab (JPL), NASA, 2005.(SWEREF-109)
NASA Marshall Space Flight Center(MSFC), 2008.(SWEREF-110)
(SWEREF-111) Test Procedure Checklist, NASA Marshall Space Flight Center (MSFC), 2008.
(SWEREF-112) Test Readiness Review Checklist, NASA Marshall Space Flight Center. This NASA-specific information and resource may be available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-113) Test Report Checklist, NASA Marshall Space Flight Center (MSFC), 2008.
(SWEREF-114)
DSTL-94-002, Data System Technology Laboratory Series, NASA Goddard Space Flight Center (GSFC), 1994.(SWEREF-115) Verification Handbook, Volume 1: Verification Process, MSFC-HDBK-2221, NASA Marshall Space Flight Center (MSFC), 1994.
(SWEREF-116)
2008. Accessed August 15, 2011 at http://ceh.nasa.gov. This URL is a website that lists multiple resources for download.(SWEREF-117)
NPD 1001.0C, NASA Office of Office of the Chief Financial Officer, 2018.(SWEREF-118)
(SWEREF-119) Acquirer Software Assurance Plan template.
(SWEREF-120)
Suellen Eslinger (The Aerospace Corporation), Karen L. Owens (The Aerospace Corporation), Mary A. Rich (The Aerospace Corporation), This 2004 presentation was delivered at the 3rd OSD Conference on the Acquisition of Software Intensive Systems by Richard J. Adams and others of the Aerospace Corporation.(SWEREF-121)
(SWEREF-122)
Alberts, C.J. , 1996.(SWEREF-123)
Andy German, Qinetiq Ltd. (2003). " CrossTalk Online.(SWEREF-124)
ASME (2006). New York, NY Available to members(SWEREF-125)
Asay, Matt. CNET, September 27, 2007(SWEREF-126)
Balci, O. (2004). Proceedings of the 2004 Winter Simulation Conference. R.G. Ingalls; M.D. Rossetti; J.S. Smith; B.A. Peters, eds. Dec. 5-8. Piscataway, NJ: IEEE. pp. 122-129.(SWEREF-127)
(SWEREF-128)
Banks, J., ed. (1998). New York: John Wiley & Sons, Sep 14, 1998,(SWEREF-129)
Baron, Sally J. F. (September, 2006). International Public Procurement Conference Proceedings.(SWEREF-130)
Baron, Sally J. F., Ph.D. Management Consulting. IEEE Xplore, Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07), 0-7695-2785-X/07.(SWEREF-131)
Len Bass, Paul Clements, and Rick Kazman. Boston: Addison-Wesley, 2003.(SWEREF-132)
Beaver, Brian (2002). Categorizing Defects by Eliminating "Severity" and "Priority". In StickyMinds.com. Retrieved February 29, 2012.(SWEREF-133)
Sven Efftinge, Peter Friese, Jan Köenlein, June 2008.(SWEREF-134)
Boehm, B., (1988). IEEE Computer. 21(5). Pp 61-72.(SWEREF-135)
Boehm, B., et. al. (2000). Prentice Hall, Upper Saddle River, N.J., ISBN-10: 0130266922(SWEREF-136)
Boehm, Barry. Englewood Cliffs, NJ:Prentice-Hall, 1981.(SWEREF-137) Boeing Houston Site Metrics Manual, HOU-EGM-308, January 17, 2002. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-138) Software Maintenance Boeing, Houston Procedure, HOU-EGP-333, 2002. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-139)
Booch, G., Rumbaugh, J., and Jacobson, L., Addison Wesley, 2nd Edition, 2005.(SWEREF-140)
Borysowich, Craig, 2006. Observations from a Tech Architect: Enterprise Implementation Issus & Solutions,(SWEREF-141)
Brijesh, R. G. (ed.) (July, 2009). In WikiHow: the how to manual that you can edit.(SWEREF-142) The Importance of Requirements Traceability Brown, Craig (2008). The Project Management Hut. No longer available Formerly accessed June 2011 from http://www.pmhut.com/the-importance-of-requirements-traceability. Other articles are available based on a search on the title.
(SWEREF-143)
Budden, Timothy J. AVISTA. CrossTalk - Journal of Defense Software Engineering, November 2003. See page 18.(SWEREF-144)
Diaz, Al,NASA Goddard Space Flight Center (Jan, 2004). CAIB Columbia Accident Investigation Board Report. (August 2003). Vol. 1. PB2005-100968(SWEREF-145)
California Polytechnic University, extracted from Reusable Software Management Plan, NASA Goddard Space Flight Center (GSFC). Accessed January 3, 2012 from http://users.csc.calpoly.edu/~jdalbey/308/Resources/NASAsqaplan.html.(SWEREF-146)
Capers Jones, 2007, McGraw Hill, New York.(SWEREF-147)
Carlos, Tom (October, 2008).(SWEREF-148)
Carney, D.J., Oberndorf, P.A. (May, 1997). Carnegie Mellon Software Engineering Institute, Carnegie Mellon University.(SWEREF-149)
(SWEREF-150)
GAO-14-413, Report to the Chairman, Committee on Homeland Security and Governmental Affairs, U.S. Senate, May 2014,(SWEREF-151)
Chen, Yuan-Tsong; Tanik, Murat M.; Southern Methodist University, Dallas, TX IEEE0-8186-3520-7/92, 1992. Published in: 1992 Proceedings - The Third International Workshop on Rapid System Prototyping(SWEREF-152)
Chillarege, Ram (1999). Technical Report RC 21457 Log 96856. Center for Software Engineering/IBM Research.(SWEREF-153)
Chrissis, M.B., Konrad, M., Shrum, S., This book is the definitive reference for CMMI-DEV Version 1.3. It describes best practices for the development and maintenance of products and services across their lifecycle. 3rd Edition, 2010, Addison-Wesley Professional, ISBN: 0-321-71150-5(SWEREF-154)
Clark, Drs. Brad and Betsy. Software Metrics, Inc. (June, 2007). CrossTalk - Journal of Defense Software Engineering.(SWEREF-155)
Clemen, R.T. (1996). Second Edition. Pacific Grove, CA: Brooks/Cole. download available from link.(SWEREF-156)
2012, March 11. In Wikipedia, The Free Encyclopedia. Retrieved 18:29, March 19, 2012, from http://en.wikipedia.org/w/index.php?title=Cluster_(spacecraft)&oldid=481296441 Note: Wikipedia disambiguous link rerout from topic: Ariane_5_Flight_501(SWEREF-157)
CMMI Development Team (2010). CMU/SEI-2010-TR-033, Software Engineering Institute.(SWEREF-157)
CMMI Development Team (2010). CMU/SEI-2010-TR-033, Software Engineering Institute.(SWEREF-158)
NDIA Working Group, NDIA Systems Engineering Division, CMMI Technology Conference, Nov, 2010.(SWEREF-159)
In Center for Systems and Software Engineering, University of Southern California.(SWEREF-160)
Ingo Sturmer, Mirko Conrad, 2004.(SWEREF-161)
MSDN Library, 2003. Accessed May 23, 2011 from http://msdn.microsoft.com/en-us/library/aa291591%28v=vs.71%29.aspx. Checked 6/10/2019, document retired and no longer available, need to find suitable replacement(SWEREF-162)
Milan Malkani, 2011. Accessed May 20, 2011 at http://ezinearticles.com/6122965.(SWEREF-163)
Compuware Corporation (2004). Accessed via Slideshare.net in June 2011.(SWEREF-164)
Cooke, R.M. (1991). New York: Oxford University Press.(SWEREF-165)
Cooper, Jack, IEEE Transactions on Software Engineering, January 1984. Retrieved December 21, 2011 from http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5010194&tag=1.(SWEREF-166)
Database of cost metrics for NASA missions: http://www.nasa.gov/offices/ooe/CADRe_ONCE.html#.U0Qc-BC9Z8E, (Accessed December 09, 2014). This URL is a website that lists multiple resources for download.(SWEREF-167)
June 1997.University of Southern California, Center for Software Engineering.(SWEREF-168) COTS Software: Vendor Demonstration Guidelines and Scripts, Defense Acquisition University, 2009.
(SWEREF-169)
Crosby, P.B. New York, McGraw-Hill, 1979.(SWEREF-170)
D. Dvorak, Presented at AIAA Infotech@Aerospace, Seattle, WA, April 2009. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.(SWEREF-171)
Wetherholt, Martha, Session: I@A-33: Software Assurance, AIAA Infotech@Aerospace Conference, 06 April 2009 - 09 April 2009, Seattle, Washington,(SWEREF-172)
Defense Acquisition University, Production Date:16-September-2013. Retrieved from https://at.dod.mil/sites/default/files/documents/DefenseAcquisitionGuidebook.pdf.(SWEREF-173)
Dellarocas, Chrysanthos, Sloan School of Management, Massachusetts Institute of Technology, MA, 1997.(SWEREF-174)
Department of Defence Systems Management College, Supplementary text prepared by the Defense Acquisition University Press, Fort Belvoir, VA, 2001.(SWEREF-175)
Department of Defense, MIL-STD-3022, 2008.(SWEREF-176)
Department of Defense, DI-MCCR-80012A, 1988.(SWEREF-177)
(SWEREF-178)
Dorfman, Merlin, Software Engineering Institute. (March, 1999). Multiple resources are available by searching Requirements Engineering at this site.(SWEREF-179)
A variety of articles from Dr. Forrest Shull is available on this cite.(SWEREF-180)
Easterbrook, Steve (1996), Proceedings from 2nd World Conference on Integrated Design and Process Technology (IDPT). Retrieved on February 28, 2012 from http://www.cs.toronto.edu/fm/pubs/pdf/easterbrook96c.pdf.(SWEREF-181)
Easterbrook, Steve, 1998. NASA-IVV-97-015, October, 16, 1997, Accessed November 2011 from http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19980016986_1998065191.pdf.(SWEREF-182)
Emigh, Jacqueline (May, 2008), Betanews. Accessed March 19, 2012 from http://betanews.com/2008/05/20/researchers-bugs-in-open-source-software-are-waning/(SWEREF-183)
In Wikipedia, The Free Encyclopedia (6 April 2019).(SWEREF-184)
Stutzke, R., Addison-Wesley Professional (May 6, 2005).(SWEREF-185)
Feathers, Michael C. (2004). Prentice Hall.(SWEREF-186)
Federal Acquisition Requirements (FAR) clause 52.227-14(SWEREF-187)
Fidelity ISG Glossary Simulation Interoperability Standards Organization (SISO). (Dec. 1998). Vol. 3.0. Site still exists at https://www.sisostds.org/. Unable to locate the Fidelity ISG Glossary.(SWEREF-188)
Florac, William; CMU/SEI-92-TR-022, Software Engineering Institute. 1992.(SWEREF-189) Writing an SRS, Foster, C.M. (1993). Analex Corporation for Glenn Research Center. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-190)
Fowler, M., 2005. Accessed July 22, 2011 from http://martinfowler.com/articles/newMethodology.html.(SWEREF-191)
Frank Buschman, Regine Meunier, Hans Rohnert, Peter Sommertad, and Michael Stal. Wiley, 1996.(SWEREF-192)
(SWEREF-193)
Ewen Denney (SGT NASA Ames), Bernd Fischer, July 2009.(SWEREF-194)
Federal Acquisition Regulation; FAR Case 2005-014, SmartBUY, A Proposed Rule by the Defense Department, the General Services Administration, and the National Aeronautics and Space Administration on 10/31/2007(SWEREF-195)
FAR 52.212-4 Contract Terms and Conditions-Commercial Items, Effective Date: 2021-07/2021-09-10,(SWEREF-196)
CMMI - Capability, Maturity Model, Integration, Version 2.0, See your SEPG for a NASA licensed copy.(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-198)
AIAA G-077. Reston, VA: AIAA. 1998. This document is avaible from AIAA; NASA has access to the AIAA website via the NASA START (AGCY NTSS) system (https://standards.nasa.gov ).(SWEREF-199)
MISRA Consortium, ISBN 0 9524156 2 3 (paperback), ISBN 0 9524156 4 X (PDF), October 2004.(SWEREF-200)
Hale, J.P.; Hartway, B.L.; Thomas, D.A. (2007). The 5th Joint Army-Navy-NASA-Air Force (JANNAF) Modeling and Simulation Subcommittee Meeting, May, CDJSC 49. Columbia, MD: Johns Hopkins University.(SWEREF-201)
Hammer, Huffman, Rosenberg (1998). CrossTalk Online,(SWEREF-202)
Harmon, S.Y.; Youngblood, S.M. (2005). Vol. 2, No. 4, pp. 179-190. Conference: Spring 2003 SISO Simulation Interoperability Workshop, At Kissimmee, FL(SWEREF-203)
Heller, Roger, Q/P Management Group, Inc. 2002,(SWEREF-204)
Hinchey, M., NASA Software Working Group, July 2006.(SWEREF-205)
John Kelly, 25th Annual Software Engineering Workshop, November 30, 2000, This is the presentation that introduced the Initiative and for the specific rationale for the Initiative.(SWEREF-206)
Hooks, Ivy F., Farry, Kirstin A., American Management Association, New York, 2001.(SWEREF-207)
Hower, Rick. (December, 2016), Software QA and Testing Resource Center,(SWEREF-208)
Hsieh, Paul., 2007. Accessed November 28, 2017 from http://www.azillionmonkeys.com/qed/optimize.html.(SWEREF-209)
IEEE Computer Society, IEEE Std 1012-2012 (Revision of IEEE Std 1012-2004), This link requires an account on the NASA START (AGCY NTSS) system (https://standards.nasa.gov ). Once logged in, users can access Standards Organizations, IEEE and then search to get to authorized copies of IEEE standards.(SWEREF-209)
IEEE Computer Society, IEEE Std 1012-2012 (Revision of IEEE Std 1012-2004), See Chapter 7. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-210)
IEEE Computer Society, IEEE Std 1471-2000 ( ISO/IEC 42010:2007), 2007. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-211)
IEEE Computer Society, IEEE STD 1059-1993, 1993. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-212)
IEEE Computer Society, IEEE STD 1042-1987, 1987. This link requires an account on the NASA START (AGCY NTSS) system (https://standards.nasa.gov ). Once logged in, users can access Standards Organizations, IEEE and then search to get to authorized copies of IEEE standards.(SWEREF-213)
IEEE Computer Society, IEEE Std 1062-1998, 1998. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-214)
IEEE Computer Society, IEEE STD 830-1998, 1998. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-215)
IEEE Computer Society, IEEE Std 829-2008, 2008. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-216)
IEEE STD IEEE 828-2012, 2012., NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-217)
IEEE 1058-1998, 1998. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-218)
IEEE 730-2002, 2002. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-219)
IEEE Std 1028, 2008. IEEE Computer Society, NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-220)
NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-221)
IEEE STD 1063-2001, 2001. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-222)
IEEE STD 610.12-1990, 1990. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-223)
ISO/IEC 16085, IEEE STD 16085-2006. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-224)
ISO/IEC 12207, IEEE Std 12207-2008, 2008. IEEE Computer Society, NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-224)
ISO/IEC 12207, IEEE Std 12207-2008, 2008. See Key section: Stakeholder Requirements Definition Process. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-224)
ISO/IEC 12207, IEEE Std 12207-2008, 2008. See Key section: Software Integration Process, Software Qualification Testing Process, Software Verification Process. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-225)
This link requires an account on the NASA START (AGCY NTSS) system (https://standards.nasa.gov ). Once logged in, users can access Standards Organizations, IEEE and then search to get to authorized copies of IEEE standards.(SWEREF-226) Informal surveys of personnel at the IV&V Facility, Fairmont, WV, Oct 2010.
(SWEREF-227)
NASA GRC-SW-TPLT-IDD, 2009.(SWEREF-228)
ISO/IEC 14764:2006, 2006. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-229)
NPR 7120.11A - Effective Date: September 08, 2020, Expiration Date: September 08, 2025(SWEREF-230)
ISO/IEC/IEEE 24765:2017 It was prepared to collect and standardize terminology. Copy attached.(SWEREF-231)
22 CFR §120.16(SWEREF-232)
Jayaswal, Bijay, and Patton, Peter. (2006). Developer.com.(SWEREF-233)
Jenkins, Nick (April, 2008). In The Project Management Hut. Retrieved February 29, 2012 from http://www.pmhut.com/traceability.(SWEREF-234) Software Stress-Testing Guide, JPL D-24472, NASA Jet Propulsion Laboratory (JPL), 2001. This NASA-specific information and resource may be available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-235)
John C. Kelly, Joseph S. Sherif, Jonathan Hops, NASA. Goddard Space Flight Center, Proceedings of the 15th Annual Software Engineering Workshop; 35 p(SWEREF-236)
Jones, Capers (1986), McGraw Hill, New York.(SWEREF-237)
Kannenberg, CrossTalkOnline, July/August 2009.(SWEREF-238)
Kuhl, J., (2002). Business eSolutions, Accessed Dec, 2017 from http://www.business-esolutions.com/islm.htm.(SWEREF-239)
Len Bass, Paul Clements, and Rick Kazman, 2003. Second Edition. Addison-Wesley.(SWEREF-240)
Lin, J.; West, J.S.; Williams, R.W.; Tucker, P.K. (2005). AIAA-2005-4524 .(SWEREF-241)
Wikipedia, The Free Encyclopedia.(SWEREF-242)
Livingston, Jr. P.E., Wiley F. (June, 2007). Software Technology Support Center (STSC), Hill AFB.(SWEREF-243) Simulation Project Software Configuration Management (SCM) Plan, Madden, Michael, Unisys Corporation for NASA Langley Research Center (LaRC), 1996. This is listed as a Best Practice on the LaRC PAL site (http://sw-eng.larc.nasa.gov/resource.cfm ). It is an example, not a practice/process. Note that it is from 1996 and it is based on IEEE Std 828-1990 which has been superseded by 828-2005. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-244)
Dr. Juha-Pekka Tolvanen, Embedded Systems Europe, August/September 2004.(SWEREF-245)
Dan Matheson, Robert France, James Bieman, Roger Alexander, James DeWitt, Nathan McEachen, OOPSLA & GPCE Workshop, 2004.(SWEREF-246)
NASA-STD-3000, Volume I, Revision B, NASA, 1995. See also Man-Systems Integration Standards, NASA-STD-3000, Volume II(SWEREF-247)
Marasco, Dr. Joe, 2007. In http://www.techtarget.com. Requires Free Membership to view content.(SWEREF-248)
NASA-HDBK-7009 Revision: A, Document Date: 2019-05-08, Next 5-Year Review Date: 2024-05-08(SWEREF-249)
McHale, John, Exec. Ed. (January, 2008). Military & Aerospace Electronics magazine. Title no longer available.(SWEREF-250)
Pedro Molina, Code Generation 2008. CAPGemini, Spain(SWEREF-251)
Mehta, U.B. (2007). The 5th Joint Army-Navy-NASA-Air Force (JANNAF) Modeling and Simulation Subcommittee Meeting, CDJSC 49, May, CPIAC. Columbia, MD: Johns Hopkins University.(SWEREF-252)
Mills, Everald E. (1988). Carnegie-Mellon University-Software Engineering Institute. Retrieved on December 2017 from http://www.sei.cmu.edu/reports/88cm012.pdf.(SWEREF-253)
(2012, March 16). In Wikipedia, The Free Encyclopedia. Retrieved December 2017 from http://en.wikipedia.org/w/index.php?title=Model-driven_engineering&oldid=482208649(SWEREF-254) MSFC Organizational Metrics Plan, EI32-OMP, Revision D, May 10, 2013. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-255) NASA Assurance Process for Complex Electronics: Traceability Analysis (2009, December 14). Link no longer valid last reviewed March 15, 2012 from http://www.hq.nasa.gov/office/codeq/software/ComplexElectronics/techniques/traceability-analysis.htm.
(SWEREF-256)
NPR 1400.1H, NASA Office of Internal Controls and Management Systems, Effective Date: March 29, 2019, Expiration Date: March 29, 2024(SWEREF-257)
NPD 7120.4E, NASA Office of the Chief Engineer, Effective Date: June 26, 2017, Expiration Date: June 26, 2022(SWEREF-257)
NPD 7120.4E, NASA Office of the Chief Engineer, Effective Date: June 26, 2017, Expiration Date: June 26, 2022(SWEREF-258)
Welcome to the Software Community. Software engineering is a core capability and a key enabling technology for NASA's missions and supporting infrastructure. Software Community site covers topics such as software requirements, design, implementation, architecture, assurance, testing, training, tools, process improvement, best practices, software release, models and simulations, and software research and technology innovation.(SWEREF-259)
The NFS is issued as Chapter 18 of Title 48, Code of Federal Regulations. The NFS has been modified through PN 19-05, dated June 11, 2019.(SWEREF-260)
This NASA-only resource is available to NASA-users at https://nen.nasa.gov/web/faultmanagement.(SWEREF-261)
NPD 1000.0C, NASA Governance and Strategic Management Handbook, Effective Date: January 29, 2020, Expiration Date: January 29, 2025(SWEREF-262)
NASA Headquarters NASA Office of the Chief Engineer engineering deviations and waivers website.(SWEREF-263)
NASA HQ OCE Letter. August 15, 2012.(SWEREF-264)
NPR 7120.7A, Office of the Chief Information Officer, Effective Date: August 17, 2020, Expiration Date: August 17, 2025 .(SWEREF-265)
NPR 7150.2B, Effective Date: November 19, 2014, Expiration Date: November 19, 2019 Copy attached to this SWEREF.(SWEREF-266)
This NASA-only resource is available to NASA users at https://nen.nasa.gov/web/software/nasa-software-process-asset-library-pal.(SWEREF-267)
NASA Procedural Requirements, NPR8715.3D, Effective Date: August 01, 2017, Expiration Date: August 01, 2022(SWEREF-268)
NPD 1440.6I, 2008. Effective Date: September 10, 2014(SWEREF-269)
NPR 7120.8A, NASA Office of the Chief Engineer, 2008, Effective Date: September 14, 2018, Expiration Date: September 14, 2023(SWEREF-270)
OSMA Website(SWEREF-271)
NASA STD 8719.13 (Rev C ) , Document Date: 2013-05-07(SWEREF-271)
NASA STD 8719.13 (Rev C ) , Document Date: 2013-05-07(SWEREF-272)
NASA STD 7009. Revision: A, Document Date: 2016-07-13(SWEREF-273)
NASA SP-2016-6105 Rev2 supersedes SP-2007-6105 Rev 1 dated December, 2007(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 6.2 Requirements Management.(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 3.8 Project Phase E: Operations and Sustainment, 3.9 Project Phase E: Closeout.(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 5.5 Product Transition.(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 7.1.5 Contract Completion.(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 6.5 Configuration Management.(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 6.7 Technical Assessment.(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 6.4 Technical Risk Management.(SWEREF-273)
NASA SP-2007-6105, Rev1, NASA Headquarters, 2007. See 4.2 Technical Requirements Definition.(SWEREF-274)
NASA-HDBK-8709.22. Baseline, 2018-03-08, Change 5: 2019-05-14(SWEREF-275)
NPR 7150.2A, Effective Date: November 19, 2009, Expiration Date: November 19, 2014 Copy attached to this SWEREF.(SWEREF-276)
NASA-GB-8719.13, NASA, 2004. Access NASA-GB-8719.13 directly: https://swehb-pri.msfc.nasa.gov/download/attachments/16450020/nasa-gb-871913.pdf?api=v2(SWEREF-277)
NASA-STD-8739.9, NASA Office of Safety and Mission Assurance, 2013. Change Date: 2016-10-07, Change Number: 1(SWEREF-278)
NASA-STD-8739.8B , NASA TECHNICAL STANDARD, Approved 2022-09-08 Superseding "NASA-STD-8739.8A,(SWEREF-278)
NASA-STD-8739.8B , NASA TECHNICAL STANDARD, Approved 2022-09-08 Superseding "NASA-STD-8739.8A,(SWEREF-279)
Dolores R. Wallace, Laura M. Ippolito, Barbara B. Cuthill, National Institute of Standards and Technology (NIST), NIST Special Publication 500-234, 1996.(SWEREF-280)
This NASA-only resource is available to NASA users at https://nen.nasa.gov/web/software/contacts.(SWEREF-281)
Jeffrey S. Norris , Jet Propulsion Laboratory, Poul-Henning Kamp (2004). IEEE Software.(SWEREF-282) Software Requirements Specification (SRS) Template, GRC-SW-TPLT-SRS, NASA Glenn Research Center, 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-283)
NPR 7150.2C, Effective Date: August 02, 2019, Expiration Date: August 02, 2024(SWEREF-284)
This topic contains spreadsheets for each class of software. For older versions of SWEHB, see SWE-125 and Topic 7.16 in the appropriate version.(SWEREF-285)
(SWEREF-286)
NPR 8715.3D - (w/Change 1 dated 8/01/17)(SWEREF-287)
Nurmuliani, N; Zowghi, Didar; Fowell, Sue. Proceedings of the 2004 Australian Software Engineering Conference, 2004, pp. 28 - 37, University of technology, Sydney, ASWEC'04, 2004.(SWEREF-288)
Oberkampf, W.L.; Pilch, M.; Trucano, T.G. (October 2007), SAND2007-5948. Sandia National Laboratories: Albuquerque, New Mexico 87185 and Livermore, California 94550.(SWEREF-289)
NESC Academy Software Discipline. Topics include software requirements, design, implementation, architecture, assurance, testing, training, tools, process improvement, best practices, software release, models and simulations, and software research and technology innovation.(SWEREF-289)
SWE-107 includes "DACUM" in its description in section 5, but the url is the same.(SWEREF-290) OCE Software Survey Instructions and Templates (on SPAN) This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook. 2010 Software Inventory instructions, version 7 (available from the OCE).
(SWEREF-291)
ISO/IEC 17021-1:2015 contains principles and requirements for the competence, consistency and impartiality of bodies providing audit and certification of all types of management systems. ISO 17021-1:2015(E) – Conformity assessment – Requirements for bodies providing audit and certification of management systems (accessible through the NASA Standards website (https://standards.nasa.gov) than searching the HIS Engineering Workbench)(SWEREF-292)
Oliver, D., Kelliher, T., Keegan, J., New York: McGraw-Hill, 1997.(SWEREF-293)
Open Source Initiative, September, 2010.(SWEREF-294)
The Safety and Mission Assurance (SMA) Technical Excellence Program (STEP) is a career-oriented, professional development roadmap for SMA professionals.(SWEREF-295)
Clements, P., et al. Addison-Wesley, 2011. Available for purchase at various locations.(SWEREF-296)
(2012). Software Engineering Institute (SEI). Carnegie-Mellon University. Retrieved April 13, 2012 from link listed here.(SWEREF-297)
Paul Goodman (1993). London: McGraw Hill. Available in ACM digital Library at: https://dl.acm.org/citation.cfm?id=541761(SWEREF-298)
Petlick, J., DePaul University, Chicago, IL. Accessed June 3, 2014 from http://condor.depaul.edu/~jpetlick/extra/394/Session2.ppt.(SWEREF-299)
Pettichord, Bret, editor (August, 2001). In PrismNet: The Complete Business Internet. Retrieved August 04, 2015 from http://www.prismnet.com/~wazmo/qa/.(SWEREF-300)
Piyush, J., Rao, DTV Ramakrishna, Balan, S. (May/June 2011), Crosstalk Online. Retrieved February 29, 2012 from http://www.crosstalkonline.org/storage/issue-archives/2011/201107/201107-Jain.pdf.(SWEREF-301)
Polydys, M. L. and Wisseman, S. (May 2007). CrossTalk The Journal of Defense Software Engineering, Vol. 20. No. 5 (14-18). Retrieved February 29, 2012 from http://www.crosstalkonline.org/storage/issue-archives/2007/200705/200705-0-Issue.pdf.(SWEREF-302)
Project Management Institute (2008).(SWEREF-303)
Robert Halligan, Project Performance International. (Expressing and Organizing Interface Information). Accessed November 3, 2014 from http://ppi-int.com/systems-engineering/irs-idd-icd-relationship.php.(SWEREF-304)
Raja, U.A. (February, 2009). IEEE Computer, control and Communication, 2009. 2nd International Conference. This link may require you to be logged in on your NASA network or to have an account on the NASA START (AGCY NTSS) system (https://standards.nasa.gov ). Once logged in, users can access Standards Organizations, IEEE and then search to get to authorized copies of IEEE standards. Retrieved on December 12, 2017.(SWEREF-305)
Ramzan, S., Ikram N., (December 2006). IEEE International Multitopic Conference 2006, 2006. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Retrieved on December 14, 2017 from http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4196410.(SWEREF-306) Reifer, D., (2000). A Poor Man 's Guide to Estimating Software Costs. 8th ed., Reifer Consultants, Inc.
(SWEREF-307) Requirements Management, GRC-SW-7150.6, Rev. D, Software Engineering Process Group, NASA Glenn Research Center, 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-308)
NASA-STD-8739.8 w/Change 1, July 28 2004 Replaced by NASA-STD-8739.8A - SWEREF-278 A PDF copy of this standard is attached to this SWEREF.(SWEREF-309) Robonaut 2 Risk Analysis and Waiver, NASA Johnson Space Center, 2010.
(SWEREF-310)
Royce, W., (1970). Proceedings of IEEE WESCON 26 (August): 1-9.(SWEREF-311)
Defense Modeling and Simulation Office. http://vva.dmso.mil/.(SWEREF-312)
Saltelli, A.; Chan, K.; Scott, E.M., eds. (2000). Chichester, England: John Wiley & Sons. Available via http://www.wiley.com/WileyCDA/WileyTitle/productCd-0471998923.html.(SWEREF-313)
Sangal, N., Waldman, F., Crosstalk Magazine, November, 2005(SWEREF-314)
Walt Scacchi, Institute for Software Research, University of California, Irvine, February 2001, Revised Version, May 2001, October 2001, Final Version to appear in, J.J. Marciniak (ed.), Encyclopedia of Software Engineering, 2nd Edition, John Wiley and Sons, Inc, New York, December 2001.(SWEREF-315)
Scott, J., Cyber Security & Information Systems Information Analysis Center, 3/11/2016.(SWEREF-316) Software Metrics Selection Presentation: A tutorial prepared for NASA personnel by the NASA Software Working Group and the Fraunhofer Center for Empirical Software Engineering College Park, MD. Seaman, Carolyn (2005) This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook. Retrieved on February 27, 2012 from https://nen.nasa.gov/web/software/nasa-software-process-asset-library-pal?.
(SWEREF-317) Best Practices for Effective Defect Tracking", 2008. Seapine Software was bought by Perforce http://downloads.seapine.com/pub/papers/DefectTrackingBestPractices.pdf
(SWEREF-318)
National Aeronautics and Space Administration Office of Procurement, December 16, 2016, The Government wide commercial purchase card is the preferred method of ordering and paying for micro-purchases.(SWEREF-319)
Shull, F., Basili, V. R., Boehm, B., Brown, A. W., Costa, P., Lindvall, M., Port, D., Rus, I., Tesoriero, R., and Zelkowitz, M. V., Proc. IEEE International Symposium on Software Metrics (METRICS02), pp. 249-258. Ottawa, Canada, June 2002.(SWEREF-320)
Shull., F., Feldmann, R., Seaman, C., Regardie, M., and Godfrey, S.,Innovations in Systems and Software Engineering - a NASA Journal, 2010. Available at: http://dx.doi.org/10.1007/s11334-010-0132-1.(SWEREF-321) COTS and Legacy Software Integration Issues, Smith, Dennis and Novak, Rhoda, Chairs. GSAW. February 26, 1998.
(SWEREF-322)
Brooks, Frederick P., Computer, Vol. 20, No. 4 (April 1987) pp. 10-19.(SWEREF-323)
The objectives of SARB are to manage and/or reduce flight software complexity through better software architecture and help improve mission software reliability and save costs.(SWEREF-324) Software Assurance Plan template, 2009. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-325) Software Change Request (SCR), NASA Glenn Research Center.
(SWEREF-326) Software Coding Standards Parasoft®. This document is not available but other development resources may be found at http://www.parasoft.com
(SWEREF-327)
Software Engineering Institute (SEI), architecture web site.(SWEREF-328)
Software Engineering Institute. (November, 2010). CMU/SEI-2010-TR-032. Carnegie-Mellon University. For SWE-035, see page 351 of this document. Retrieved on November 20, 2017 from http://www.sei.cmu.edu/reports/10tr032.pdf.(SWEREF-329)
Technical Report - NASA-GB-001-94 - Doc ID: 19980228474 (Acquired Nov 14, 1998), Software Engineering Program,(SWEREF-330)
NPR 7120.7A, Effective Date: August 17, 2020, Expiration Date: August 17, 2025(SWEREF-331) JPL Institutional Coding Standard for the C Programming Language Version: 1.0, Date: March 3, 2009, JPL DOCID D-60411 This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-332) Software Project Planning, GRC-SW-7150.3, Revision C, Software Engineering Process Group, NASA Glenn Research Center, 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook. Note: Revision Mark-up visible on this version.
(SWEREF-333) C CODING STANDARD GFSC - Flight Software Branch - Code 582, Version 1.1 - 11/29/05, 582-2000-005, This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-334)
Software Quality Assurance.org, Accessed December20, 2017.(SWEREF-335)
Software Quality Assurance.org, Accessed December 27, June 2017.(SWEREF-336)
Software Technology Support Center (STSC) (1995), Hill Air Force Base. Accessed 6/25/2019.(SWEREF-337)
Souppaya, Murugiah, Scarfone, Karen, NIST Special Publication NIST SP 800-40r4, April, 2022(SWEREF-338) C++ CODING STANDARD GSFC, Flight Software Branch - Code 582, Version 1.0 - 12/11/03, 582-2003-004 This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-339) Software Test Procedures (STPr) Template, GRC-SW-TPLT-STPr-2006, Software Engineering Process Group, NASA Glenn Research Center, 2006. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-340)
CMMI online Model Viewer gives you complete access and control over the full complement of CMMI V2.0 content. CMMI Process Quality Assurance (PQA) information available in CMMI model. CMMI Institute account needed to access this material.(SWEREF-341) Statement of Work (SOW) Review Procedure, LMS-CP-5523, Rev. B, Langley Research Center. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-342)
SMA-SA-WBT-230 SATERN (need user account to access SATERN courses). This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://saterninfo.nasa.gov/.(SWEREF-343)
This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://saterninfo.nasa.gov/.(SWEREF-344)
SATERN Need user account to access SATERN courses.This NASA-specific information and resource is available in at the System for Administration, Training, and Educational Resources for NASA (SATERN), accessible to NASA-users at https://saterninfo.nasa.gov/.(SWEREF-345)
Tarullo, Michael, L3 Communications, Crosstalk Magazine, Nov/Dec, 2011.(SWEREF-346)
NPR 8705.5A, NASA Office of Safety and Mission Assurance, 2010. Effective Date: June 07, 2010, Expiration Date: June 07, 2022(SWEREF-347)
Thakurta, Rahul; Ahlemann, Frederick, Proceedings of the 43rd Hawaii International Conference on System Sciences, 2010. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-348)
Thomas Tan, Barry Boehm, Brad Clark (2011), Systems Engineering Research Center, http://www.sercuarc.org/news/view/7.(SWEREF-349)
Thompson, Bernie. (2012). In Lean Software Engineering: Essays on the Continuous Delivery of High Quality Information Systems. Retrieved March 20 from http://leansoftwareengineering.com/wideband-delphi/.(SWEREF-350)
U.S. Department of Defense (1993). MIL-STD-882C, 1993. Note that MIL-STD-882D exists, but that the NASA Software Safety Guidebook recommends using MIL-STD-882C.(SWEREF-351)
U.S. Department of Defense (1997). Editor Note: Revision A is the reference. This URL is the download page for this document. The download is free.(SWEREF-352)
OSMA Web site,(SWEREF-353)
NPR 8705.6D, Effective Date: March 29, 2019, Expiration Date: March 29, 2024(SWEREF-354)
In Wikipedia, The Free Encyclopedia. (2012, January 28). Retrieved 18:33, March 19, 2012, from http://en.wikipedia.org/w/index.php?title=View_model&oldid=473612428(SWEREF-355)
Westfall, Linda, The Westfall Team (2005), Retrieved November 3, 2014 from http://www.win.tue.nl/~wstomv/edu/2ip30/references/Metrics_in_12_steps_paper.pdf(SWEREF-356)
Westfall, Linda, The Westfall Team (2006),(SWEREF-357)
Westfall, Linda, The Westfall Team (2007), Contains video slide presentation and copy companion paper.(SWEREF-358)
Wiegers, K. E. (May, 2000). Cutter IT Journal. Retrieved November 3, 2014 from http://www.processimpact.com/articles/telepathy.html.(SWEREF-359)
NASA/TP–2018–219822, J. Russell Carpenter, Goddard Space Flight Center, Greenbelt, Maryland, Christopher N. D’Souza, Johnson Space Center, Houston, Texas(SWEREF-360) Project Management and Systems Engineering Handbook, MSFC-HDBK-3173, Rev A, 2003. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-361)
NASA-STD-1006, with change 1, Approved: 2019-10-29 replaced by SWEREF-663(SWEREF-362)
Mission Resilience and Protection key document, Available in NEN, Mission Resilience and Protection Community of Practice. Formerly "Space Asset Protection"(SWEREF-363)
Wilmot, Jonathan, Fesq, Lorraine, Dvorak, Dan, Conference Paper, Publication Date March 5, 2016, GSFC-E-DAA-TN30323,(SWEREF-364) JPL Software Quality Improvement Project Initiation Plan, NASA Jet Propulsion laboratory, 2001. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-365)
Lopez, C., Cuadrado, J.J. and Sánchez-Alonso, S. (2007). In Proceedings of ONTOSE 2007 -Second International Workshop on Ontology, Conceptualizations and Epistemology for Software and Systems Engineering.(SWEREF-366)
JPL, Hihn, Jarius, Lum, Karen; 2000,(SWEREF-367)
IEEE Computer Society, Sponsored by the Software Engineering Standards Committee, IEEE Std 982.1™-2005, (Revision of IEEE Std 982.1-1988),(SWEREF-368) Software Version Description Template, GRC-SW-TPLT-SVD, 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-369)
Wagstaff, K., Benowitz, E. Byrne, D.J., Peters, K., Watney, G. (2008), NASA Jet Propulsion Lab (JPL). https://trs.jpl.nasa.gov/handle/2014/41374(SWEREF-370)
ISO/IEC/IEEE 15289:2017. NASA users can access ISO standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of ISO standards.(SWEREF-371)
Aerospace Standard 9101 Rev F, Quality Management Systems(SWEREF-372)
SAE AS9100D, ", 2016. NASA users can access standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of standards.(SWEREF-373)
NPR 2210.1C, Space Technology Mission Directorate, Effective Date: August 11, 2010, Expiration Date: January 11, 2022(SWEREF-373)
NPR 2210.1C, Space Technology Mission Directorate, Effective Date: August 11, 2010, Expiration Date: January 11, 2022 See page 9.(SWEREF-374) OCE Requirements Compliance Survey Process,Office of the Chief Engineer (OCE), NASA, 2010.
(SWEREF-375)
IEC 62304:2006, Medical device software — Software life cycle processes A copy of this standard is available from https://www.iso.org/standard/38421.html(SWEREF-376)
ISO 26262-1:2011, Road vehicles — Functional safety — Part 1: Vocabulary A copy of this standard is available from: https://www.iso.org/standard/43464.html(SWEREF-377)
NASA/TM?20205011566, NESC-RP-20-01515(SWEREF-378)
ISO/IEC/IEEE 15939:2017(en) NASA users can access ISO standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of ISO standards.(SWEREF-379)
NIST, SP 800-171 Rev. 2, February 2020 (includes updates as of January 28, 2021)(SWEREF-380) Software Risk Checklist, Flight Software Branch, Software Risk Management Plan, NASA Marshall Space Flight Center (MSFC). This is a list of generic risks organized by life cycle phase. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-381) Software Requirements Specification (SRS) Template, GRC-SW-TPLT-SRS, NASA Glenn Research Center, 2011. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA users from the SPAN tab in this Handbook.
(SWEREF-382)
NUREG/CR-6463, H. Hecht, M. Hecht, S. Graff, W Green, D. Lin, S. Koch, A. Tai, D. Wendelboe, SoHar Incorporated, U.S. Nuclear Regulatory Commission(SWEREF-383)
Model-based development environment for reliable embedded software, which provides linkage to requirements management, model-based design, verification, qualifiable/certified code generation capabilities and interoperability with other development tools and platforms.(SWEREF-384)
MCDC Checker source code implemented by GTD GmbH, tool to check all conditions in your C/C++ source code if they are in the necessary form, so that Gcov can generate modified condition decision coverage.(SWEREF-385)
OSMA, Curriculum Guide will help you plan your learning journey through STEP Levels 2, 3 and 4. It provides a detailed listing of all the courses and activities that comprise the curriculum for the STEP discipline you’ve chosen.(SWEREF-386)
NASA developed software eligible for reuse.(SWEREF-387) Software Reviews Handbook, JPL D-25798, Rev. 0, NASA Jet Propulsion Laboratory (JPL), 2005. in original SWEHB: SWE-052, SWE-055, SWE-072, SWE-111
(SWEREF-388)
Chrissis, M.B., et al. (March, 2011). SEI Series in Software Engineering. Addison-Wesley Professional.(SWEREF-389)
Course from APPEL: Academy of Program/Project & Engineering Leadership.(SWEREF-391)
Basili, V., Caldiera, G. and Rombach, H. D., Institute for Advanced Computer Studies, Department of Computer Science, University Of Maryland, College Park, Maryland. FB Informatik, Universität Kaiserslautern, Kaiserslautern, Germany.(SWEREF-392)
Park, R., Goethert, W., and Florac, W. CMU/SEI-96-HB-002.(SWEREF-393)
Couverture was an Open Source project financially supported by the French Government, the city of Paris and the Ile-de-France region The original Couverture project had the objectives to produce a Free Software coverage analysis toolset together with the ability to generate artifacts that allow the tools to be used for safety-critical software projects undergoing a DO-178B software audit process for all levels of criticality.(SWEREF-394)
Cyrille Comar, Jerome Guitton, Olivier Hainque, Thomas Quinot AdaCore, 46 rue d’Amsterdam, F-75009 PARIS (France), comar, guitton, hainque, quinot}@adacore.com, Embedded Real Time Software and Systems Conference, Feb 2012,(SWEREF-395) MC/DC for Space: A new Approach to Ensure MC/DC Structural Coverage with Exclusively Open Source Tools Thomas Wucher, Andoni Arregui, ESA Software Product Assurance Workshop 2021,
(SWEREF-396)
DOT/FAA/AR-01/18, US. Department of Transportation, Federal Aviation Administration, April 2001.(SWEREF-397)
Matteo Bordin, Cyrille Comar, Tristan Gingold, J´erˆome Guitton, Olivier Hainque, Thomas Quinot AdaCore, 46 rue d’Amsterdam, F-75009 PARIS (France) {bordin, comar, gingold, guitton, hainque, quinot}@adacore.com, Embedded Real Time Software and Systems Conference, May 2010(SWEREF-398)
Nelson, S. (2007). NASA CR-2003-212806.(SWEREF-399)
Earls, M.R. and Sitz, J.R. (1989). NASA TM-101703.(SWEREF-400)
Welch, J.W. (2010). Aerospace Report No. TOR-2010(8591)-20.(SWEREF-401)
Federal Aviation Administration (FAA), December, 1999. DI-IPSC-81438A,(SWEREF-402)
NASA Office of the Chief Information Officer, May, 2015. NPD 2810.1E,(SWEREF-403)
NPR 2810.1F, Office of the Chief Information Officer, Effective Date: January 03, 2022, Expiration Date: January 03, 2027,(SWEREF-404)
Website. October, 2011.(SWEREF-405)
Issue 1, Revision 1, ESA Board for Software Standardization and Control, 1995. FOR SECURITY REASONS, ALL LINKS TO THE ftp.estec.esa.int SERVER ARE DISABLED. YOU MAY REQUEST RELATED DOCUMENTS TO bssc@esa.int(SWEREF-406)
January, 2012. This is a list of the NASA Requirement Waivers. Instructions for submitting requirement waivers are outlined in Chapter 4 of NPR 1400.1, NASA Directives Procedural Requirements.(SWEREF-407) Software Test Description and Results. University of Southern California, Center for Systems and Software Engineering. January 30, 1997.
(SWEREF-408)
Gemini 1962. NASA. 2005. See Chapter One - The Gemini Digital Computer: First Machine in Orbit.(SWEREF-409)
In the Apollo 11 Lunar Surface Journal. Peter Adler. NASA. 1998. See section on computer restarts.(SWEREF-410)
Academy of Program/Project & Engineering Leadership (APPEL).(SWEREF-411)
NASA IV&V Facility.(SWEREF-412) Measurement Planning Table This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-413)
(SWEREF-414)
Babula, M. et al. (2008). Published Online:15 Jun 2012 https://doi.org/10.2514/6.2009-1011(SWEREF-415)
See also Man-Systems Integration Standards, NASA-STD-3000, Volume I.(SWEREF-416)
Collaris, R.A. and Dekker, E. (March 15, 2009). IBM. Developer Works website.(SWEREF-417)
Holzmann, G.J., NASA Jet Propulsion Laboratory (JPL), 2006.(SWEREF-418)
Denney, E., NASA Ames, 2008. Related: https://ti.arc.nasa.gov/m/profile/edenney/papers/Denney-BigSky-08.pdf(SWEREF-419)
GAO-09-3SP. United States Government Accountability Office. Applied Research and Methods. March, 2009.(SWEREF-420)
NASA Safety Center. Safety Training Courses.(SWEREF-421) "A collection of checklists for different purposes," Fraunhofer USA, The University of Maryland. This web page contains several resources for performing software inspections.
(SWEREF-422)
Code Q-1, NASA Headquarters, February, 2001. Contains reports from 2004 through 2018(SWEREF-423)
NASA Office of the Inspector General, March 28, 2003. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook. See Recommendations for Corrective Action, #1(SWEREF-424)
NASA Langley Research Center (LaRC), August 20, 2004. Lessons Learned Reference. (See pages 45-56)(SWEREF-425)
International Space Station, Multilateral Coordination Board, NASA Kennedy Space Center (KSC), July 22, 2009. Lessons Learned Reference.(SWEREF-426)
Office of the Secretary of Defense, June 26, 2000. Lessons Learned Reference.(SWEREF-427)
(2012, April 27). In National Archives. http://www.archives.gov/.(SWEREF-428)
German, A. (November 2003). In CrossTalk The Journal of Defense Software Engineering, Archives. Lessons Learned Reference.(SWEREF-429)
Jain, P. et al. (July/August 2011). In CrossTalk The Journal of Defense Software Engineering, Archives. Lessons Learned Reference.(SWEREF-430)
Basili, V.R., et al. (May, 2002). University of Maryland, College Park. Experimental Software Engineering Group (ESEG). Lessons Learned Reference.(SWEREF-431)
(2012). Software Program Managers Network (SPMN) Lessons Learned Reference.(SWEREF-432)
For Public Release. (2006). Lessons Learned Reference.(SWEREF-433)
Rosenberg, Dr. Linda H. NASA Goddard Space Flight Center (GSFC). In Journal of Software Technology, Vol. 6, Number 2. October, 2003. Lessons Learned Reference.(SWEREF-434)
Thomas Wucher, Andoni Arregui, 2021-10-07, ESA Software Product Assurance Workshop 2021, GTD GmbH(SWEREF-435)
(SWEREF-436)
(SWEREF-437)
(SWEREF-438)
NPR 7150.2C, Effective Date: August 02, 2019(SWEREF-439)
The NASA Lessons Learned system. The system provides access to official, reviewed lessons learned from NASA programs and projects.(SWEREF-440)
(SWEREF-441)
(SWEREF-442)
NASA users must LOGIN to fully access the NTSS.: https://standards.nasa.gov/(SWEREF-443) Topic 7.16 - Appendix C. Requirements Mapping and Compliance Matrix
(SWEREF-444)
Rosenberg, Linda H. (Oct, 2003). Journal of Software Technology.(SWEREF-445) Orbital Space Program Lessons Learned, Realistic and Integrated Schedule, Lesson Number OSP.01.0042, NASA, Agency IHM Team, March 29, 2004. Lesson Number OSP.01.0042, NASA, Agency IHM Team, March 29, 2004.
(SWEREF-446)
Software Program Managers Network, http://www.spmn.com(SWEREF-447)
IVV 09-1, Version: P, Effective Date: February 26, 2016, Based in NPR7150.2B. The official version of this document is maintained in IV&V's internal IV&V Management System Website (https://confluence.ivv.nasa.gov:8445/display/IMS).(SWEREF-448) Software Process Improvement Plan EI32-SPIP, Revision F, NASA Marshall Space Flight Center (MSFC) Flight Software Branch, 10-26-2010. Replaces SWEREF-058
(SWEREF-449) Requirements Peer Review Checklist, 580-CK-057-02, Software Engineering Division (SED), NASA Goddard Space Flight Center (GSFC), 2012. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-450) SED Software Quality and IV&V Support Planning Guidelines, 580-GL-030-02, Software Engineering Division (SED), NASA Goddard Space Flight Center (GSFC), 2012. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook. Replaces SWEREF-229
(SWEREF-451) SED Test Description Guideline, 580-GL-063-02, Software Engineering Dvision, NASA Goddard Space Flight Center (GSFC), 2012. Replaces SWEREF-080
(SWEREF-452) SED Unit Test Guideline, 580-GL-062-02, Systems Engineering Division, NASA Goddard Space Flight Center (GSFC), 2012. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook. Replaces SWEREF-081
(SWEREF-453) Project Planning Process, 580-PC-004-07, Software Engineering Division (ISD), NASA Goddard Space Flight Center (GSFC), 2020. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-454) Prepare Presolicitation Documents, Revision Q, LMS-OP-4509, Langley Research Center (LaRC) Office of Procurement, 2010. Replaces SWEREF-002 This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-455)
ISO/IEC 9646-3:1998. Must be purchased from the International Organization for Standardization (ISO); no free copy or access via NASA Technical Standards site available.(SWEREF-456)
Doxygen is the de facto standard tool for generating documentation from annotated C++ sources, but it also supports other popular programming languages such as C, Objective-C, C#, PHP, Java, Python, IDL (Corba, Microsoft, and UNO/OpenOffice flavors), Fortran, VHDL, Tcl, and to some extent D.(SWEREF-457)
The link will generate a current list of Organizational Units which have completed and reported SCAMPI Class A appraisals against the CMMI or People CMM Model. Documented authorization has been received from the sponsor of each posted appraisal for this release of information.(SWEREF-458) NPR 7150 traced to NPR 7123 and NPR 7120_20100716_V2 This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-459) NPR 7150 traced to NASA-STD-8739 8 and NASA-STD-8719 13B_20100924 This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-460) NPR 7150 traced to NASA-STD-8739 8 and NASA-STD-8719 13B_20100924 This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-461)
Jairus Hihn and Hamid Habib-agahi, Jet Propulsion Lab., California Inst. of Technol., Pasadena, CA. 1991.(SWEREF-462)
© 2014 Black Duck Software, Inc.(SWEREF-463) Verification and Validation Document: Plan and Report for the System X GFE, Johnson Space Center, 2012.
(SWEREF-464)
NASA IV&V Program(SWEREF-465)
Ewen Denney, Bernd Fischer, November 2009, accessed on April 21, 2014.(SWEREF-466)
Andrew Burnard, Land Rover, 2004, accessed on March 25, 2014.(SWEREF-468)
Wetherholt, Martha. CrossTalk - Journal of Defense Software Engineering, Sep/Oct, 2015. Retrieved October 08, 2015 from http://www.crosstalkonline.org/storage/flipbooks/2015/201509/index.html. See page 31.(SWEREF-469)
IEEE Std 730: 2014, 2014. NASA users can access IEEE standards via the NASA Technical Standards System located at https://standards.nasa.gov/. Once logged in, search to get to authorized copies of IEEE standards.(SWEREF-470)
NASA/SP-2014-3705, NASA, September, 2014.(SWEREF-471) Report Concerning Space Data System Standards, Security Threats Against Space Missions, Green Book, Issue 1, CCSDS 350.1-G-1, Consultative Committee for Space Data Systems (CCSDS), October 2006. No longer available from resource: https://public.ccsds.org/publications/greenbooks.aspx
(SWEREF-472)
Green Book, Issue 2, CCSDS 350.1-G-2, Consultative Committee for Space Data Systems (CCSDS), December 2015. From site: https://public.ccsds.org/publications/greenbooks.aspx.(SWEREF-473)
Wilson, Tom, Space Commission Staff Member. Prepared for the Commission to Assess United States National Security Space Management and Organization.Retrieved 12:15 PM August 5, 2015 from http://fas.org/spp/eprint/article05.html.(SWEREF-474)
Basili, V., Green , S., Laitenberger, O., Lanubile, F., Shull, F., Soerumgaard, S., and Zelkowitz, M. Empirical Software Engineering: An International Journal, 1(2): 133-164, 1996.(SWEREF-475)
website http://www.dcma.mil/. Accessed January, 2018.(SWEREF-476)
Michael Aguilar, NASA Engineering and Safety Center, October 21, 2014.(SWEREF-477)
Klaus Havelund and Gerard J. Holzmann Laboratory for Reliable Software (LaRS) Jet Propulsion Laboratory, California Institute of Technology 4800 Oak Grove Drive, Pasadena, California, 91109-8099.(SWEREF-478)
Aerospace Report No. TOR-2004(3909)-3537, Revision B, March 11, 2005.(SWEREF-479)
Marshall, James. And Downs, Robert, IEEE, 2008. Retrieved from http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4779626 on August 19, 2015.(SWEREF-480)
Downs, Robert and Marshall, James. Data Science Journal, Volume 9, July 24, 2010.(SWEREF-481)
Stewart, David (1999).(SWEREF-482)
Joh, HyunChul and Malaiya, Yashwant K.(2010). Colorado State University. Retrieved November 11, 2014 from http://www.cs.colostate.edu/~malaiya/p/joh.risk.2010.pdf.(SWEREF-483)
Douglas A. Ashbaugh, Software Engineering Services (2006). CrossTalk Online. Retrieved November11, 2014 from http://www.crosstalkonline.org/storage/issue-archives/2006/200609/200609-Ashbaugh.pdf.(SWEREF-484)
Paul R. Croll, CSC (2011). CrossTalk Online. Retrieved November 11, 2014 from http://www.crosstalkonline.org/storage/issue-archives/2012/201203/201203-croll.pdf. The 2012 CrossTalk article included this note, “© 2011 IEEE. Reprinted, with permission, from the Proceedings of the 5th Annual IEEE Systems Conference, April 2011”.(SWEREF-485)
Michael Atighetchi and Dr. Joseph Loyall, Raytheon bBN Technologies (2010). CrossTalk Online. Retrieved November 11, 2014 from http://www.crosstalkonline.org/storage/issue-archives/2010/201003/201003-Atighetchi.pdf.(SWEREF-486)
(SWEREF-487)
ISO/IEC/IEEE 42010:2011, 2011. Accessed at 10:19 on August 27, 2015 from http://www.iso-architecture.org/ieee-1471/.(SWEREF-488)
NASA/SP-2010-3403, NASA Headquarters, January 2010.(SWEREF-489)
NPD 1000.5C, Policy for NASA Acquisition, Effective Date: July 13, 2020, Expiration Date: July 13, 2025(SWEREF-490)
Academy of Program/Project and Engineering Leadership (APPEL). Retrieved on September 14, 2015 from http://appel.nasa.gov/about-us/history/.(SWEREF-491)
Access the APPEL curriculum catalog from this URL.(SWEREF-492)
Mil-Standard, DI-IPSC-81435. U.S. Navy. December 15, 1999.(SWEREF-493)
RTCA DO-178C, January 5, 2012(SWEREF-494)
Douglas A. Ashbaugh, Software Engineering Services (2006). Retrieved November 11, 2014 from http://www.crosstalkonline.org/storage/issue-archives/2006/200609/200609-Ashbaugh.pdf.(SWEREF-495)
Arlene F. Minkiewicz, PRICE Systems (2005). Retrieved November 11, 2014 from http://www.crosstalkonline.org/storage/issue-archives/2005/200511/200511-Minkiewicz.pdf.(SWEREF-496)
C. Warren Axelrod, Delta Risk (2014). Retrieved November 11, 2014 from http://www.crosstalkonline.org/storage/issue-archives/2014/201403/201403-Axelrod.pdf(SWEREF-497) MSFC Flight & Ground Software Division (ES50) Organizational Metrics Plan, EI32-OMP Revision D April 29, 2013. This NASA-specific information and resource is available in Software Processes Across NASA (SPAN), accessible to NASA-users from the SPAN tab in this Handbook.
(SWEREF-498)
NASA-STD_3001, Volume 2: Human Factors, Habitability, and Environmental Health, Revision A, 2015.(SWEREF-499)
Software Engineering Institute website. Carnegie-Mellon University. Retrieved July, 2016 from http://www.sei.cmu.edu/architecture/tools/document/viewsandbeyond.cfm.(SWEREF-500)
Public Lessons Learned Entry: 272.(SWEREF-501)
Public Lessons Learned Entry: 310.(SWEREF-502)
Public Lessons Learned Entry: 331.(SWEREF-503)
Public Lessons Learned Entry: 332.(SWEREF-504)
Public Lessons Learned Entry: 343.(SWEREF-505)
Public Lessons Learned Entry: 345.(SWEREF-506)
Public Lessons Learned Entry: 391.(SWEREF-507)
Public Lessons Learned Entry: 403.(SWEREF-508)
Public Lessons Learned Entry: 569.(SWEREF-509)
Public Lessons Learned Entry: 582.(SWEREF-510)
Public Lessons Learned Entry: 590.(SWEREF-511)
Public Lessons Learned Entry: 608.(SWEREF-512)
Public Lessons Learned Entry: 625.(SWEREF-513)
Public Lessons Learned Entry: 641.(SWEREF-514)
Public Lessons Learned Entry: 655.(SWEREF-515)
Public Lessons Learned Entry 657.(SWEREF-516)
Public Lessons Learned Entry: 667.(SWEREF-517)
Public Lessons Learned Entry: 707.(SWEREF-518)
Public Lessons Learned Entry: 723.(SWEREF-519)
Public Lessons Learned Entry: 733.(SWEREF-520)
Public Lessons Learned Entry: 738.(SWEREF-521)
Public Lessons Learned Entry: 740.(SWEREF-522)
Public Lessons Learned Entry: 772.(SWEREF-523)
Public Lessons Learned Entry: 790.(SWEREF-524)
Public Lessons Learned Entry: 803.(SWEREF-525)
Public Lessons Learned Entry: 835.(SWEREF-526)
Public Lessons Learned Entry: 838.(SWEREF-527)
Public Lessons Learned Entry: 839.(SWEREF-528)
Public Lessons Learned Entry: 921,(SWEREF-529)
Public Lessons Learned Entry: 938.(SWEREF-530)
Public Lessons Learned Entry: 939.(SWEREF-531)
Public Lessons Learned Entry: 987.(SWEREF-532)
Public Lessons Learned Entry: 1021.(SWEREF-533)
Public Lessons Learned Entry: 1023.(SWEREF-534)
Public Lessons Learned Entry: 1024.(SWEREF-535)
Public Lessons Learned Entry: 1048.(SWEREF-536)
Public Lessons Learned Entry: 1062.(SWEREF-537)
Public Lessons Learned Entry: 1104.(SWEREF-538)
Public Lessons Learned Entry: 1106.(SWEREF-539)
Public Lessons Learned Entry: 1122.(SWEREF-540)
Public Lessons Learned Entry: 1128.(SWEREF-541)
Public Lessons Learned Entry: 1130.(SWEREF-542)
Public Lessons Learned Entry: 1132.(SWEREF-543)
Public Lessons Learned Entry: 1153.(SWEREF-544)
Public Lessons Learned Entry: 1173.(SWEREF-545)
Public Lessons Learned Entry: 1197.(SWEREF-546)
Public Lessons Learned Entry: 1213.(SWEREF-547)
Public Lessons Learned Entry: 1281.(SWEREF-548)
Public Lessons Learned Entry: 1294.(SWEREF-549)
Public Lessons Learned Entry: 1321.(SWEREF-550)
Public Lessons Learned Entry: 1346.(SWEREF-551)
Public Lessons Learned Entry: 1370.(SWEREF-552)
Public Lessons Learned Entry: 1384.(SWEREF-553)
Public Lessons Learned Entry: 1414.(SWEREF-554)
Public Lessons Learned Entry: 1448.(SWEREF-555)
Public Lessons Learned Entry: 1457.(SWEREF-556)
Public Lessons Learned Entry: 1481.(SWEREF-557)
Public Lessons Learned Entry: 1483.(SWEREF-558)
Public Lessons Learned Entry: 1499.(SWEREF-559)
Public Lessons Learned Entry: 1501.(SWEREF-560)
Public Lessons Learned Entry: 1504.(SWEREF-561)
Public Lessons Learned Entry: 1529.(SWEREF-562)
Public Lessons Learned Entry:2044. In NASA Engineering Network. Retrieved March 31, 2015 from http://llis.nasa.gov/lesson/2044.(SWEREF-563)
Public Lessons Learned Number: 24503, Lesson Date 2018-08-23, Submitting Organization: NESC,(SWEREF-564)
Public Lessons Learned Entry:3556. In NASA Engineering Network. Retrieved March 31, 2015 from http://llis.nasa.gov/lesson/3556. points to same URL as SWE-577(SWEREF-565)
Public Lessons Learned Entry: 609.(SWEREF-566)
Public Lessons Learned Entry: 1715.(SWEREF-567)
Public Lessons Learned Entry: 1772.(SWEREF-568)
Public Lessons Learned Entry: 1799.(SWEREF-569)
Public Lessons Learned Entry:1805. In NASA Engineering Network. Retrieved March 31, 2015 from http://llis.nasa.gov/lesson/1805.(SWEREF-570)
Public Lessons Learned Entry:1807. In NASA Engineering Network. Retrieved March 31, 2015 from http://llis.nasa.gov/lesson/1807.(SWEREF-571)
Public Lessons Learned Entry: 2050.(SWEREF-572)
Public Lessons Learned Entry: 2218.(SWEREF-573)
Public Lessons Learned Entry: 2419.(SWEREF-574)
Public Lessons Learned Entry: 2476.(SWEREF-575)
Public Lessons Learned Entry:2816. In NASA Engineering Network. Retrieved March 31, 2015 from http://llis.nasa.gov/lesson/2816.(SWEREF-576)
Public Lessons Learned Entry: 3377.(SWEREF-577)
Public Lessons Learned Entry: 3556.(SWEREF-578)
Public Lessons Learned Entry: 3716.(SWEREF-579)
Lessons Learned Entry: 991.(SWEREF-580) COTS Change Processing Lessons Learned Entry:3457. No longer available
(SWEREF-581)
CAMS 10188. In NASA Engineering Network.(SWEREF-582)
Public Lessons Learned Entry: 377.(SWEREF-583)
Public Lessons Learned Entry: 1024.(SWEREF-584)
Public Lessons Learned Entry: 6656.(SWEREF-585)
In NASA Engineering Network.(SWEREF-586)
Public Lessons Learned Entry: 559.(SWEREF-587)
Public Lessons Learned Entry: 2158.(SWEREF-588)
Public Lessons Learned Entry: 4516.(SWEREF-589)
Public Lessons Learned Entry: 8501.(SWEREF-590)
Public Lessons Learned Entry: 1148.(SWEREF-591)
Public Lessons Learned Entry: 1133.(SWEREF-592)
Public Lessons Learned Entry: 2158.(SWEREF-593)
NPD 1200.1E, Office of the Chief Financial Officer, Effective Date: July 21, 2008, Expiration Date: July 21, 2022,(SWEREF-594)
NPD 1210.2, Office of the Chief Financial Officer, Effective Date: January 13, 2005, Expiration Date: October 24, 2023,(SWEREF-595)
NPD 2091.1C, Office of the General Counsel, Effective Date: May 24, 2018, Expiration Date: May 24, 2023,(SWEREF-596)
NASA Policy Directive, NPD 7120.6 Effective Date: November 26, 2013, Expiration Date: November 26, 2018(SWEREF-597)
NPR 2190.1C, NASA Procedural Requirements, Effective Date: September 08, 2017, Expiration Date: September 08, 2022(SWEREF-598)
NPD 2800.1E, Office of the Chief Information Officer, Effective Date: December 09, 2019, Expiration Date: December 09, 2024,(SWEREF-599)
NASA Procedural Requirements, NPR 2841.1, Effective Date: January 06, 2011, Expiration Date: January 06, 2022, (Revalidated w/change 1)(SWEREF-600)
NASA Procedural Requirements, NPR 7120.10A, Effective Date: February 21, 2017, Expiration Date: February 21, 2022(SWEREF-601)
48 CFR Ch. 18 (10–1–05 Edition) 1852.227–86(SWEREF-602)
NASA FAR Sup 1812(SWEREF-603)
Carnegie Mellon University course 18-642 updated Fall 2020, Koopman, Phil(SWEREF-604)
NPR 9420.1A, Effective Date: September 07, 2016, Expiration Date: September 07, 2021(SWEREF-605)
Office of Procurement, NASA Headquarters, Washington, DC 20546, September 2014(SWEREF-606)
NASA-STD-2804 — Fall 2017, Approved: February 9, 2018 , Superseding NASA-STD-2804, Spring 2017(SWEREF-607)
NFS is issued as Chapter 18 of Title 48, Code of Federal Regulations. The NFS has been modified through PN 18-15, dated August 21, 2018(SWEREF-608)
NPD 9250.1A, Effective Date: October 08, 2010, Expiration Date: October 08, 2024, NASA policy for property, plant, and equipment (PP&E)(SWEREF-609)
IVV 09-4, Version: AG, Effective Date: June 24, 2014, The official version of this document is maintained in IV&V's internal IV&V Management System Website (https://confluence.ivv.nasa.gov:8445/display/IMS).(SWEREF-610)
IVV 09-9, Version: D, Effective Date: January 27, 2016 The official version of this document is maintained in IV&V's internal IV&V Management System Website (https://confluence.ivv.nasa.gov:8445/display/IMS).(SWEREF-611)
IVV 22, Version: H, Effective Date: October 16, 2017 The official version of this document is maintained in IV&V's internal IV&V Management System Website (https://confluence.ivv.nasa.gov:8445/display/IMS).(SWEREF-612)
S3001, Version: G, Effective Date: October 16, 2017 The official version of this document is maintained in IV&V's internal IV&V Management System Website (https://confluence.ivv.nasa.gov:8445/display/IMS).(SWEREF-613)
S3105, Version: K, Effective Date: March 20, 2017 The official version of this document is maintained in IV&V's internal IV&V Management System Website (https://confluence.ivv.nasa.gov:8445/display/IMS).(SWEREF-614)
S3106, Version: D, Effective Date: October 4, 2012 The official version of this document is maintained in IV&V's internal IV&V Management System Website (https://confluence.ivv.nasa.gov:8445/display/IMS).(SWEREF-615)
Alfred Spector, David Gifford Alternate source for article in ACM: https://dl.acm.org/citation.cfm?id=358246 Communications of the ACM 27 (1984): 874-900(SWEREF-616)
Knight , John C. ; Leveson, Nancy G., Also available from IEEE: https://ieeexplore.ieee.org/document/6312924(SWEREF-617)
Brilliant, Susan S. , Virginia Commonwealth Univ., Richmond, Knight, John C. ,Univ. of Virginia, Charlottesville, Leveson, Nancy G. ,Univ. of California, Irvine, IEEE Transactions on Software Engineering archive, Volume 16 Issue 2, February 1990, Page 238-247 Also available: https://dl.acm.org/citation.cfm?id=78716(SWEREF-618)
Butler, Ricky W., Caldwell, James L. , Carreno, Victor A., Holloway, C. Michael, Miner, Paul S. (NASA Langley Research Center, Hampton, VA, United States); DiVito, Ben L., (Vigyan Research Associates, Inc., Hampton, VA, United States)(SWEREF-619)
NUREG-0492,(SWEREF-620)
DOD-STD-2167A Military Standard, (this document has been replaced by DOD-STD-498, which was cancelled in 1998 when IEEE 12207 was released) https://standards.ieee.org/standard/12207-2017.html(SWEREF-621) JPL Software Systems Safety Handbook SSSHB 3.2/Draft JPL Software Systems Safety Handbook
(SWEREF-622)
N. G. Leveson, Journal of Spacecraft and Rockets, vol. 41, no. 4, pp. 564–575, Jul. 2004(SWEREF-623)
Cook, Dr. David A. ; Skinner, Dr. James M.; The AEgis Technologies Group, Inc.(SWEREF-624)
Report by the Inquiry Board, The Chairman of the Board : Prof. J. L. LIONS(SWEREF-625)
Leveson, N. G. and Turner, C. S. ; Computer (Long. Beach. Calif)., vol. 26, no. 7, pp. 18–41, Jul. 1993.(SWEREF-626)
Alexander, Ian; IEEE Softw., vol. 20, no. 1, pp. 58–66, Jan. 2003.(SWEREF-627)
T. Ishimatsu, N. G. Leveson, J. P. Thomas, C. H. Fleming, M. Katahira, Y. Miyamoto, R. Ujiie, H. Nakao, and N. Hoshino, J. Spacecr. Rockets, vol. 51, no. 2, pp. 509–522, Mar. 2014(SWEREF-628)
Leveson, Nancy ; Version 1, August 2013 The old STPA Primer (2013) has been replaced by the STPA Handbook (2018), which provides updated guidance and more information. See http://mit.edu/psas to download a free copy of the STPA Handbook.(SWEREF-629)
John C. Day, Kenneth Donahue , Michel Ingham, Alex Kadesch, Andrew K. Kennedy and Ethan Post; Jet Propulsion Laboratory, California Institute of Technology, Pasadena, CA, 91109(SWEREF-630)
S. J. Prowell and J. H. Poore, IEEE Transactions on Software Engineering, vol. 29, no. 5, pp. 417-429, May 2003,(SWEREF-631)
A. K. Ghosh and J. M. Voas, Commun. ACM, vol. 42, no. 7, pp. 38–44, Jul. 1999.(SWEREF-632)
A. K. Ghosh and M. Schmid, in Proceedings 10th International Symposium on Software Reliability Engineering (Cat. No.PR00443), 1999, pp. 166–174.(SWEREF-633)
R. Binder; Addison-Wesley Professional, 2000.(SWEREF-634)
Vignir Gudmundsson , Christoph Schulze, Dharmalingam Ganesan, Mikael Lindvall and Robert Wiegand; Innovations in Systems and Software Engineering, Volume (ISSE), Vol 11, Number 3, 217—232, 2015(SWEREF-635)
Christoph Schulze, Dharmalingam Ganesan, Mikael Lindvall, Rance Cleaveland, Daniel Goldman; ICSE Companion 2014: 135-144(SWEREF-636)
Christoph Schulze, Mikael Lindvall, Sigurthor Bjorgvinsson, Robert Wiegand; ISSRE 2015: 77-87(SWEREF-637) Improving model based testing to detect off-nominal Behaviors, Christoph Schulze, Mikael Lindvall, Dharmalingam Ganesan, Arnab Ray; Fraunhofer Technical Report, December 2015. Available upon request from Fraunhofer.
(SWEREF-638)
yEd is a powerful desktop application that can be used to quickly and effectively generate high-quality diagrams(SWEREF-639)
JUnit is a unit testing framework for the Java programming language. JUnit has been important in the development of test-driven development, and is one of a family of unit testing frameworks which is collectively known as xUnit that originated with SUnit(SWEREF-640)
GraphWalker, an open-source model-based testing tool(SWEREF-641)
Selenium automates browsers.(SWEREF-642)
Goddard Mission Services Evolution Center (GMSEC)(SWEREF-643)
Tutorials Point, Simply Easy Learning web site(SWEREF-644)
Benowitz, Ed, and Chris Swan. 2014(SWEREF-645)
Cox, Jake; 2010 IV&V Annual Workshop, September 2010,(SWEREF-646)
Gibson, C., Karban, R., Andolfato, L., and Day, J., 2014 ACM SIGSOFT Software Engineering Notes, 39(1), 1-5, 2014,(SWEREF-647)
Goseva-Popstojanova, K., Kahsai, T., Kyanko, T., Nkwocha, N., Knudson, M., and Schumann, J., September 2016. NASA report, TM-2016-219443,(SWEREF-648)
Henry, J., 2011. Document Number: FlyDyb-CEV-8-148, 2011.(SWEREF-649)
The Orion Guidance, Navigation, and Control MATLAB and Simulink Standards document describes the modeling standards and guidelines that the Orion Crew Exploration Vehicle (CEV) Flight Dynamics Team (FDT) are using while developing and coding the GN&C algorithms using Simulink, Stateflow, MATLAB language for code generation, and Embedded Coder.(SWEREF-650)
Rouquette, N.F., Neilson, T., and Chen, G., 1999. Proceedings of the 1999 IEEE Aerospace Conference,Vol 1, March 1999, pp. 477-487.(SWEREF-651)
Wagstaff, K. L., Benowitz, E., Byrne, D. J., Peters, K., and Watney, G., 2008. Jet Propulsion Laboratory, California Institute of Technology(SWEREF-652)
Tomassetti, G., (blog), May 9, 2018.(SWEREF-653)
Hinchey, M.G., Rash, J., and Rouff, C.A., 2005. NASA-TM-2005-212774.(SWEREF-654)
Jackson, M. C., & Henry, J. R., AIAA Guidance, Navigation and Control Conference, 2012. Also available from the NASA Technical Reports Server, Document ID: 20120013073.(SWEREF-655)
Klein, J., Levinson, H., and Marchetti, J., Technical Report CMU/SEI-2015-TN-005, March 2015.(SWEREF-656)
Liebel, G., Marko, N., Tichy, M., Leitner, A., and Hansson, J., 2016, Software & Systems Modeling, 1-23, 2016.(SWEREF-657)
Odegard, R., Milenkovic, Z., Henry, J., & Buttacoli, M., IEEE Aerospace Conference, (pp. 1-13). IEEE, 2014. Available from the NASA Technical Reports Server, Document ID: 20140003581.(SWEREF-658)
Oh, J. M., Watney, G. J., and Benowitz, E. G., IEEE Aerospace Conference, (pp. 1-6), IEEE, 2008.(SWEREF-659)
Tamblyn, S., Henry, J., & King, E., IEEE Aerospace Conference, (pp. 1-12). IEEE, 2010.(SWEREF-660)
Torchiano, M., Tomassetti, F., Ricca, F., Tiso, A., and Reggio, G., Journal of Systems and Software, 86(8), pp. 2110-2126, 2013.(SWEREF-661)
Watney, G., Reder, L. J., and Canham, T., IEEE International Conference on Space Mission Challenges for Information Technology (SMC-IT), pp. 54-61, 2014. An abbreviated description of this work is found in NASA Tech Brief NPO-49403.(SWEREF-662)
Casas, M.F., Trilateral SMA Conference (TRISMAC), June 2018. Requires special access into NSC resources.(SWEREF-663)
NASA-STD-1006, Approved: 2019-10-29, Office of the NASA Chief Engineer(SWEREF-664)
OCE site in NASA Engineering Network, Portal that houses information for software developers to develop code in a secure fashion, Formerly known as "Secure Coding"(SWEREF-665)
NVD is the U.S. government repository of standards based vulnerability management data represented using the Security Content Automation Protocol (SCAP).(SWEREF-666)
CVE® is a dictionary of publicly disclosed cybersecurity vulnerabilities and exposures that is free to search, use, and incorporate into products and services, per the terms of use.(SWEREF-667)
Multi-national forum for the development of communications and data systems standards for spaceflight(SWEREF-668)
MIL-STD-1553B, published in 1978,(SWEREF-669)
NASA/TM-2008- 215126/Vol II, NESC-RP-06-108/05-173-E/Part 2, April, 2008, See report section: 6.3.1.4.1 Coding and Implementation Issues Related to Reliability(SWEREF-670)
ARC - APR 8070.1 This document defines engineering design and environmental test requirements and guidelines for Class C and D space flight systems.(SWEREF-671)
JPL: DocID 43913, Rev. 1(SWEREF-672)
GSFC-STD-1000F, Approved: 02-08-2013 - With Administrative Changes , Expiration Date: 02-08-2018, Superseding GSFC-STD-1000E(SWEREF-673)
Public Lessons Learned Entry: 0405, Date: 1996-04-26, Submitting Organization: JPL, Submitted by: J.A. Roberts(SWEREF-674)
Lessons Learned Entry: 1598, Date: 2005-06-27, Submitting Organization: JPL, Submitted by: David J. Oberhettinger, Authored by: Allan Lee(SWEREF-675)
Public Lessons Learned Entry: 1843, Date: 2008-02-19, Submitting Organization: JPL, Submitted by: David Oberhettinger(SWEREF-676)
Public Lessons Learned Entry: 0567, Date: 1998-04-09, Submitting Organization: JPL, Submitted by: C. Guernsey/D. Oberhettinger(SWEREF-677)
Public Lessons Learned Entry: 0195, Date: 1992-11-04, Submitting Organization: KSC, Submitted by: David Pennington(SWEREF-678)
Final Report of the NEAR (Near Earth Asteroid Rendezvous Anomaly Review Board, November 1999(SWEREF-679)
Public Lessons Learned Entry: 1480, Date: 2004-06-21, Submitting Organization: JPL, Submitted by: Mark Boyles/David Oberhettinger(SWEREF-680)
Public Lessons Learned Entry: 0885, Date: 2000-06-8,Submitting Organization: JPL, Submitted by: R. Menke, R. Welch, D. Oberhettinger(SWEREF-681)
Public Lessons Learned Entry: 2041, Date: 2008-12-16, Submitting Organization: JPL, Submitted by: David Oberhettinger(SWEREF-682)
Public Lessons Learned Entry: 0288, Date: 1993-07-13, Submitting Organization: JPL, Submitted by: J. O. Blosiu(SWEREF-683)
Public Lessons Learned Entry: 1778, Date: 2007-03-6. Submitting Organization: JPL, Submitted by: Martin Ratliff(SWEREF-684)
Public Lessons Learned Entry: 0369, Date: 1995-01-24, Submitting Organization: JPL, Submitted by: B. Larman(SWEREF-685)
Arianne 5 Inquiry Board - European Space Agency(SWEREF-686)
NASA-HDBK-4008, Revision: Baseline w/CHANGE 1, Document Date: 2013-12-02(SWEREF-687)
(SWEREF-996)
Communities of Practice centered around engineering disciplines and led by NASA Technical Fellows. This SWEREF is used for testing.(SWEREF-997) Test Title, Test Citation, SWEREF-997 for testing
(test from )