1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there
2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2014 SAE International All rights reserved. No part of this p
3、ublication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-497
4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/EIA632 TECHNICAL REPORT EIA-632 Issued 1999-01 Reaffirmed 2003-09 Processes for E
5、ngineering a System NOTICE This document has been taken directly from the original TechAmerica document and contains only minor editorial and format changes required to bring it into conformance with the publishing requirements of SAE Technical Standards. The release of this document is intended to
6、replace the original with the SAE International document. Any numbers established by the original document remain unchanged. The original document was adopted as an SAE publication under the provisions of the SAE Technical Standards Board (TSB) Rules and Regulations (TSB 001) pertaining to accelerat
7、ed adoption of specifications and standards. TSB rules provide for (a) the publication of portions of unrevised specifications and standards without consensus voting at the SAE committee level, and (b) the use of the existing specification or standard format. TechAmerica Standard Processes for Engin
8、eering a System EIA-632 (Upgrade and Revision of EIA/IS-632) January 1999 EIA-632 NOTICE TechAmerica Engineering Standards and Publications are designed to serve the public interest by eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement
9、 of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TechAmerica from manufacturing or selling products not conform
10、ing to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TechAmerica members, whether the standard is to be used either domestically or internationally. Standards and Publications are adopted by TechAmerica in
11、 accordance with the American National Standards Institute (ANSI) patent policy. By such action, TechAmerica does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This TechAmerica Standard is considered to have
12、International Standardization implications, but the ISO/IEC activity has not progressed to the point where a valid comparison between the TechAmerica Standard and the ISO/IEC document can be made. This Standard does not purport to address all safety problems associated with its use or all applicable
13、 regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Standards Proposal No. 3527-A, formulated under the cognizance of the EIA 632 Workin
14、g Group of the G-47 Systems Engineering Committee). This document is maintained under the ANSI/TechAmerica continuous maintenance program. Changes may be submitted at any time on any part of the standard using the TechAmerica Document Improvement Proposal at the back of this document or a similar me
15、thod containing the same information. These comments shall be acted on for revision of the standard at the first meeting following working group resolution of the comment. Published by 2010 TechAmerica Standards distributionis unlimited.EIA-632 iProcesses for Engineering a System CONTENTS FOREWORD .
16、 vii INTRODUCTION ix ACKNOWLEDGMENTS xi 1 SCOPE . 1 1.1 PURPOSE . 1 1.2 COVERAGE . 1 1.3 INTENDED APPLICATIONS 2 1.4 LIMITATIONS 2 2 NORMATIVE REFERENCES . 3 3 DEFINITIONS AND ACRONYMS 3 3.1 KEY TERMS . 3 3.2 ACRONYMS . 3 3.3 TERMINOLOGY . 3 4 REQUIREMENTS . 4 4.1 ACQUISITION AND SUPPLY . 6 4.1.1 Su
17、pply Process . 7 4.1.2 Acquisition Process 8 4.2 TECHNICAL MANAGEMENT 9 4.2.1 Planning Process 10 4.2.2 Assessment Process 14 4.2.3 Control Process 16 4.3 SYSTEM DESIGN . 19 4.3.1 Requirements Definition Process . 19 4.3.2 Solution Definition Process 23 4.4 PRODUCT REALIZATION . 26 4.4.1 Implementat
18、ion Process . 27 4.4.2 Transition to Use Process 29 4.5 TECHNICAL EVALUATION . 29 4.5.1 Systems Analysis Process . 30 4.5.2 Requirements Validation Process . 344.5.3 System Verification Process . 37 4.5.4 End Products Validation Process . 42 5 APPLICATION CONTEXT 43 5.1 ENTERPRISE FACTORS . 44 5.2 P
19、ROJECT FACTORS 44 5.2.1 Enterprise support 44 5.2.2 Project support of the technical processes . 45 5.3 EXTERNAL FACTORS . 45 5.4 INFLUENCE OF OTHER ENTERPRISE PROJECTS . 45 6 APPLICATION KEY CONCEPTS 46EIA-632 ii6.1 SYSTEM CONCEPT . 46 6.1.1 Building block 46 6.1.1.1 System element . 47 6.1.1.2 End
20、 product elements 476.1.1.3 Subsystem elements 48 6.1.1.4 Enabling product elements 48 6.1.2 Building block roles . 49 6.1.2.1 Specifications 50 6.1.2.2 Interface definition 52 6.1.2.3 Multidisciplinary teamwork 52 6.1.2.4 Risk management 53 6.1.2.5 Technical reviews 53 6.1.2.6 Cost collection and r
21、eporting. 54 6.2 SYSTEM STRUCTURE CONCEPT 55 6.2.1 Top-down development. 566.2.2 Bottom-up realization . 58 6.3 ENGINEERING LIFE CYCLE CONCEPT . 60ANNEX AGLOSSARY (NORMATIVE) 63 ANNEX BENTERPRISE-BASED LIFE CYCLE (INFORMATIVE) . 69 B.1 RELATIONSHIP TO ENGINEERING LIFE CYCLE PHASES . 69 B.2 PRODUCT E
22、VOLUTION 70 B.3 LIFE CYCLE CONSIDERATIONS 70 ANNEX CPROCESS TASK OUTCOMES (INFORMATIVE) 71 C.1 ACQUISITION AND SUPPLY TASK OUTCOMES . 71 C.2 TECHNICAL MANAGEMENT TASK OUTCOMES 74 C.3 SYSTEM DESIGN TASK OUTCOMES . 84 C.4 PRODUCT REALIZATION TASK OUTCOMES . 92 C.5 TECHNICAL EVALUATION TASK OUTCOMES .
23、94 ANNEX DPLANNING DOCUMENTS (INFORMATIVE) 105 D.1 SOURCE DOCUMENTS . 105 D.2 TECHNICAL DOCUMENTS . 105 D.3 ENTERPRISE OR PROJECT DOCUMENTS . 108 ANNEX ESYSTEM TECHNICAL REVIEWS (INFORMATIVE) . 110 ANNEX FUNPRECEDENTED AND PRECEDENTED DEVELOPMENT (INFORMATIVE) 112 ANNEX GREQUIREMENT RELATIONSHIPS (I
24、NFORMATIVE) 113 INDEX 117 EIA-632 iiiLIST OF FIGURES Figure 1.2Fundamental processes for engineering a system 1 Figure 1.3Application of this Standard 2 Figure 4aRelationship of processes for engineering a system . 4 Figure 4bRequirements for engineering a system 5 Figure 4.1Acquisition and Supply P
25、rocesses . 7 Figure 4.1.2Acquisition Process requirements 8 Figure 4.2Technical Management Processes . 10 Figure 4.2.1Planning Process requirements . 10 Figure 4.2.2Assessment Process requirements 14 Figure 4.2.3Control Process requirements . 17Figure 4.3System Design Processes 19 Figure 4.3.1Requir
26、ements Definition Process requirements 20 Figure 4.3.2Solution Definition Process requirements 23 Figure 4.4Product Realization Processes . 27 Figure 4.5Technical Evaluation Processes 30 Figure 4.5.1Systems Analysis Process requirements . 30 Figure 4.5.2Requirements Validation Process requirements .
27、 34 Figure 4.5.3System Verification Process requirements . 38Figure 5.0Context for application of this Standard 43 Figure 6.1System concept 46Figure 6.1.1Building block 47Figure 6.1.2.1Building block role - specifications . 50 Figure 6.1.2.3Building block role - teamwork . 52 Figure 6.1.2.5Building
28、block role - technical reviews . 54Figure 6.2Forming a system structure . 55 Figure 6.2.1aExample system structure . 57 Figure 6.2.1bTop-down development 58 Figure 6.2.2Bottom-up realization . 59 Figure B.1Enterprise-based life cycle phases 69 Figure F.1Approaches for unprecedented and precedented e
29、nd products 112 Figure G.1Requirement relationships 113 Figure G.2Role of specified requirements . 114 Figure G.3Development of enabling products . 115 Figure G.4Relationship between requirement types and elements of this Standard 116 EIA-632 ivLIST OF TABLES Table 6.1.1.4Examples of enabling produc
30、ts for each associated process . 49 Table 6.1.2.5Purposes of technical reviews . 54 Table 6.3Engineering life cycle phases . 62 Table C.1Requirement 1 (Supply Process - Product Supply) 71 Table C.2Requirement 2 (Acquisition Process - Product Acquisition) 72 Table C.3Requirement 3 (Acquisition Proces
31、s - Supplier Performance) . 73 Table C.4Requirement 4 (Planning Process - Process Implementation Strategy) 74 Table C.5Requirement 5 (Planning Process - Technical Effort Definition) . 75 Table C.6Requirement 6 (Planning Process - Schedule and Organization) . 76 Table C.7Requirement 7 (Planning Proce
32、ss - Technical Plans) . 77 Table C.8Requirement 8 (Planning Process - Work Directives) 78 Table C.9Requirement 9 (Assessment Process - Progress Against Plans and Schedules) . 78 Table C.10Requirement 10 (Assessment Process - Progress Against Requirements) . 79 Table C.11Requirement 11 (Assessment Pr
33、ocess - Technical Reviews) . 79 Table C.12Requirement 12 (Control Process - Outcomes Management) 80 Table C.13Requirement 13 (Control Process - Information Dissemination) . 83 Table C.14Requirement 14 (Requirements Definition Process - Acquirer Requirements) 84 Table C.15Requirement 15 (Requirements
34、 Definition Process - Other Stakeholder Requirements) 84 Table C.16Requirement 16 (Requirements Definition Process - System Technical Requirements) 85 Table C.17Requirement 17 (Solution Definition Process - Logical Solution Representations) . 87Table C.18Requirement 18 (Solution Definition Process -
35、 Physical Solution Representations) . 89 Table C.19Requirement 19 (Solution Definition Process - Specified Requirements) 91 Table C.20Requirement 20 (Implementation Process ) . 92 Table C.21Requirement 21 (Transition to Use Process) 93 Table C.22Requirement 22 (Systems Analysis Process - Effectivene
36、ss Analysis) 94 Table C.23Requirement 23 (Systems Analysis Process - Tradeoff Analysis) . 95 Table C.24Requirement 24 (Systems Analysis Process - Risk Analysis) 96 Table C.25Requirement 25 (Requirements Validation Process - Requirement Statements Validation) 97 Table C.26Requirement 26 (Requirements
37、 Validation Process - Acquirer Requirements) . 98 Table C.27Requirement 27 (Requirements Validation Process - Other Stakeholder Requirements) . 98 Table C.28Requirement 28 (Requirements Validation Process - System Technical Requirements) . 99 Table C.29Requirement 29 (Requirements Validation Process
38、 - Logical Solution Representations) 100 Table C.30Requirement 30 (System Verification Process - Design Solution Verification) . 101 Table C.31Requirement 31 (System Verification Process - End Product Verification) . 102 Table C.32Requirement 32 (System Verification Process - Enabling Product Readin
39、ess) 102 Table C.33Requirement 33 (End Products Validation Process) 104 Table E.1System technical reviews . 110 EIA-632 vLIST OF REQUIREMENTS Requirement 1Product Supply . 7 Requirement 2Product Acquisition 8 Requirement 3Supplier Performance . 9 Requirement 4Process Implementation Strategy . 10 Req
40、uirement 5Technical Effort Definition 11 Requirement 6Schedule and Organization . 12 Requirement 7Technical Plans 13 Requirement 8Work Directives . 13 Requirement 9Progress Against Plans and Schedules . 14 Requirement 10Progress Against Requirements 15 Requirement 11Technical Reviews . 16Requirement
41、 12Outcomes Management 17 Requirement 13Information Dissemination . 17 Requirement 14Acquirer Requirements 20 Requirement 15Other Stakeholder Requirements 21 Requirement 16System Technical Requirements 22 Requirement 17Logical Solution Representations . 23 Requirement 18Physical Solution Representat
42、ions . 24 Requirement 19Specified Requirements 26 Requirement 20Implementation 28 Requirement 21Transition to Use 29 Requirement 22Effectiveness Analysis . 31 Requirement 23Tradeoff Analysis . 32 Requirement 24Risk Analysis . 33 Requirement 25Requirement Statements Validation . 34 Requirement 26Acqu
43、irer Requirements Validation . 35Requirement 27Other Stakeholder Requirements Validation 35 Requirement 28System Technical Requirements Validation . 36 Requirement 29Logical Solution Representations Validation . 37Requirement 30Design Solution Verification 38 Requirement 31End Product Verification 3
44、9 Requirement 32Enabling Product Readiness . 40 Requirement 33End Products Validation . 42EIA-632viTHIS PAGE LEFT BLANKEIA-632viiForewordThis Standard is intended to enable an enterprise to strengthen its competitiveness in global markets byengineering and producing quality systems, and by deliverin
45、g its products on time at an affordable price orcost. The focus, therefore, is on conceptualizing, creating, and realizing a system and the products thatmake up a system.This Standard was developed as a joint project of the Electronic Industries Alliance (EIA) and theInternational Council on Systems
46、 Engineering (INCOSE). This effort was chartered by the G-47 SystemsEngineering Committee of EIA and has been designated as Project PN-3537. This Standard has beenapproved by the EIA Engineering Department Executive Committee.Intended uses of this Standard includea) benchmarking by an enterprise aga
47、inst the requirements of this Standard for engineering a system,or portion thereof;b) preparing enterprise standards , policies, and procedures for engineering a system;c) developing lower-tier industry- or domain-specific process standards;d) developing process capability and assessment models ;e)
48、establishing terminology and concepts for better communications;f) developing training and education curricula;g) preparing plans for actual development of a product.Use is not limited to specific disciplines, industry sectors, or technology domains.To provide each enterprise with the greatest degre
49、e of flexibility for adapting to changing environmentswhile maintaining the integrity of adopted processes, this Standarda) limits the set of required processes to those directly related to the technical aspects ofengineering systems;b) defines representative tasks associated with each process;c) includes the relevant information f
