1 | Purpose, applicability and hierarchy of the directive | 0 |
2.2 | Principles for tailoring the requirements | 0 |
6 | Recommended software documentation contents | 0 |
C | Requirements mapping matrix | 0 |
D | Software classifications | 0 |
SWE-002 | OCE leads a NASA Software Engineering Initiative | 0 |
SWE-003 | Center Director maintains a plan to advance in-house software engineering capability and monitor contractors | 0 |
SWE-004 | OCE benchmarks each Center's software engineering capability | 0 |
SWE-005 | Center Director establishes and maintains software processes per the directive | 0 |
SWE-006 | Center Director maintains a reliable list of programmes and projects with Class A to D software | 0 |
SWE-013 | Develop, maintain and execute software plans covering the whole life cycle | 0 |
SWE-015 | Establish and maintain software cost estimate models and parameters | 0 |
SWE-016 | Document and maintain a software schedule that coordinates with the project | 0 |
SWE-017 | Plan, track and ensure project-specific software training | 0 |
SWE-018 | Hold regular software schedule reviews with stakeholders and track issues to resolution | 0 |
SWE-020 | Classify each system and subsystem containing software per Appendix D | 0 |
SWE-021 | Project manager updates plans and supplier contracts when software classification changes | 0 |
SWE-022 | Plan and implement software assurance, software safety and IV&V per NASA-STD-8739.8 | 0 |
SWE-023 | Implement the safety-critical software requirements of NASA-STD-8739.8 | 0 |
SWE-024 | Track actual results and performance against the software plans | 0 |
SWE-027 | Satisfy the conditions for COTS, GOTS, MOTS, OSS or reused software | 0 |
SWE-032 | Acquire, develop and maintain software from organisations with the required CMMI-DEV rating | 0 |
SWE-033 | Assess software acquisition versus development options | 0 |
SWE-034 | Define and document software acceptance criteria | 0 |
SWE-036 | Establish software processes, documentation plans, deliverables and Government actions on receipt | 0 |
SWE-037 | Define the milestones at which developer progress is reviewed and audited | 0 |
SWE-039 | Require developers to report status and give insight into development and test | 0 |
SWE-040 | Require developers to provide products, traceability, change tracking and nonconformances electronically | 0 |
SWE-042 | Require electronic access to source code in a modifiable format | 0 |
SWE-045 | Participate in joint NASA and developer audits | 0 |
SWE-046 | Require developers to provide a software schedule and updates for review | 0 |
SWE-050 | Establish, record, approve and maintain software requirements as part of the technical specification | 0 |
SWE-051 | Analyse software requirements from flowed-down and derived sources | 0 |
SWE-052 | Perform and maintain bi-directional traceability per software classification | 0 |
SWE-053 | Track and manage changes to the software requirements | 0 |
SWE-054 | Identify, correct and track to closure inconsistencies among requirements, plans and products | 0 |
SWE-055 | Validate requirements against intended performance in the customer environment | 0 |
SWE-057 | Transform the software requirements into a recorded software architecture | 0 |
SWE-058 | Develop, record and maintain a software design that describes the lower-level units | 0 |
SWE-060 | Implement the software design into code | 0 |
SWE-061 | Select, define and adhere to software coding methods, standards and criteria | 0 |
SWE-062 | Unit test the software code | 0 |
SWE-063 | Provide a software version description for each release | 0 |
SWE-065 | Establish and maintain software test plans, procedures, tests and reports | 0 |
SWE-066 | Test the software against its requirements | 0 |
SWE-068 | Evaluate test results and record the evaluation | 0 |
SWE-070 | Use validated and accredited models, simulations and analysis tools for qualification | 0 |
SWE-071 | Keep test and verification plans and procedures consistent with the requirements | 0 |
SWE-073 | Validate the software system on the target platform or a high-fidelity simulation | 0 |
SWE-075 | Plan and implement software operations, maintenance and retirement activities | 0 |
SWE-077 | Deliver the software product with the records needed for operations and maintenance | 0 |
SWE-079 | Develop a software configuration management plan | 0 |
SWE-080 | Track and evaluate changes to software products | 0 |
SWE-081 | Identify the software configuration items and versions to be controlled | 0 |
SWE-082 | Establish procedures for control levels and change authority | 0 |
SWE-083 | Prepare and maintain configuration status records | 0 |
SWE-084 | Perform software configuration audits | 0 |
SWE-085 | Establish procedures for storage, handling, delivery, release and maintenance of deliverable software | 0 |
SWE-086 | Record, analyse, plan, track, control and communicate software risks | 0 |
SWE-087 | Perform and report software peer reviews or inspections of the key products | 0 |
SWE-088 | Run each peer review with checklists, criteria, action tracking and required participants | 0 |
SWE-089 | Record the necessary measurements for each peer review | 0 |
SWE-090 | Establish, record, maintain, report and use software management and technical measurements | 0 |
SWE-091 | Center Director maintains a software measurement repository for Class A, B and C projects | 0 |
SWE-092 | Center Director uses measurement data to monitor capability and improve quality | 0 |
SWE-093 | Analyse measurement data using documented procedures | 0 |
SWE-094 | Provide access to measurement data, analyses and status on request | 0 |
SWE-095 | Center Director reports on the Center's software engineering discipline on request | 0 |
SWE-098 | OCE maintains an Agency-wide process asset library | 0 |
SWE-100 | OCE and Center training organisations provide software engineering training | 0 |
SWE-121 | Document approved tailoring in the controlling plans or procedures | 0 |
SWE-125 | Maintain a requirements mapping matrix against this directive | 0 |
SWE-126 | Technical and institutional authorities assess mapping matrices and tailoring | 0 |
SWE-129 | OCE authorises appraisals against selected requirements | 0 |
SWE-131 | Ensure an IV&V Project Execution Plan is developed, approved, maintained and executed | 0 |
SWE-134 | Build the safe-state and integrity behaviours into safety-critical and mission-critical software | 0 |
SWE-135 | Use static analysis tools during development and test | 0 |
SWE-136 | Validate and accredit the software tools required to develop or maintain software | 0 |
SWE-139 | Comply with the Appendix C requirements for the software classification | 0 |
SWE-140 | Center Director complies with the requirements marked for Centers in Appendix C | 0 |
SWE-141 | Ensure IV&V is performed on the designated categories of projects | 0 |
SWE-142 | Center Director maintains software cost repositories for Class A, B and C projects | 0 |
SWE-143 | Perform a software architecture review on the designated categories of projects | 0 |
SWE-144 | Center Director contributes process assets to the Agency library | 0 |
SWE-146 | Define the approach to automatic generation of source code | 0 |
SWE-147 | Specify reusability requirements to enable future reuse for Government purposes | 0 |
SWE-148 | Evaluate software for reuse and contribute candidates to the NASA sharing system | 0 |
SWE-150 | Engineering, CIO and SMA authorities review and agree all tailored requirements | 0 |
SWE-151 | Software cost estimates meet the stated conditions | 0 |
SWE-152 | OCE periodically reviews project requirements mapping matrices | 0 |
SWE-153 | Designated Engineering Technical Authorities define content requirements for software documents | 0 |
SWE-154 | Identify and plan mitigations for cybersecurity risks in flight and ground software | 0 |
SWE-156 | Perform a software cybersecurity assessment on the software components | 0 |
SWE-157 | Protect communicating software systems against unauthorised access per NASA-STD-1006 | 0 |
SWE-159 | Test and record the required cybersecurity mitigations | 0 |
SWE-174 | Submit software planning parameters to the Center measurement repository at major milestones | 0 |
SWE-176 | Keep records of classification determinations, mapping matrices and independent assessments for the project's life | 0 |
SWE-178 | Give IV&V access to development artefacts, products, source code and data | 0 |
SWE-179 | Respond to IV&V issues and risks and track them to closure | 0 |
SWE-184 | Include software-related safety constraints, controls, mitigations and assumptions in the requirements | 0 |
SWE-185 | Verify the code meets the secure coding standard using static analysis results | 0 |
SWE-186 | Assure that unit test results are repeatable | 0 |
SWE-187 | Place software items under configuration management before testing | 0 |
SWE-189 | Select, implement, track, record and report code coverage measurements | 0 |
SWE-190 | Verify code coverage by analysing the results of test execution | 0 |
SWE-191 | Plan and conduct regression testing | 0 |
SWE-192 | Verify by test the requirements that trace to hazards | 0 |
SWE-193 | Develop acceptance tests for loaded or uplinked data, rules and code | 0 |
SWE-194 | Verify before delivery that requirements are met, changes implemented and defects resolved | 0 |
SWE-195 | Maintain the software to the standards and processes of its classification | 0 |
SWE-196 | Identify the records and tools to archive and the access procedures for retirement | 0 |
SWE-199 | Monitor measures to ensure performance and functionality requirements will be met | 0 |
SWE-200 | Collect, track and report software requirements volatility metrics | 0 |
SWE-201 | Track and maintain software non-conformances | 0 |
SWE-202 | Define and implement clear severity levels for all software non-conformances | 0 |
SWE-203 | Assess reported non-conformances in all off-the-shelf and reused components | 0 |
SWE-204 | Run closed-loop process assessments for high-severity non-conformances | 0 |
SWE-205 | Determine with SMA whether each software component is safety-critical | 0 |
SWE-206 | Require electronic access to the models, simulations and data used for auto-generation | 0 |
SWE-207 | Identify, record and implement secure coding practices | 0 |
SWE-208 | Chief SMA leads a Software Assurance and Software Safety Initiative | 0 |
SWE-209 | Chief SMA benchmarks Center assurance and safety capability against NASA-STD-8739.8 | 0 |
SWE-210 | Identify requirements for collecting, reporting and storing adversarial action detection data | 0 |
SWE-211 | Test embedded off-the-shelf and reused components to the same level as custom components | 0 |
SWE-212 | Chief SMA periodically reviews project requirements mapping matrices | 0 |
SWE-214 | Center Director performs the prescribed actions for each type of internal software transfer | 0 |
SWE-215 | Center Director ensures Government rights before internal software sharing or reuse | 0 |
SWE-216 | Center Director ensures catalogued reuse software conforms to NASA software policy | 0 |
SWE-217 | Center Director keeps contributor lists and disclaimer provisions on reuse products | 0 |
SWE-218 | Contracting Officers and Agreement Managers include the required software clauses in every acquisition instrument | 0 |
SWE-219 | Achieve 100 percent MC/DC code test coverage of safety-critical components | 0 |
SWE-220 | Keep safety-critical components at cyclomatic complexity 15 or lower | 0 |
SWE-221 | Chief SMA authorises appraisals against selected requirements | 0 |
SWE-222 | Chief SMA provides for software assurance training | 0 |
SWE-223 | Chief SMA makes the final decision on tailoring of the IV&V requirement | 0 |