ISO IEC IEEE 24765-2017（原版可复制）.pdf

Systems and software engineering VocabularyIngnierie des systmes et du logiciel VocabulaireINTERNATIONAL STANDARDISO/IEC/IEEE24765Reference numberISO/IEC/IEEE 24765:2017(E)Second edition2017-09 ISO/IEC 2017 IEEE 2017 ISO/IEC 2017 All rights reservedii IEEE 2017 All rights reservedISO/IEC/IEEE 24765:2017(E)COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017,Published in Switzerland IEEE 2017Allrightsreserved.Unlessotherwisespecified,nopartofthispublicationmaybereproducedorutilizedinanyformorbyanymeans,electronicormechanical,includingphotocopyingandmicrofilm,withoutpermissioninwritingfromISO,IECorIEEEatthe respective address below.ISOcopyrightofficeInstituteofElectricalandElectronicsEngineers,IncCh.de Blandonnet 8 CP 401 3 Park Avenue,New YorkCH-1214 Vernier,Geneva,Switzerland NY 10016-5997,USATel.+41 22 749 01 11 Fax[phone] copyrightiso.orgstds.iprieee.orgwww.iso.orgwww.ieee.orgISO/IEC/IEEE 24765:2017(E)iiiISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedContents Page Foreword.viIntroduction.viii1Scope.11.1General.11.2Relationship of the print and internet-accessible versions.11.3Vocabulary structure.11.4PMI Glossary provisions.22Normative references.23Terms,definitions,and abbreviated terms.2Annex A(informative)List of References.516Bibliography.517 ISO/IEC/IEEE 24765:2017(E)ivISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedList of Figures Figure 1 Activity group.10Figure 2 Bathtub curve.43Figure 3 Block diagram.47Figure 4 Box Diagram.50Figure 5 Bubble chart.52Figure 6 Call graph.57Figure 7 Case construct.59Figure 8 Category.60Figure 9 Data flow diagram.116Figure 10 Data structure diagram.119Figure 11 Directed graph.140Figure 12 Documentation tree.144Figure 13 Flowchart.186Figure 14 If-then-else construct.213Figure 15 Input-process-output chart.227Figure 16 Modification request.281Figure 17 Structure chart.443Figure 18 UNTIL construct.491Figure 19 Waterfall model.509Figure 20 Website.510Figure 21 WHILE construct.511ISO/IEC/IEEE 24765:2017(E)vISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedISO/IEC/IEEE 24765:2017(E)viISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedForeword ISO(theInternationalOrganizationforStandardization)andIEC(theInternationalElectrotechnicalCommission)formthe specialized system for worldwide standardization.National bodies thatare members of ISOor IECparticipate in the development of International Standards through technical committees established by therespective organization to deal with particular fields of technical activity.ISO and IEC technical committeescollaborateinfieldsofmutualinterest.Otherinternationalorganizations,governmentalandnongovernmental,inliaisonwithISOandIEC,alsotakepartinthework.Inthefieldofinformationtechnology,ISOandIEChaveestablishedajointtechnicalcommittee,ISO/IECJTC1.IEEEStandardsdocumentsaredevelopedwithintheIEEESocietiesandtheStandardsCoordinatingCommitteesof the IEEE Standards Association(IEEESA)Standards Board.The IEEE develops its standards through aconsensusdevelopmentprocess,approvedbytheAmericanNationalStandardsInstitute,whichbringstogethervolunteers representing varied viewpoints and interests to achieve the final product.Volunteers are notnecessarilymembersoftheInstituteandservewithoutcompensation.WhiletheIEEEadministerstheprocessandestablishesrulestopromotefairnessintheconsensusdevelopmentprocess,theIEEEdoesnotindependentlyevaluate,test,orverifytheaccuracyofanyoftheinformationcontainedinitsstandards.Theproceduresusedtodevelopthisdocumentandthoseintendedforitsfurthermaintenancearedescribedinthe ISO/IEC Directives,Part1.In particular the different approval criteria needed for the different types ofdocument should be noted.This document was drafted in accordance with the editorial rules of theISO/IECDirectives,Part2(seewww.iso.org/directives).Attentioniscalledtothepossibilitythatimplementationofthisstandardmayrequiretheuseofsubjectmattercoveredbypatentrights.Bypublicationofthisstandard,nopositionistakenwithrespecttotheexistenceorvalidityofanypatentrightsinconnectiontherewith.ISO/IEEEisnotresponsibleforidentifyingessentialpatentsorpatentclaimsforwhichalicensemayberequired,forconductinginquiriesintothelegalvalidityorscopeofpatentsorpatentclaimsordeterminingwhetheranylicensingtermsorconditionsprovidedinconnectionwithsubmissionofaLetterofAssuranceoraPatentStatementandLicensingDeclarationForm,ifany,orinanylicensingagreementsarereasonableornondiscriminatory.Usersofthisstandardareexpresslyadvisedthatdeterminationofthevalidityofanypatentrights,andtheriskofinfringementofsuchrights,isentirelytheirownresponsibility.FurtherinformationmaybeobtainedfromISOortheIEEEStandardsAssociation.Anytradenameusedinthisdocumentisinformationgivenfortheconvenienceofusersanddoesnotconstituteanendorsement.UseofIEEEStandardsdocumentsiswhollyvoluntary.IEEEdocumentsaremadeavailableforusesubjecttoimportant notices and legal disclaimers(see http:/standards.ieee.org/IPR/disclaimers.html for moreinformation).Foranexplanationonthevoluntarynatureofstandards,themeaningofISOspecifictermsandexpressionsrelatedtoconformityassessment,aswellasinformationaboutISOsadherencetotheWorldTradeOrganization(WTO)principlesintheTechnicalBarrierstoTrade(TBT)seethefollowingURLwww.iso.org/iso/foreword.html.ThisdocumentwaspreparedbyTechnicalCommitteeISO/IECJTC1,Information technology,SC7,Software and systems engineering,incooperationwiththeIEEEComputerSocietySystemsandSoftwareEngineeringStandardsCommittee,underthePartnerStandardsDevelopmentOrganizationcooperationagreementbetweenISOandIEEE.CertainmaterialcontainedinISO/IEC/IEEE24765isreproduced,withpermission,fromA Guide to the Project Management Body of Knowledge(PMBOK)Guide Fifth Edition,copyright2013,ProjectManagementInstitute.Thissecondeditioncancelsandreplacesthefirstedition(ISO/IEC/IEEE24765:2010),andhasbeeneditoriallyrevised.Revisions in terms and definitions published in this second edition have been previously approvedthroughthevocabularymaintenanceproceduresofISO/IECJTC1/SC7,incooperationwiththeIEEEComputerSociety.Theserevisionshavebeenmadeavailablethroughtheonlinevocabularydatabaseusedforthisstandard,maintained by the ISO/IEC JTC 1/SC7/SWG 22 Vocabulary Validation Team in cooperation with the IEEEComputerSputer.org/sevocabISO/IEC/IEEE 24765:2017(E)viiISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedISO/IEC/IEEE 24765:2017(E)viiiISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedIntroduction The systems and software engineering disciplines are continuing to mature while information technologyadvances.New terms are being generated and new meanings are being adopted for existing terms.Thisdocumentwaspreparedtocollectandstandardizeterminology.Itspurposeistoidentifytermscurrently inuse in the field and standard definitions for these terms.It is intended to serve as a usefulreferenceforthose in the Information Technology field,and to encourage the use of systems and softwareengineeringstandardspreparedbyISO/IECJTC1andliaison organizationsIEEEComputerSocietyandProjectManagementInstitute(PMI).Itprovidesdefinitionsthatarerigorous,uncomplicated,andunderstandablebyallconcerned.Whileitisusefultofindthemeaningofaterm,nowordstandsinisolation.Thisdocumentmakesitpossibletosearchforrelatedconceptsandtoviewhowatermisusedindefinitionsofotherterms.EveryefforthasbeenmadetousedefinitionsfromestablishedsystemsandsoftwareengineeringstandardsofISO JTC 1/SC 7 and its liaison organizations IEEE Computer Society and the PMI.When existingstandardswere found to be incomplete,unclear or inconsistent with other entries in the vocabulary,however,new,revised,orcompositedefinitionshavebeendeveloped.Somedefinitionshavebeenrecastinasystem,ratherthansoftware,context.Thevocabularyisofferedinbothprintandinternetaccessibleversionsforeaseofreferenceandtoencourageuseofthesourcestandardsforthevocabulary.TheonlinevocabularydatabaseusedforthisstandardismaintainedbytheISO/IECJTC1/SC7/SWG22VocabularyValidationTeamincooperationwiththeIEEEComputerSputer.org/sevocabINTERNATIONAL STANDARD ISO/IEC/IEEE 24765:2017(E)1ISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedSystems and software engineering Vocabulary 1 Scope 1.1 General ConsistentwithISOvocabularystandards,eachtechnicalcommitteeisresponsibleforstandardterminologyinitsarea of specialization.This document provides a common vocabulary applicable to all systems and softwareengineeringworkfallingwithinthescopeofISO/IECJTC1/SC7,Software and systems engineering,andtheIEEEComputerSocietySystemsandSoftwareEngineeringStandardsCommittee(IEEECSS2ESC).Thescopeofeachconceptdefinedhasbeenchosentoprovideadefinitionthatissuitableforgeneralapplication.Inthosecircumstanceswherearestrictedapplicationisconcerned,amorespecificdefinitionmightbeneeded.Termshavebeenexcludediftheywere:consideredtobeparochialtoonegroupororganization;companyproprietaryortrademarked;multiwordtermswhosemeaningcouldbeinferredfromthedefinitionsofthecomponentwords;and termswhosemeaningintheinformationtechnology(IT)fieldcouldbedirectlyinferredfromtheircommonEnglishdictionarymeaning.1.2 Relationship of the print and internet-accessible versionsTheprimarytoolformaintainingthisvocabularyisadatabasethatismodifiedinacontrolledfashion.HostedbytheIEEEComputerSociety,theSEVOCAB(systemsandsoftwareengineeringvocabulary)databaseispubliclyaccessible at puter.org/sevocab ISO/IEC/IEEE 24765 is issued periodically as a formal,publisheddocumentreflectingasnapshotofthedatabase.Thecopyrightnoticeprovidedwiththedatabasepermitsuserstocopydefinitionsfromthedatabaseaslongasthe source of the definition is cited.Permitting public use of the definitions in the database is intended toencouragetheuseofotherISO/IECJTC1andIEEEsystemsandsoftwareengineeringstandards.1.3 Vocabulary structureEntries in the vocabulary are arranged alphabetically.Blanks precede all other characters in alphabetizing.Hyphensandslashes(and/)followallothercharactersinalphabetizing.Preferredtermsareshowninbold.Synonymsoradmittedterms(termswiththesamemeaningasthepreferredterm),arelistedunderthepreferredterminplaintext,andcanbelocatedbysearching.Terms,definitions,andnotesusespellingpreferredintheUS.Theuseofcapitallettershasbeenminimizedandgenerallylimitedtopropernamesandacronyms.Insomecases,thesourcestandardusesanothercorrectspelling(suchasbehaviourratherthanbehavior,onlineratherthanonline).TechnicaltermsinEnglishoftenchangeformfromtwowordstoahyphenatedwordtoasinglewordastheybecomemorefamiliar,e.g.,realtimetorealtimetorealtime.Hence,other correct spellings and capitalization ofthe terms,according to a national standard,anauthoritativegeneraldictionaryoracceptedstyleguide,canbeusedwiththedefinitions.Anentrycanconsistofasingleword,suchassoftware;aphraseorcompoundterm,suchastestcase;oranabbreviatedterm,suchasCDR.Phrasesaregivenintheirnaturalorder(testplan)ratherthaninreversedorder(plan,test).Abbreviatedtermscanbelistedseparatelyaswellasinparenthesesfollowingthesourceterm.Termsthatareverbsareshownwithouttheinfinitivemarkerto.ISO/IEC/IEEE 24765:2017(E)2ISO/IEC2017AllrightsreservedIEEE2017AllrightsreservedAftereachterm,numbereddefinitionsarelistedinorderofpreference,orfromthemostgeneraltothemorespecificusages.Thedifferentdefinitionscanshowtheuseofatermasanoun,verbandadjective.Thisdocumentincludesreferencestotheactivesourcestandardsforeachdefinition,sothattheuseofthetermcanbefurtherexplored.ThesourcesofmostofthedefinitionsareISOJTC1/SC7orIEEEComputerSocietystandards and the PMI Glossary,Fifth Edition.Sources are listed in the Bibliography.Additional sources fordefinitionsdrawnfromoutsidethescopeofsystemsandsoftwareengineeringareinAnnexA,ListofReferences.Insomecases,thesamedefinitioncanalsobefoundinotheractiveorwithdrawnstandards.Nosourceisshownifthe original source standard has been withdrawn or archived and the definition has been retained in thisvocabulary.Notes(comments),Examples,andFigurestakenfromthesourcestandardshavebeenincludedtoclarifyselecteddefinitions.Crossreferencesareusedtoshowatermsrelationshiptoothertermsinthedictionary:cf.referstorelatedtermsthatarenotsynonyms.1.4 PMI Glossary provisionsThe Project Management Institute(PMI)Glossary definitions have been included without alteration inaccordancewiththecopyrightagreement.SomeofthesetermsanddefinitionsarenotwordedaccordingtoISO/IECorIEEEstyles.Manyofthesedefinitionsincludeexplanatorymaterial.Forotherterms and otherdefinitionsthathaveISO/IECandIEEEstandardsastheirsource,explanatorymatterisshownintheNotesandExamples.2 Normative references Therearenonormativereferencesinthisdocument.NOTEThe definitions in this document are drawn from normative standards and informative guidancedocuments,including ISO/IEC Technical Reports(TR).Where terms have multiple definitions,users shouldconsultthesourcestandardsforfurtherinformationonappropriateusagewithinaspecificcontext.3 Terms,definitions,and abbreviated terms Forthepurposesofthisdocument,thefollowingtermsanddefinitionsapply.ISO,IECandIEEEmaintainterminologicaldatabasesforuseinstandardizationatthefollowingaddresses:IECElectropedia:availableathttp:/www.electropedia.org ISOOnlinebrowsingplatform:availableathttp:/www.iso.org/obp IEEEStandardsDictionaryOnline:availableathttp:/dictionary.ieee.org3.1 1GL 1.firstgenerationlanguage cf.machinelanguage3.2 2GL 1.secondgenerationlanguagecf.assemblylanguage3.3 3D 1.threedimensionalISO/IEC/IEEE23026:2015SystemsandsoftwareengineeringEngineeringandmanagementofwebsitesforsystems,software,andservicesinformation3.4 3GL 1.thirdgenerationlanguagecf.highorderlanguageISO/IEC/IEEE 24765:2017(E)3ISO/IEC2017AllrightsreservedIEEE2017Allrightsreserved3.5 4GL 1.fourthgenerationlanguage3.6 5GL 1.fifthgenerationlanguage3.7 language 1.definitionsofconceptsandrulesforthespecificationofanODPsystemfromtheviewpointISO/IEC107463:2009InformationtechnologyOpenDistributedProcessingReferenceModel:Architecture,4.2.1.1Note1toentry:Thus,engineeringlanguage:definitionsofconceptsandrulesforthespecificationofanODPsystemfromtheengineeringviewpoint.3.8 domain 1.setofobjects,eachofwhichisrelatedbyacharacterizingrelationshiptoacontrollingobjectISO/IEC107462:2009 Information technology Open Distributed Processing Reference Model:Foundations,10.3 3.9 federation munityofdomains ISO/IEC 10746-3:2009 Information technology Open Distributed Processing Reference Model:Architecture,5.1.2 3.10 group 1.setofobjectswithaparticularcharacterizingrelationship ISO/IEC 10746-2:2009 Information technology Open Distributed Processing Reference Model:Foundations,10.1 3.11 interceptor 1.engineeringobjectinachannel,placedataboundarybetweendomains ISO/IEC 10746-3:2009 Information technology Open Distributed Processing Reference Model:Architecture,8.1.11 Note1toentry:Aninterceptorperformscheckstoenforceormonitorpoliciesonpermittedinteractionsbetweenbasicengineeringobjectsindifferentdomains;performstransformationstomaskdifferencesininterpretationofdatabybasicengineeringobjectsindifferentdomains.Anintersubnetworkrelayisanexampleofaninterceptor3.12 pattern 1.abstractspecificationofacompositionofobjectsthatresultsinanyinstanceofthecompositionhavingagivenproperty,na