Page 1 of 7. Showing 67 results (0.005 seconds)
7.04 - Flowdown of NPR Requirements on Contracts and to Other Centers in Multi-Center Projects
safety policies, project safety plans, and risk management plans. Reporting of mishaps, close calls, and lessons learned. Surveillance by NASA. Performance-based … , in the Supplier Agreement Management (SAM) process area are required to support the acquiring organization during the acquisition planning process in the softwareSWE-016 - Software Schedule
of the goals and objectives of the project requires in-depth planning to develop and document and maintain an integrated set of work activities and tasks. This is normally … described in the software development plan in response to the overall project/system schedule. The planned software activities need to include the detailed stepsSWE-122 - Technical Authority Appointment
of Engineering Technical Authority(s) is documented in the Center Technical Authority Implementation Plan. Please refer to Appendix D (last column) for requirements … in appointment letters from the Engineering Technical Authority (or designee), in the Center implementation plans, in project plans, and in organizationSWE-004 - OCE Benchmarking
Software Engineering Improvement Plan. 1.1 Notes Note: Center Software Engineering Improvement Plans are documented per Center Software Engineering Improvement Plan requirements. Capability Maturity Model Integration (CMMI) for Development (CMMI-DEV) appraisals are the preferred benchmarks for objectively measuring7.13 - Transitioning to a Higher Class
only to remaining work, e.g., cost estimates? Process-related requirements, e.g., configuration management and planning, should already be met but should … ) Software Management Plan 1 1 1 1 1 1 1 Software Configuration Management Plan 1 1 1 1 1 1 1 Software Test PlanSWE-131 - Independent Verification and Validation Project Execution Plan
, the NASA IV&V program shall develop an IV&V Project Execution Plan (IPEP). 1.1 Notes Note: The selection of projects and capabilities by the Chief, Safety … http://www.nasa.gov/centers/ivv/ims/home/index.html. Note from 5.1.8 IV&V Project Execution Plan (IPEP): The IPEP is divided into two major parts: The bodySWE-092 - Measurement Collection and Storage
: To improve future planning and cost estimation. To provide realistic data for progress tracking. To provide indicators of software quality. To provide baseline … of the data, an agreed-to procedure for this is needed within the Software Development Plan (see SWE-102). Activities within the data collection procedure include7.08 - Maturity of Life Cycle Products at Milestone Reviews
PDR CDR SIR TRR SAR ORR Software Development Plan (SDP) / Software Management Plan (SMP) P P B U … Software Configuration Management Plan (SCMP) P P B U Software Test Plans PSWE-104 - Software Test Plan
1. Requirements 5.1.3.1 The Software Test Plan shall include: [SWE-104] a. Test levels (separate test effort that has its own documentation and resources … and depth) or other methods for ensuring sufficiency of testing. h. Planned tests, including items and their identifiers. i. Test schedules. jSWE-101 - Center SW Training Plans
1. Requirements 4.6.2 Each Center shall maintain and implement Software Training Plan(s) to advance its in-house software engineering capability and as a reference for its contractors. 1.1 Notes The Software Training Plan content is defined by the Software Training Plan requirement in Chapter 5 [of NPR 7150.2, NASA
