Page 5 of 56. Showing 559 results (0.035 seconds)
SWE-185 - Secure Coding Standards Verification
ABSTRACT: "code is mechanically checked against the standards with the help of state of-the-art static source code analyzers..." Paraphrasing from section 2.2 The Code "Code should be checked nightly for compliance with a coding standard and subjected to rigorous analysis with state-of-the-art (static source code analSWE-207 - Secure Coding Practices
2D-SWE Page Message Content updates needed on this page: 1. Requirements 3.11.6 The project manager shall identify, record, and implement secure coding practices. 1.1 Notes NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement. 1.2 History SWE-207 History 1.3 AppliSWE-159 - Verify and Validate Risk Mitigations
2D-SWE Page Message Content updates needed on this page: 1. Requirements 3.11.5 The project manager shall test the software and record test results for the required software cybersecurity mitigation implementations identified from the security vulnerabilities and security weaknesses analysis. 1.1 Notes Include asSWE-157 - Protect Against Unauthorized Access
Current trends such as technology proliferation, accessibility to space, globalization of space programs and industries, commercialization of space systems and services, and foreign knowledge about U.S. space systems increases the likelihood that the U.S. will experience a "Space Pearl Harbor." For example, in July 200SWE-154 - Identify Security Risks
"The reality is that there are many extant capabilities to deny, disrupt or physically destroy space systems and the ground facilities that command and control them. Knowledge of U.S. space systems functions, locations and physical characteristics, as well as the means to conduct counterspace operations, is increasinglSWE-148 - Contribute to Agency Software Catalog
2D-SWE Page Message 1. Requirements 3.10.2 The project manager shall evaluate software for potential reuse by other projects across NASA and contribute reuse candidates to the appropriate NASA internal sharing and reuse software system. However, if the project manager is not a civil servant, then a civil servant wSWE-147 - Specify Reusability Requirements
#25 Reusing code not designed for reuse Code that is not designed for reuse will not be in the form of an abstract data type or object. The code may have interdependencies with other code, such that if all of it is taken, there is more code than needed. If only part is taken, it must be thoroughly dissected, which incSWE-032 - CMMI Levels for Class A and B Software
2D-SWE Page Message Content updates needed on this page: Update Guidance Update Software Assurance Update tab 3, last para, re: SPAN and "Process for Evaluation instead of CMMI® Appraisal" - where can this process be found? Fix PARS links in tab 7.4 - 12/15 - FDH changed Notes to remove reference to CMMI Dev 1SWE-206 - Auto-Generation Software Inputs
"Users not only need to be sure that the code implements the model, but also that the code generator is correctly used and configured, that the target adaptations are correct, that the generated code meets high-level safety requirements, that it is integrated with legacy code, and so on." 2D-SWE PagSWE-150 - Review Changes To Tailored Requirements
“The request for relief from a requirement includes the rationale, a risk evaluation, and reference to all material that provides the justification supporting acceptance.” 2D-SWE Page Message 1. Requirements 2.2.7 The engineering, CIO, and SMA authorities shall review and agree with any tailore
