1、IEEE Std 1220-2005(Revision ofIEEE Std 1220-1998)1220TMIEEE Standard for Application andManagement of the SystemsEngineering Process3 Park Avenue, New York, NY10016-5997, USAIEEE Computer SocietySponsored by theSoftware and Systems Engineering Standards Committee9 September 2005Print: SH95334PDF: SS
2、95334The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2005 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 9 September 2005. Printed in the United States of America.IEEE is a registered tradem
3、ark in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.NOTEAttention is called to the possibility that implementation of this standard may require use of subjectmatte
4、r covered by patent rights. By publication of this standard, no position is taken with respect to theexistence or validity of any patent rights in connection therewith. The IEEE shall not be responsible foridentifying patents for which a license may be required by an IEEE standard or for conducting
5、inquiries into thelegal validity or scope of those patents that are brought to its attention.Copyright 2005 IEEE. All rights reserved.iiiIntroductionHistoryIEEE Std 1220 was initially published in January 1995 as a trial-use standard. After the two-year trial-useperiod, the document was revised and
6、balloted in 1998 for full publication in 1999.The International Organization for Standardization (ISO) and the International Electrotechnical Commission(IEC) formed a joint body to collaborate in fields of mutual interest for worldwide standardization efforts.ISO/IEC established a joint technical co
7、mmittee for international standards development, ISO/IEC JTC 1,Information Technology. In parallel with IEEE Std 1220 developments, ISO/IEC JTC 1, Subcommittee 7(SC7), Software and Systems Engineering, began generation of ISO/IEC 15288:2002 B3.aISO/IEC15288:2002 provides a framework based on a broad
8、 set of processes that an organization or project mayemploy to perform or manage the stages of a systems life cycle. ISO/IEC 15288:2002 supports the full lifecycle of systemsfrom conception through retirementas well as the acquisition and supply of systems.It is the intent of ISO/IEC 15288:2002 to e
9、stablish standard life cycle process descriptions suitable for mostman-made systems. As such, the processes and terminology of the standard are defined at an appropriatelyhigh level of abstraction. ISO/IEC 15288:2002 does not prescribe, nor provide, detailed system engineeringprocess definitions or
10、methods and procedures to address detail process requirements derived from theapplication of this standard. ISO/IEC TR 19760:2003 B4, the companion guide for ISO/IEC 15288:2002,lists several standards, including IEEE Std 1220-1998, that cover engineering disciplines at a lower-tierlevel and are suit
11、able for implementation with ISO/IEC 15288:2002.This revision of IEEE Std 1220-1998 is a result of an ongoing harmonization of the standards of the IEEEComputer Societys Software and Systems Engineering Standards Committee (S2ESC) and thecorresponding international standards committee, ISO/IEC JTC1/
12、SC7. This initial alignment of IEEE Std1220-1998 with ISO/IEC 15288:2002 was developed in cooperation with ISO/IEC JTC1/SC7 and includedparticipation of the International Council on Systems Engineering (INCOSE). The next step towardsharmonization of these two standards would be the submission of IEE
13、E Std 1220-2005 for a “fast-track”ballot with ISO/IEC JTC1/SC7 followed by a coordinated revision.The IEEE Computer Society has embraced the top-level framework provided by ISO/IEC 15288:2002 andhas adopted ISO/IEC 15288 as IEEE Std 15288-2004. The IEEE Computer Society offered to align IEEEStd 1220
14、-1998 with ISO/IEC 15288:2002 to facilitate the joint use of the two standards to manage systemengineering efforts. The purpose of this revision of IEEE Std 1220-1998 is to identify key similarities anddifferences in the two standards and demonstrate how they can be used together while minimizing th
15、eimpact of ISO/IEC 15288:2002 on current IEEE Std 1220-1998 users who may not employ ISO/IEC15288:2002.The key differences between this version of the standard, IEEE Std 1220-2005, and the 1998 version are asfollows:a) Inclusion of explanations regarding key differences between IEEE Std 1220-1998 an
16、d ISO/IEC15288:2002 in areas such as terminology and structure b) Minimal adjustments to some IEEE Std 1220-1998 terms and definitions for alignment with ISO/IEC publication requirementsc) Clarification of the distinction between requirements and recommendations of the standardaThe numbers in bracke
17、ts correspond to those of the bibliography in Annex D.This introduction is not part of IEEE Std 1220-2005, IEEE Standard for Application and Management of the SystemsEngineering Process.ivCopyright 2005 IEEE. All rights reserved.d) Update of the conformance clause for alignment with IEEE standards s
18、tyle and rulesMost of the IEEE Std 1220-1998 content remains the same in this version. Explanations to facilitate use ofIEEE Std 1220 with ISO/IEC 15288:2002 are contained in a new Annex C.PurposeThis standard defines the requirements for an enterprises total technical effort related to development
19、ofproducts (including computers and software) and processes that will provide life cycle support (sustain andevolve) for the products. It prescribes an integrated technical approach to engineering a system and requiresthe application and management of the systems engineering process throughout a pro
20、duct life cycle. Thesystems engineering process is applied recursively to the development or incremental improvement of aproduct to satisfy market requirements and to simultaneously provide related life cycle processes for productdevelopment, manufacturing, test, distribution, operation, support, tr
21、aining, and disposal.The concept of systems engineering embodied in this standard provides an approach for productdevelopment in a system context. It is not meant to describe what an organizational entity called systemsengineering does or a job position for which a systems engineer is responsible. R
22、ather, it encompasses whatall organizational entities and all enterprise and project personnel must accomplish to produce a quality,competitive product that will be marketable, will provide an acceptable return on investment to theenterprise, will achieve stakeholder satisfaction, and will meet publ
23、ic expectations.The fundamental systems engineering objective is to provide high-quality products and services, with thecorrect people and performance features, at an affordable price, and on time. This involves developing,producing, testing, and supporting an integrated set of products (hardware, s
24、oftware, people, data, facilities,and material) and processes (services and techniques) that is acceptable to stakeholders, satisfies enterpriseand external constraints, and considers and defines the processes for developing, producing, testing,handling, operating, and supporting the products and li
25、fe cycle processes. This objective is achieved bysimultaneous treatment of product and process content to focus project resources and design decisions forthe establishment of an effective system design. This involves an integrated handling of all elements of asystem, including those related to manuf
26、acturing, test, distribution, operations, support, training, anddisposal.Notice to usersErrataErrata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL forerrata perio
27、dically.InterpretationsCurrent interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/index.html.PatentsAttention is called to the possibility that implementation of this standard may require use of subject mattercovered by patent rights. By publication of
28、 this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for identifyingCopyright 2005 IEEE. All rights reserved.vpatents or patent applications for which a license may be required to implement an IE
29、EE standard or forconducting inquiries into the legal validity or scope of those patents that are brought to its attention.ParticipantsAt the time this standard was completed, the IEEE 1220 Revision Working Group had the followingmembership:Teresa (Terry) Doran,Chair and EditorKen Crowder, ISO/IEC J
30、TC1/SC7 LiaisonJames Moore,IEEE CS Liaison to ISO/IEC JTC1/SC7Lorraine Pajerek,INCOSE Organizational RepresentativeThe following members of the individual balloting committee voted on this standard. Balloters may havevoted for approval, disapproval, or abstention.The following organizational represe
31、ntative voted on this standard:Lorraine Pajerek,INCOSEIn addition, this standard was coordinated with the following organizations:Werner AltmannJim ArmstrongStuart ArnoldRandy CaseJohn ClarkPaul CrollAlain FaisandierKevin ForsburgRich HarwellMark HenleyRon KohlJerome (Jerry) LakeJean-Philippe LeratE
32、lizabeth LotsuJohn H. MeeFrederick I. MoxleyJohn NapierSteve OlsonRobert PetersonKen PtackKaren RichterGarry RoedlerRobert J. SchaafRichard SchmidtRobert SkalameraThomas StaraiMark WilsonMatthew YoungEdward BartlettRichard BiehlStephen BlanchetteJuris BorzovsBruce BullockJoseph ButchkoDino ButoracKe
33、ith ChowAntonio M. CicuPaul CrollGregory DaichGeoffrey DarntonTaz DaughtreyMaulik DavePerry DeWeeseDr. Guru Dutt DhingraTeresa (Terry) DoranEinar DragstedtScott DuncanClint Early, Jr.Christof EbertWilliam EventoffJohn FendrichYaacov FensterRoger FujiiJean-Denis GorinLewis GrayMichael GrimleyMark Hei
34、nrichJohn HorchPeeya IwagoshiThomas M. KuriharaJoerg KampmannPiotr KarockiRon KenettCarol LongYuhai MaJoseph MarshallJacques MathotJames MooreDennis NickleLou PintoGerald RadackAnnette ReillyDavid RockwellGarry RoedlerHelmut SandmayrJames SandersRobert J. SchaafCarl SingerMitchell SmithLuca Spotorno
35、Thomas StaraiDavid WaldenJohn WalzOren YuenLi ZhangGEIA NDIA vi Copyright 2005 IEEE. All rights reserved.When the IEEE-SA Standards Board approved this standard on 20 March 2005, it had the followingmembership:Steve M. Mills, ChairRichard H. Hulett, Vice ChairDon Wright, Past ChairJudith Gorman, Sec
36、retary*Member EmeritusAlso included are the following nonvoting IEEE-SA Standards Board liaisons:Satish K. Aggarwal, NRC RepresentativeRichard DeBlasio, DOE RepresentativeAlan Cookson, NIST RepresentativeMichelle D. TurnerIEEE Standards Project EditorMark D. BowmanDennis B. BrophyJoseph BruderRichar
37、d CoxBob DavisJulian Forster*Joanna N. GueninMark S. HalpinRaymond HapemanWilliam B. HopfLowell G. JohnsonHerman KochJoseph L. Koepfinger*David J. LawDaleep C. MohlaPaul NikolichT. W. OlsenGlenn ParsonsRonald C. PetersenGary S. RobinsonFrank StoneMalcolm V. ThadenRichard L. TownsendJoe D. WatsonHowa
38、rd L. WolfmanCopyright 2005 IEEE. All rights reserved.viiContents1. Overview 11.1 Scope 11.2 Purpose. 21.3 How to use this standard 21.4 Organization of this standard. 62. Normative references. 63. Definitions and acronyms 73.1 Definitions 73.2 Acronyms. 104. General requirements. 104.1 Systems engi
39、neering process . 114.2 Policies and procedures for systems engineering 114.3 Planning the technical effort 124.4 Development strategies 134.5 Modeling and prototyping 134.6 Integrated repository 134.7 Integrated data package 144.8 Specification tree . 164.9 Drawing tree. 164.10 System breakdown str
40、ucture 174.11 Integration of the systems engineering effort 174.12 Technical reviews 194.13 Quality management 194.14 Product and process improvement.195. Application of systems engineering throughout the system life cycle 205.1 System definition stage 215.2 Preliminary design stage 255.3 Detailed d
41、esign stage . 295.4 Fabrication, assembly, integration, and test stage 325.5 Production and support stages . 345.6 Simultaneous engineering of life cycle processes . 366. The systems engineering process 376.1 Requirements analysis . 376.2 Requirements validation 436.3 Functional analysis. 456.4 Func
42、tional verification. 486.5 Synthesis 496.6 Design verification. 536.7 Systems analysis 576.8 Control . 61viiiCopyright 2005 IEEE. All rights reserved.Annex A (informative) The role of systems engineering within an enterprise 67Annex B (informative) The systems engineering management plan. 71Annex C
43、(informative) Use of IEEE Std 1220 in an ISO/IEC 15288:2002 context 79Annex D (informative) Bibliography. 87Copyright 2005 IEEE. All rights reserved.1IEEE Standard for Application and Management of the Systems Engineering Process1. Overview1.1 ScopeThis standard defines the interdisciplinary tasks t
44、hat are required throughout a systems life cycle totransform stakeholder needs, requirements, and constraints into a system solution. This standard is intendedto guide the development of systems for commercial, government, military, and space applications. Theinformation applies to a project within
45、an enterprise that is responsible for developing a product design andestablishing the life cycle infrastructure needed to provide for life cycle sustainment.This standard specifies the requirements for the systems engineering process (SEP) and its applicationthroughout the product life cycle. It doe
46、s not attempt to define the implementation of each system life cycleprocess, but addresses the issues associated with defining and establishing supportive life cycle processesearly and continuously throughout product development. In addition, the standard does not address the manycultural or quality
47、 variables that should be considered for successful product development. The standardfocuses on the engineering activities necessary to guide product development while ensuring that theproduct is properly designed to make it affordable to produce, own, operate, maintain, and eventually todispose of,
48、 without undue risk to health or the environment.The requirements of this standard are applicable to new products as well as incremental enhancements toexisting products. It applies to one-of-a-kind products, such as a satellite, as well as products that are mass-produced for the consumer marketplac
49、e. The requirements of this standard should be selectively applied foreach specific system-development project. The role of systems engineering within the enterpriseenvironment is described in Annex A.The content of this standard describes an integrated approach to product development, which represents thetotal technical effort for the following:a) Understanding the environments and the related conditions in which the product may be utilized andfor which the product should be designed to accommodateb) Defining product requirements in terms of functional and perfo
