MSFC NASA MWI 7123 1 REV D-2009 SYSTEMS ENGINEERING STAKEHOLDER EXPECTATIONS REQUIREMENTS DEFINITION AND MANAGEMENT PROCESSES《系统工程利害相关方期望 需求定义和管理流程》.pdf

《MSFC NASA MWI 7123 1 REV D-2009 SYSTEMS ENGINEERING STAKEHOLDER EXPECTATIONS REQUIREMENTS DEFINITION AND MANAGEMENT PROCESSES《系统工程利害相关方期望 需求定义和管理流程》.pdf》由会员分享，可在线阅读，更多相关《MSFC NASA MWI 7123 1 REV D-2009 SYSTEMS ENGINEERING STAKEHOLDER EXPECTATIONS REQUIREMENTS DEFINITION AND MANAGEMENT PROCESSES《系统工程利害相关方期望 需求定义和管理流程》.pdf（18页珍藏版）》请在麦多课文档分享上搜索。

1、CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE MWI 7123.1 BASELINE EFFECTIVE DATE: July 10, 2009 EXPIRATION DATE: July 10, 2014 MARSHALL WORK INSTRUCTION DA01 SYSTEMS ENGINEERING STAKEHOLDER EXPECTATIONS, REQUIREM

2、ENTS DEFINITION, AND MANAGEMENT PROCESSES Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Engineering Stakeholder Expectations, Requirements Definition, and Management Processes MWI 7123.1 Revision: Baseline Dat

3、e: July 10, 2009 Page 2 of 18 CHECK THE MASTER LIST at https:/repository.msfc.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 I

4、HSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Engineering Stakeholder Expectations, Requirements Definition, and Management Processes MWI 7123.1 Revision: Baseline Date: July 10, 2009 Page 3 of 18 CHECK THE MASTER LIST at

5、https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 1. PURPOSE This Marshall Work Instruction (MWI) implements five of the seventeen core set of common technical processes identified in MPR 7123.1, “Marshall Space Flight Center (MSFC) Systems

6、Engineering Processes and Requirements.” This MWI encompasses systems engineering processes for the “Stakeholder Expectations Definition,” “Technical Requirements Definition,” “Logical Decomposition,” “Requirements Management,” and “Interface Management.” 2. APPLICABILITY This MWI applies to the per

7、sonnel, programs, projects, and activities 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 Agreemen

8、t recipients, Space Act Agreement partners, or other agreement parties.) 3. APPLICABLE DOCUMENTS 3.1 NPR 1441.1, “NASA Records Retention Schedule” 3.2 MPR 1410.2, “Marshall Management Directives System” 3.3 MPR 1440.2, “MSFC Records Management Program” 3.4 MPR 7123.1, “MSFC Systems Engineering Proce

9、sses and Requirements” 3.5 MPR 8040.1, “Configuration Management, MSFC Programs/Projects” 3.6 MPR 8823.1, “Design Control of Facilities” 3.7 MWI 8050.1, “Verification and Validation of Hardware, Software, and Ground Support Equipment for MSFC Projects” 4. REFERENCES 4.1 NASA/SP-2007-6105, “NASA Syst

10、ems Engineering Handbook” 4.2 MPR 8500.1, “MSFC Environmental Management Program” 4.3 MSFC-HDBK-3173, “Project Management and Systems Engineering Handbook” Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Enginee

11、ring Stakeholder Expectations, Requirements Definition, and Management Processes MWI 7123.1 Revision: Baseline Date: July 10, 2009 Page 4 of 18 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 5. DEFINITIONS 5.1 Act

12、ivities 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 (as defined in MPR 850

13、0.1) and Restoration projects. 5.2 Stakeholders Individuals and/or organizations who are 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/act

14、ivity - end-users, designers, manufacturing, test, quality personnel, etc. 5.3 System of Interest The product for which the project team is responsible for designing, developing, integrating, validating, verifying, and delivering. 5.4 Validation Proof that the product accomplishes the intended purpo

15、se when placed in its intended environment. Product validation is accomplished through simulation, demonstration, inspection, analysis, test, or a combination of these, as appropriate (as defined in MWI 8050.1). 5.5 Verification Proof that the product complies with its associated configuration docum

16、entation such as requirement, specifications, engineering drawings, parts lists, etc. Methods of verification include - test, analysis, inspection, demonstration, validation of records, and similarity (as defined in MWI 8050.1). 6. INSTRUCTIONS 6.1 Requirements Development and Management Requirement

17、s development and management primarily involves four activities that start with a need and convert that need into a “design to” set of requirements from which a product can be developed. The set of requirements is maintained, modified and managed through the product life cycle. Those four activities

18、 are (1) to elicit and define stakeholder expectations (Stakeholder Expectations Definition Process); (2) to transform the expectations into quantitative and measurable technical requirements (Technical Requirements Definition Process); (3) to transform the defined set of technical requirements into

19、 a set of logical decomposition models (Logical Decomposition Process) and their associated set of element requirements for input to the design solution definition process; and (4) to maintain and manage change of the requirements over the life cycle of the project (Requirements and Interface Manage

20、ment Processes). Although the process instructions below are identified sequentially, the requirements development and management process occurs iteratively over the life cycle of the project. Additional information about these processes is provided in NASA/SP-2007-6105. A previous MSFC handbook was

21、 MSFC-HDBK-3173 “Project Management and Systems Engineering Handbook” that provided a description of the basic processes and general guidance for managing Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Engineer

22、ing Stakeholder Expectations, Requirements Definition, and Management Processes MWI 7123.1 Revision: Baseline Date: July 10, 2009 Page 5 of 18 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE and implementing the li

23、fe cycle of all projects managed at MSFC and executing the systems engineering processes. 6.2 Requirements Implementation Implementation of the requirements development and management process at MSFC requires participation by the product or “system of interest” customer and three principal MSFC orga

24、nizations: (a) the Program/Project/Activity Office; (b) the Engineering Directorate; and (c) the Safety and Mission Assurance Directorate or applicable contractor counterparts of these organizations. Specific responsibilities for these organizations are provided below: Requirement Number Actionee Sh

25、all Perform All Actions 6.2.1 System Engineer or Requirements Developer/Manager Establish a list that identifies the customer(s) and other stakeholders that have an interest in the product. 6.2.2 System Engineer or Requirements Developer/Manager Identify and collect higher-level expectations (e.g, n

26、eeds, goals, objectives, assumptions, constraints, requirements) from parent documentations (e.g., Project Plan, proposals, and requirements documents.) (See Appendix Z.1 for guidance.) 6.2.3 System Engineer or Requirements Developer/Manager Elicit and document the customer(s) and other stakeholders

27、 expectations (e.g., needs, goals, objectives, assumptions, drivers, constraints) for the product. (See Appendix Z.1 for guidance.) 6.2.4 System Engineer or Requirements Developer/Manager Identify and document all external interfaces (e.g., hardware, software) for the product. (See Appendix Z.2 for

28、guidance.) 6.2.5 System Engineer or Requirements Developer/Manager and Stakeholders Validate the customer(s) and other stakeholder expectations and identified external interfaces to ensure all expectations and interfaces are identified and agreed upon. 6.2.6 System Engineer or Requirements Developer

29、/Manager Develop and maintain operational concepts and scenarios for each of the Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Engineering Stakeholder Expectations, Requirements Definition, and Management Proc

30、esses MWI 7123.1 Revision: Baseline Date: July 10, 2009 Page 6 of 18 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE products life cycle phases (e.g., Assembly, Integration, Test, Operations, Disposal) based on the

31、 customer(s) and other stakeholders expected use of the product. (See Appendix Z.3 for guidance.) 6.2.7 System Engineer or Requirements Developer/Manager Define functional and behavioral expectations for the product in technical measures for the anticipated uses of the product as identified in the o

32、perational concepts. 6.2.8 System Engineer or Requirements Developer/Manager and Stakeholders Validate the operational concepts and scenarios to ensure all customers and other stakeholders agree on correctness, completeness, and incorporation of expectations. 6.2.9 System Engineer or Requirements De

33、veloper/Manager Collect and document in “shall” statements the product requirements (i.e., design performance, safety, and interface) based on the functional and behavioral expectations of the operational concepts and parent documentation (e.g., Project Plan, proposals, requirements documents) to fo

34、rm a set of “design-to” requirements. (See Appendices Z.4, Z.5, and Z.6 for guidance.) 6.2.10 System Engineer or Requirements Developer/Manager Document the rationale (why requirement exists) for each requirement established. (See Appendix Z.7 for guidance.) 6.2.11 System Engineer or Requirements De

35、veloper/Manager Document the traceability to the next higher level (parent) requirement(s) for each requirement established. (See Appendix Z.8 for guidance.) 6.2.12 System Engineer or Requirements Developer/Manager Document the verification method(s), as identified in MWI 8050.1, for each requiremen

36、t established. 6.2.13 System Engineer or Requirements Validate the product requirements in Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Engineering Stakeholder Expectations, Requirements Definition, and Manag

37、ement Processes MWI 7123.1 Revision: Baseline Date: July 10, 2009 Page 7 of 18 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Developer/Manager and Stakeholders accordance with MWI 8050.1 to ensure all stakeholder

38、s agree that all the requirements are identified, agreed upon, and that they satisfy the stakeholders expectations. 6.2.14 System Engineer or Requirements Developer/Manager and Configuration Management Personnel/Manager Baseline the specified requirements. 6.2.15 System Engineer or Requirements Deve

39、loper/Manager Define one or more system architecture models (See paragraph 4.3 of NASA/SP-2007-6105 for guidance in defining and developing system architecture models) that provide details of the product or “system of interest” into lower level elements. 6.2.16 System Engineer or Requirements Develo

40、per/Manager Decompose the product or “system of interest” requirements and group them together into functional or logical blocks based on commonality (e.g., function, performance, environment, and packaging). 6.2.17 System Engineer or Requirements Developer/Manager Allocate the common set of require

41、ments to the lower level elements of the system architecture model. 6.2.18 System Engineer or Requirements Developer/Manager and Stakeholders Validate the resultant set of element requirements to ensure all stakeholders agree that all the requirements have been identified and allocated to the approp

42、riate element and baseline. 6.2.19 System Engineer or Requirements Developer/Manager and Configuration Management Personnel/Manager Baseline the requirements. 6.2.20 Project Manager, System Engineer, Configuration Management Personnel/Manager, and Use the projects configuration management process, a

43、s identified in MPR 8040.1, to perform the following: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Engineering Stakeholder Expectations, Requirements Definition, and Management Processes MWI 7123.1 Revision:

44、Baseline Date: July 10, 2009 Page 8 of 18 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Stakeholders 6.2.20.1 Document requested requirement(s) change (i.e., modification, addition, or deletion) with justificatio

45、n for change. 6.2.20.2 Communicate the requested requirement(s) change to all stakeholders who are impacted. 6.2.20.3 Evaluate the impact (i.e., cost, schedule, technical, upper/lower requirements) of the requested requirement(s) change. 6.2.20.4 Approve or disapprove each change. 6.2.21 Configurati

46、on Management Personnel/Manager and System Engineer or Requirements Developer/Manager Perform the following activities for approved requirement(s) changes: 6.2.21.1 Distribute change to all who are impacted. 6.2.21.2 Maintain the requirements change history. 6.2.21.3 Make change to the requirement(s

47、) documentation. 7. NOTES None. 8. SAFETY PRECAUTIONS AND WARNING NOTES None. 9. RECORDS The following records are required by this MWI: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction DA01 Systems Engineering Stakeholder Ex

48、pectations, Requirements Definition, and Management Processes MWI 7123.1 Revision: Baseline Date: July 10, 2009 Page 9 of 18 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Record Custodian SEMP PM or designee Proc

49、ess Plans PM or designee Process Support Documents PM or designee Enabling Support Documentation PM or designee Product Implementation Documents PM or designee Pre-board minutes PM or designee Board minutes PM or designee Board Certification Board Chairperson Review results PM or designee System Requirements Document (SRD) PM or designee I