NASA-Systems Engineering

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Reviews. Software reviews are scheduled by the program/project manager for the purpose of ensuring that software specifications and associated products are well understood by both program/project and user personnel. Throughout the development cycle, the pedigree, maturity, limitations, and schedules of delivered preproduction items, as well as the Computer Software Configuration Items (CSCI), are of critical importance to the project's engineering, operations, and verification organizations. Readiness Reviews. Readiness reviews are conducted prior to commencement of major events that commit and expose critical program/project resources to risk. These reviews define the risk environment and address the capability to satisfactorily operate in that environment. Mission Requirements Review. Purpose — The Mission Requirements Review (MRR) examines and substantiates top-level requirements analysis products and assesses their readiness for external review. Timing—Occurs (as required) following the maturation of the mission requirements in the mission definition stage. Objectives—The objectives of the review are to: • • • Confirm that the mission concept satisfies the customer's needs Confirm that the mission requirements support identification of external and long-lead support requirements (e.g., DoD, international, facility resources) Determine the adequacy of the analysis products to support development of the preliminary Phase B approval package. NASA Systems Engineering Handbook Management Issues in Systems Engineering Criteria for Successful Completion —The following items compose a checklist to aid in determining readiness of MRR product preparation: • • • • • • • • Are the top-level mission requirements sufficiently defined to describe objectives in measurable parameters? Are assumptions and constraints defined and quantified? Is the mission and operations concept adequate to support preliminary program/project documentation development, including the Engineering...
View Full Document

This document was uploaded on 02/26/2014 for the course E 515 at University of Louisiana at Lafayette.

Ask a homework question - tutors are online