Page 1 of 57. Showing 569 results (0.069 seconds)
SWE-219 - Code Coverage for Safety Critical Software
2D-SWE Page Message 1. Requirements 3.7.4 If a project has safety-critical software, the project manager shall ensure that there is 100 percent code test coverage using the Modified Condition/Decision Coverage (MC/DC) criterion for all identified safety-critical software components. 1.1 Notes In MC/DC coverage, eaBook A. Introduction
4 4 https://swehb.nasa.gov/download/thumbnails/50888752/NASA%20LOGO.jpg?version=1&modificationDate=1520963945000&api=v2 Welcome to the NASA Software Engineering and Assurance Handbook, NASA-HDBK-2203. Software is a core capability and key enabling technology for NASA's missions and suSWEREF-083
https://swehb.nasa.gov/download/attachments/16450224/N_PR_7150_002D_.pdf?api=v2 NPR 7150.2 NASA Software Engineering Requirements, Intro, SWE-002, SWE-003, SWE-004, SWE-005, SWE-006, SWE-018, SWE-020, SWE-022, SWE-024, SWE-033, SWE-036, SWE-037, SWE-039, SWE-040, SWE-085, SWE-092, SWE-095, SWE-098, SWE-100, SWE-121,SWE-217 - List of All Contributors and Disclaimer Notice
2D-SWE Page Message 1. Requirements 2.1.5.15 The Center Director, or designee, (e.g., the Civil Servant Technical Point of Contact (POC) for the software product) shall perform the following actions: a. Keep a list of all contributors to the software product. b. Ensure that the software product contains appropriSWE-215 - Software License Rights
2D-SWE Page Message 1. Requirements 2.1.5.13 The Center Director or designee shall ensure that the Government has clear rights in the software, a Government purpose license, or other appropriate license or permission from third party owners prior to providing the software for internal NASA software sharing or reusSWEREF-278
https://standards.nasa.gov/sites/default/files/standards/NASA/B/0/NASA-STD-87398-Revision-B.pdf SOFTWARE ASSURANCE AND SOFTWARE SAFETY STANDARD HR-31 , HR-33 , HR-34 , HR-41 , HR-42 , SWE-001, SWE-002, SWE-003, SWE-004, SWE-005, SWE-006, SWE-013, SWE-014, SWE-018, SWE-020, SWE-022, SWE-023, SWE-024, SWE-025, SWESWE-006 - Center Software Inventory
2D-SWE Page Message 1. Requirements 2.1.5.6 Center Director, or designee, shall maintain a reliable list of their Center’s programs and projects containing Class A, B, C, and D software. The list should include: a. Project/program name and Work Breakdown Structure (WBS) number. b. Software name(s) and WBS numberSWEREF-257
https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPD&c=7120&s=4E NASA Engineering and Program/Project Management Policy, SWE-002, SWE-028, SWE-039, SWE-041, SWE-044, SWE-120, SWE-121, SWE-122, SWE-124, SWE-125, SWE-126, SWE-127, SWE-128, SWE-129, SWE-131, SWE-140, SWE-141, SWE-145, SWE-149, SWE-152, SWE-161, SWE-165, SWSWE-129 - OCE NPR Appraisals
“The baseline set of questions are reviewed and may be revised as needed to support the survey at each specific organization. Input for updates to the questions is obtained from survey team members including the software engineering sub-team lead, the systems engineering sub-team lead, and the Office of the Chief InfoSWE-050 - Software Requirements
2D-SWE Page Message Content updates needed on this page: Guidance Rebuild flow diagram to remove SWE-028 which was removed after version B. 1. Requirements 4.1.2 The project manager shall establish, capture, record, approve, and maintain software requirements, including requirements for COTS, GOTS, MOTS, OSS
