ImageVerifierCode 换一换
格式:PDF , 页数:140 ,大小:6.75MB ,
资源ID:754552      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-754552.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(GEIA EIA-731 1-2002 Systems Engineering Capability Model《系统工程能力模型》.pdf)为本站会员(孙刚)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

GEIA EIA-731 1-2002 Systems Engineering Capability Model《系统工程能力模型》.pdf

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-,-,-

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1