1、EIA STANDARD Systems Engineering Capability Model EIA-73 1.1 (Formerly EMS-731.1) AUGUST 2002 ELECTRONIC INDUSTRIES ALLIANCE GOVERNMENT ELECTRONICS AND INFORMATION TECHNOLOGY ASSOCIATION Copyright Government Electronics (b) acquirers of systems; (c) university professors, organizational trainers, an
2、d consultants; and (d) developers of other maturity or capability models. Use is not limited to specific disciplines, industry sectors, or technology domains. This Standard may be tailored for a specific domain, organization, or program. This Standard is intended to neither specifj nor encourage the
3、 use of any particular implementation method or tool. The using organization is responsible for selecting those methods or tools necessary to support the objectives of the organization and program, and to define and implement engineering policies and procedures. Annexes A and B are normative. Normat
4、ive annexes are integral parts of the standard that, for reasons of convenience, are placed after all other normative elements. The fact that an annex is normative is made clear by the way in which it is referred to in the text, by a statement to the effect in the foreword, and by an indication at t
5、he head of the annex itself. Annexes Cy Dy and E are informative. Informative annexes, formerly called appendices, give additional information and are placed after the normative elements of a standard. They do not contain requirements. The fact that an annex is informative is made clear by the way i
6、n which it is refered to in the text, by a statement in the foreword, and by an indication at the beginning of the annex itself . 111 Copyright Government Electronics the current release of the SECAM Assessment Method is Version 1.50, dated July 1997. In January 1994, the EPIC (then called Industria
7、l Collaboration) began generating the Capability Maturity Model (CMM) for Systems Engineering (SE-CMM) and completed it as an initial release, Version 1.0, in December 1994. Version 1.0 of the SE-CMM Appraisal Method was released in June 1995. Following the initial release, one update was made to bo
8、th the EPIC SE-CMM and the SE-CMM Appraisal Method. The current release of the EPIC SE-CMM is Version 1.1 , dated November 1995; the current release of the SE- CMM Appraisal Method is Version 1.1 , dated 1996. In March 1996, an effort was initiated under the auspices of the EIA G-47 (Systems Enginee
9、ring) Committee to merge the current versions of the INCOSE SECAM and its Assessment Method with the current versions of the EPIC SE-CMM and its Appraisal Method. The resulting EIA Systems Engineering Capability Model (SECM) and SECM Appraisal Method will be proposed as a US national standard for th
10、e measurement and improvement of systems engineering capability. 1.2 Benefits Associated with the Use of this Standard Proper implementation of this Standard is intended to improve the capability to perform systems engineering. Improved capability enables an organization to: Reduce cycle time from c
11、oncept to deployed system products; Improve the match of deployed system product capability with stakeholder requirements; Reduce total ownership cost of system products; Reduce the number of engineering changes; Improve system quality; Improve communications among personnel involved in the engineer
12、ing of a system; Improve ability to sustain and upgrade system products after deployment; and Reduce development risks. By proper implementation, it is meant that: a) b) c) Processes, activities, and tasks of this Standard are appropriately tailored (see Annex A and EIA-73 1-2, EIA SECM Appraisal Me
13、thod); Skilled personnel are used to accomplish the purpose of this Standard as tailored; Users of this Standard have training and familiarity with the usage of this Standard. Copyright Government Electronics simple or complex; software intensive or not; precedented or unprecedented. It applies to s
14、ystems that may contain hardware, software, personnel, facilities, data, materials, services, or techniques. This Standard is applicable to the engineering of a new system or the reengineering of a legacy system, or portions thereof. This Standard is intended solely to be used for self-development,
15、self-improvement, and self-appraisal. Organizations should not apply this Standard to suppliers as a means of source selection or as a means of qualification to be a supplier. 2.4 Limitations This Standard is not intended to specifj the details of “how to” implement process activities. It does not s
16、pecifj the methods or tools a developer would use to accomplish required activities. The developer will select methods, techniques, and tools that are consistent with program or organization needs, directives, and procedures. Adherence to this Standard shall be entirely voluntary and within the disc
17、retion of individual organizations. This Standard does not prescribe the name, format, content, or structure of documentation. Throughout this Standard, the terms “document” or “documentation” are used to mean a collection of data regardless of its medium. This Standard is, to a large extent, a proc
18、ess-based systems engineering capability model. Process maturity indicators were developed first because they were deemed easiest to develop and had received the most attention in other efforts, e.g., IS0 initiatives, and other disciplines, e.g., software. This Standard also includes non-process ind
19、icators of systems engineering capability. These non-process indicators represent high leverage characteristics of systems engineering capability. Copyright Government Electronics a sixth, and lowest, level of capability is a default level that contains no questions. The numbering of each FA indicat
20、es the Category to which it belongs, as follows: TC 1.0 Systems Engineering Technical Category FA 1.1 Define Stakeholder and System Level Requirements FA 1.2 Define Technical Problem FA 1.3 Define Solution FA 1.4 Assess and Select FA 1.5 Integrate System FA 1.6 Verify System FA 1.7 Validate System T
21、C 2.0 Systems Engineering Management Category FA 2.1 FA 2.2 FA 2.3 FA 2.4 FA 2.5 FA 2.6 FA 2.7 FA 2.8 Plan and Organize Monitor and Control Integrate Disciplines Coordinate with Suppliers Manage Risk Manage Data Manage Configurations Ensure Quality TC 3.0 Systems Engineering Environment Category FA
22、3.1 Define and Improve the Systems Engineering Process FA 3.2 Manage Competency FA 3.3 Manage Technology FA 3.4 Manage Systems Engineering Support Environment Copyright Government Electronics & Information Technology Association Reproduced by IHS under license with GEIA Not for ResaleNo reproduction
23、 or networking permitted without license from IHS-,-,-EIA-73 1.1 Page 22 FA 1.1 Define Stakeholder and System Level Requirements A Focus Area for the Systems Engineering Technical Category Description: Define Stakeholder and System Level Requirements produces a validated set of system-level requirem
24、ents (technical, support, interface) which reflect stakeholder needs and expectations. To accomplish this purpose, the Focus Area includes collection and coordination of stakeholder needs, development of an operational concept, and analysis of needs and requirements. These practices are supported by
25、 definition of alternative and preferred system concepts developed in FA 1.3 - Define Solution. Stakeholders include customer/users, developers, producers, testers, suppliers, marketers, maintainers, disposers and others who may be affected by, or may affect, the system or product. Needs and expecta
26、tions are elicited, stimulated, analyzed, and communicated to obtain the system technical requirements which constitute a common, quantitative, understanding of what will satisfy all stakeholders. Define Stakeholder and System Level Requirements includes engaging all stakeholders in an ongoing dialo
27、gue to translate needs and expectations into a concept of operations, system concept and a verifiable set of requirements, technological limitations, cost drivers, time drivers and risks, which the stakeholders understand and which provide the basis for agreements between the acquirer/customer/user
28、and the developer. Suppliers and developers engage in a continuing solicitation of feedback from customer/users to establish and maintain the validity of requirements. Stakeholder needs, objectives, and requirements are analyzed in relation to mission operations, operational environments and desired
29、 system characteristics to derive alternative system concepts which unify the system feature, function, performance, and costs. System concepts are used to define and communicate requirements with the customer. The evolution and impact of evolving stakeholder requirements and technological constrain
30、ts and features on systems/products are planned and managed. Notes: Since this Focus Area supports the dialogue between those performing systems engineering and the customer/user, all other Focus Areas will use this Focus Area to keep stakeholders informed throughout the program life cycle. Customer
31、, as used here, denotes either a directly contracted customer, an internal customer, or a customer surrogate who represents a particular market segment in a market-driven, multi- customer industry. In addition to being identified and collected, needs and expectations are elicited (stimulated) from s
32、takeholders by such means as demonstrating new technology or improved methods for solving operational problems. This FA has strong interaction with development of system concepts in FA 1.3 and integrated with all technical category FAS to provide the customer interface. Outputs of this FA, such as s
33、ystem requirements, are baselined and controlled by the practices of FA 2.7 - Manage Configurations. References: Not Applicable. Themes of Define Stakeholder and System Level Requirements: 1.1-1 Stakeholder Needs 1.1-2 System Level Requirements Copyright Government Electronics & Information Technology Association Reproduced by IHS under license with GEIA Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-
