Page 1 of 56. Showing 559 results (0.028 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 suSWE-214 - Internal Software Sharing and Reuse
2D-SWE Page Message 1. Requirements 2.1.5.16 The Center Director or designee (e.g., the Civil Servant Technical POC for the software product) shall perform the following actions for each type of internal NASA software transfer or reuse: a. A NASA civil servant to a NASA civil servant: (1) Verify the requesting NSWE-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-216 - Internal Software Sharing List
2D-SWE Page Message 1. Requirements 2.1.5.14 The Center Director, or designee, shall ensure that all software listed on the internal software sharing or reuse catalog(s) conforms to NASA software engineering policy and requirements. 1.1 Notes NPR 7150.2, NASA Software Engineering Requirements, does not include aSWE-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 reusSWE-153 - ETA Define Document Content
2D-SWE Page Message 1. Requirements 2.1.5.12 The designated ETA(s) shall define the content requirements for software documents or records. 1.1 Notes The recommended practices and guidelines for the content of different types of software activities (whether stand-alone or condensed into one or more project levelSWE-144 - Software Engineering Process Assets
2D-SWE Page Message 1. Requirements 2.1.5.11 Each Center Director, or designee, shall contribute applicable software engineering process assets in use at his/her Centers to the Agency-wide process asset library. 1.1 Notes NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this reSWE-142 - Software Cost Repositories
2D-SWE Page Message 1. Requirements 2.1.5.10 For Class A, B, and C software projects, each Center Director, or designee, shall establish and maintain software cost repository(ies) that contains at least the following measures: a. Planned and actual effort and cost. b. Planned and actual schedule dates for majorSWE-092 - Using Measurement Data
Step 2 Target Goals "At the organizational level, we typically examine high-level strategic goals like being the low cost provider, maintaining a high level of customer satisfaction, or meeting projected revenue or profit margin target. At the project level, we typically look at goals that emphasize project management
