1、CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE MPR 7123.1 BASELINE EFFECTIVE DATE: July 10, 2009 EXPIRATION DATE: July 10, 2014 MARSHALL PROCEDURAL REQUIREMENTS DA01 MSFC SYSTEMS ENGINEERING PROCESSES AND REQUIREM
2、ENTS Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements DA01 MSFC Systems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 2 of 36 CHECK THE MASTER LIST at https:/repository.m
3、sfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE DOCUMENT HISTORY LOG Status (Baseline/ Revision/ Canceled) Document Revision Effective Date Description Baseline 7/10/2009 Provided by IHSNot for ResaleNo reproduction or networking permitted without license fr
4、om IHS-,-,-Marshall Procedural Requirements DA01 MSFC Systems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 3 of 36 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE TA
5、BLE OF CONTENTS Preface P.1 Purpose P.2 Applicability P.3 Authority P.4 Applicable Documents P.5 References P.6 Cancellation Document Content 1. Definitions 2. Responsibilities 2.1 MSFC Center Director 2.2 MSFC Engineering Director 2.3 Program/Project/Activity Manager 2.4 Engineering Line Management
6、 2.5 Designated Governing Authority 2.6 Multi-Center Programs/Projects 2.7 Software 3. Procedures 3.1 Program/Project/Activity Systems Engineering Life-Cycle 3.2 System Design Processes 3.3 Product Realization Processes 3.4 Technical Management Processes 3.5 SEMP Common Technical Process Implementat
7、ion Matrix 3.6 SEMP Maintenance 4. Records 4.1 Records Custodian 4.2 Records Retention 5. Flow Diagram Appendix A SEMP Appendix B DGA Appendix C Best Practices Appendix D Acronyms Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Re
8、quirements DA01 MSFC Systems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 4 of 36 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE PREFACE P.1 PURPOSE a. This Marshal
9、l Procedural Requirements (MPR) document implements the Agency Systems Engineering Management requirements documented in NASA Procedural Requirements (NPR) 7123.1. The NPR mandates seventeen (17) processes to be used for consistency in Systems Engineering (SE) throughout the Agency. These processes
10、focus on defining stakeholder expectations and implementing a systematic approach for satisfying those expectations. The processes are extracted from industry, national, international, and Agency standards. These processes provide the best typical practices currently available. The processes and con
11、cepts are not new, but the context and terminology may be unfamiliar. b. The implementation plan of system engineering requirements at Marshall Space Flight Center (MSFC) was submitted and approved in August 2006. The MSFC Systems Engineering requirements can be summarized in four simple statements:
12、 (1) Every Program/Project/Activity shall have a Systems Engineering Management Plan (SEMP); (2) A SEMP shall contain the mandatory sections outlined and annotated in Appendix A of this MPR; (3) Every SEMP shall be approved by a Designated Governing Authority (DGA) as defined by Appendix B of this M
13、PR; and (4) The Engineering Line Management shall ensure compliance with the approved SEMP. c. All additional requirements and information in this MPR provide amplification on these four requirement statements. P.2 APPLICABILITY a. This MPR applies to the personnel, programs, projects, and activitie
14、s at MSFC and MSFCs Michoud Assembly Facility, including contractors and resident agencies to the extent specified in their respective contracts or agreements. (“Contractors,” for purposes of this paragraph, include contractors, grantees, Cooperative Agreement recipients, Space Act Agreement partner
15、s, or other agreement parties.) b. Applying the common technical processes and reviews may also benefit Basic and Applied Research (BAR) and Advanced Technology Development (ATD) projects. The processes in this MPR and the reviews detailed in MPR 7123.2 are recommended but not required for BAR and A
16、TD projects. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements DA01 MSFC Systems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 5 of 36 CHECK THE MASTER LIST at https:/repo
17、sitory.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE P.3 AUTHORITY a. NPR 7123.1, “NASA Systems Engineering Processes and Requirements” b. NPR 7150.2, “NASA Software Engineering Requirements” P.4 APPLICABLE DOCUMENTS a. NPD 2820.1, “NASA Software Policy”
18、b. NPR 1441.1, “NASA Records Retention Schedules” c. MPR 1280.2, “Process Control” d. MPR 1440.2, “MSFC Records Management Program” e. MPR 4000.1, “Control of Customer-Supplied Product” f. MPR 5000.1, “Purchasing” g. MPR 6410.1, “Handling, Storage, Packaging, Preservation, and Delivery (HSPPD)” h. M
19、PR 7120.3, “Data Management, Programs/Projects” i. MPR 7123.2, “Technical Reviews and Review Item Discrepancy (RID) Processing, MSFC Programs and Projects” j. MPR 8040.1, “Configuration Management, MSFC Programs/Projects” k. MPR 8823.1, “Design Control of Facilities” l. MWI 1280.1, “Mechanical Fabri
20、cation Request Instructions” m. MWI 5100.1, “Initiating Procurement Requisitions” n. MWI 6410.1, “Packaging, Handling, and Moving Program Critical Hardware” o. MWI 7120.2, “Data Identification/Definition” p. MWI 7120.4, “Document Preparation, Programs and Projects” q. MWI 7120.6, “Program/Project Co
21、ntinuous Risk Management” Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements DA01 MSFC Systems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 6 of 36 CHECK THE MASTER LIST a
22、t https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE r. MWI 7123.1, “Systems Engineering Stakeholder Expectations, Requirements Definition, and Management Processes” s. MWI 8050.1, “Verification and Validation of Hardware, Software, and Groun
23、d Support Equipment for MSFC Projects” P.5 REFERENCES a. NASA/SP-2007-6105, “NASA Systems Engineering Handbook” b. MPR 8500.1, “MSFC Environmental Management Program” c. MSFC-HDBK-3173, “MSFC Project Management and Systems Engineering Handbook” d. CMMI Guidelines for Process Integration and Product
24、Improvement Addison-Wesley e. MSFC Systems Engineering Implementation Plan Submitted: August 2006 P.6 CANCELLATION None. Original signed by Robert M. Lightfoot Acting Director Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requir
25、ements DA01 MSFC Systems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 7 of 36 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE DOCUMENT CONTENT 1 DEFINITIONS 1.1 Acti
26、vities - Common technical processes for large and small efforts associated with flight systems, ground support systems, advanced technology development, information systems, technology projects, institutional projects, and also Construction of Facility, Environmental Compliance and Restoration proje
27、cts. 1.2 Architecture - Model(s) showing performance, function, and interface. The architectural drawings provide a means to evaluate alternate solutions by highlighting risks and enabling judgments. Operating and Use-case conditions are exercised on the architectural model to provide insight on how
28、 the system will perform. 1.3 Design Constraint - Design constraints are derived requirements. Constraints may be based on limits of physical design that result in budgeted allocations like fuel, weight or power, but they may also be determined by management considerations like cost or schedule. 1.4
29、 Design Tools (prototypes, models, analysis) - Convert design into objects that present virtual or real physical appearance with limited functional performance (prototypes); provide realistic output response from different inputs (models); or provide some computer analysis or model that simulates th
30、e final end product. 1.5 Detailed Design - Fully defines the structures and capabilities to the level necessary to build a product or to develop software. 1.6 Measure of Effectiveness (MOE) - A measure by which a stakeholders expectations are judged in assessing satisfaction with products and system
31、s produced and delivered in accordance with the associated technical effort. The MOE is deemed to be critical to not only the acceptability of the product by the stakeholder, but also critical to the operational/mission usage. An MOE is typically qualitative in nature or not able to be used directly
32、 as a “design-to” requirement. 1.7 Measure of Performance (MOP) - A quantitative measure that, when met by the design solution, will help ensure that an MOE for a product or system will be satisfied. These MOPs are given special attention during design to ensure that the MOEs to which they are assoc
33、iated are met. There are generally two or more measures of performance for each MOE. 1.8 Preliminary Design - Initiates the process of transferring the raw requirements into functional entities. Verbal requirements are visualized into product partitions, components, system-states and modes. The desi
34、gner draws out the system architecture as blocks assigning mechanical and electronic functions. (For software, timing and memory requirements are included.) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements DA01 MSFC Sy
35、stems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 8 of 36 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 1.9 Stakeholders - Individuals and/or organizations who ar
36、e affected by or in some way accountable for the outcome of an undertaking, but who may not be directly involved with doing the processing work. Stakeholders include all who are involved in the program/project/activity - end-users, designers, manufacturing, test, and quality personnel. 1.10 Technica
37、l Performance Measures (TPM) - The set of critical or key performance parameters that are monitored by comparing the current actual achievement of the parameters with the anticipated performance. Used to confirm progress and identify deficiencies that might jeopardize meeting a system requirement. A
38、ssessed parameter values that fall outside an expected range around the anticipated values indicate a need for evaluation and corrective action. TPMs are typically selected from the defined set of MOPs. 1.11 Technical Requirements - Statements defining performance characteristics of a product. Requi
39、rements are written from the top down. The “system” is initially described, and subsequently, requirements devolve to lower level components. Specific documents are associated with requirements. Each System Requirement, Configuration Item specification, Critical Item specification, Manufacturing spe
40、cification, etc., defines an area of requirements that is traceable from the top down or from the bottom up. Requirements are stated in such a manner that pass/fail or quantitative assessment criteria are specified. 1.12 Use-Case - A defined task within a system that provides a measured result for s
41、omeone or something outside the system. Use-cases bridge the gap between users statements and performance functionality. No single Use-case specifies the entire system. Each Use-case explains one particular interaction. 1.13 Validation - Proof that the product accomplishes the intended purpose when
42、placed in its intended environment. Product validation is accomplished through simulation, demonstration, inspection, analysis, test, or a combination of these, as appropriate. 1.14 Verification - Proof that the product complies with its associated configuration documentation such as requirements, s
43、pecifications, engineering drawings, parts lists, etc. Methods of verification include test, analysis, inspection, demonstration, validation of records, and similarity. 2. RESPONSIBILITIES: 2.1 The MSFC Center Director or designee shall: 2.1.1 Ensure implementation of the SE policies at MSFC; and 2.
44、1.2 Serve as Chairperson of the MSFC SE DGA to approve systems engineering implementation for MSFC Class 1 Programs/Projects/Activities (see Appendix B). 2.2 The MSFC Engineering Director or designee shall: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS
45、-,-,-Marshall Procedural Requirements DA01 MSFC Systems Engineering Processes and Requirements MPR 7123.1 Revision: Baseline Date: July 10, 2009 Page 9 of 36 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 2.2.1 Se
46、rve as Chairperson of the MSFC SE DGA to approve systems engineering implementation of MSFC Class 2 Programs/Projects/Activities (see Appendix B); 2.2.2 Review Class 1 Programs/Projects/Activities systems engineering implementation prior to DGA review/approval; and 2.2.3 Ensure appropriate Engineeri
47、ng Directorate and Engineering Management Council (EMC) review of the SEMP prior to DGA review and approval. 2.3 The Program/Project/Activity Manager or designee shall: 2.3.1 Ensure a SEMP is written to define Program/Project/Activity implementation of SE requirements and processes; 2.3.2 Ensure rev
48、iew and approval by the appropriate SE DGA; and 2.3.3 Control the SEMP under Program/Project/Activity control processes. 2.3.4 Provide the design team with statutory and regulatory requirements, relevant information from previous similar designs, and any other requirements deemed essential for produ
49、ct design and development. 2.4 The Engineering Line Management shall: 2.4.1 Prepare and approve the SEMP in accordance with this MPR for the Program/Project/Activity; and 2.4.2 Ensure compliance with the approved SEMP. 2.5 The DGA approval of the SEMP, including any tailored and/or waived processes and/or requirements, shall authorize it for imple
