1、 Reference number ISO/IEC/IEEE 24765:2017(E) INTERNATIONAL STANDARD ISO/IEC/ IEEE 24765 2ndedition Systems and software engineering Vocabulary Ingnierie des systmes et du logiciel Vocabulaire RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT, WITH THEIR COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIG
2、HTS OF WHICH THEY ARE AWARE AND TO PROVIDE SUPPORTING DOCUMENTATION. IN ADDITION, TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO- LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME STAN-
3、 DARDS TO WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS. ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland IEEE 2017 All rights reserved. Unless otherwise specified, or required in the context of its implementatio
4、n, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs
5、member body in the country of the requester ISO copyright office Institute of Electrical and Electronics Engineers, Inc z CP 401 3 Park Avenue, New York CH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USA Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org stds.iprieee.org www.iso.org ww
6、w.ieee.org ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved ISO/IEC/IEEE 24765 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved This document was developed under the Partner Standards Development Organization cooperation agreement between ISO and IEEE, as approved by Coun
7、cil Resolution 49/2007, and is submitted to a parallel enquiry vote by the ISO/IEC national bodies and IEEE. In accordance with the provisions of Council Resolution 21/1986 this document is circulated in the English language only. Conformment aux dispositions de la Rsolution du Conseil 21/1986, ce d
8、ocument est distribu en version anglaise seulement. ISO/IEC/IEEE 24765 iv ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Contents Page Table of Contents 1 Scope 1 1.1 General 1 1.2 Relationship of the print and internet-accessible versions . 1 1.3 Vocabulary structure . 1 1.4 PMI Glo
9、ssary provisions 2 2 Normative references 2 3 Terms, definitions, and abbreviated terms . 2 Annex A (informative) List of References 552 Bibliography . 553 ISO/IEC/IEEE 24765 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved List of Figures Figure 1 Activity group 11 Figure 2 Bathtub cu
10、rve 45 Figure 3 Block diagram . 50 Figure 4 Box Diagram 53 Figure 5 Bubble chart 55 Figure 6 Call graph . 60 Figure 7 Case construct 63 Figure 8 Category . 64 Figure 9 Data flow diagram 124 Figure 10 Data structure diagram . 128 Figure 11 Directed graph 150 Figure 12 Documentation tree 155 Figure 13
11、 Flowchart 199 Figure 14 If-then-else construct . 228 Figure 15 Input-process-output chart . 243 Figure 16 Modification request 300 Figure 17 Structure chart . 475 Figure 18 UNTIL construct . 526 Figure 19 Waterfall model . 545 Figure 20 Website . 546 Figure 21 WHILE construct 547 ISO/IEC/IEEE 24765
12、 vi ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC parti
13、cipate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmenta
14、l and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees
15、 of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Vo
16、lunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the informatio
17、n contained in its standards. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was draft
18、ed in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is called to the possibility that implementation of this standard may require the use of subject matter covered by patent rights. By publication of this standard, no position is taken
19、with respect to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or scope of patents or patent claims or determi
20、ning whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determin
21、ation of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards Association. Any trade name used in this document is information given for the convenience of users and do
22、es not constitute an endorsement. Use of IEEE Standards documents is wholly voluntary. IEEE documents are made available for use subject to important notices and legal disclaimers (see http:/standards.ieee.org/IPR/disclaimers.html for more information). For an explanation on the meaning of ISO speci
23、fic terms and expressions related to conformity assessment, as well as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL www.iso.org/iso/foreword.html. The committee responsible for this document is ISO/IE
24、C JTC 1, Information technology, SC 7, Software and systems engineering, in cooperation with the IEEE Computer Society Systems and Software Engineering Standards Committee, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE. Certain material contained in
25、ISO/IEC/IEEE 24765 is reproduced, with permission, from A Guide to the Project Management Body of Knowledge (PMBOK) Guide Fifth Edition, copyright 2013, Project Management Institute. This second edition cancels and replaces the first edition, published in 2010, and has been editorially revised. Revi
26、sions in terms and definitions published in this second edition have been previously approved through the vocabulary maintenance procedures of ISO/IEC JTC 1/SC7, in cooperation with the IEEE Computer Society. These revisions have been made available through the online vocabulary database used for th
27、is standard, maintained by the ISO/IEC JTC 1/SC7/SWG 22 Vocabulary Validation Team in cooperation with the IEEE Computer Society at puter.org/sevocab ISO/IEC/IEEE 24765 vii Introduction The systems and software engineering disciplines are continuing to mature while information technology advances. N
28、ew terms are being generated and new meanings are being adopted for existing terms. This document was prepared to collect and standardize terminology. Its purpose is to identify terms currently in use in the field and standard definitions for these terms. It is intended to serve as a useful referenc
29、e for those in the Information Technology field, and to encourage the use of systems and software engineering standards prepared by ISO/IEC JTC 1 and liaison organizations IEEE Computer Society and Project Management Institute (PMI). It provides definitions that are rigorous, uncomplicated, and unde
30、rstandable by all concerned. While it is useful to find the meaning of a term, no word stands in isolation. This document makes it possible to search for related concepts and to view how a term is used in definitions of other terms. Every effort has been made to use definitions from established syst
31、ems and software engineering standards of ISO JTC 1/SC 7 and its liaison organizations IEEE Computer Society and the PMI. When existing standards were found to be incomplete, unclear or inconsistent with other entries in the vocabulary, however, new, revised, or composite definitions have been devel
32、oped. Some definitions have been recast in a system, rather than software, context. The vocabulary is offered in both print and internet-accessible versions for ease of reference and to encourage use of the source standards for the vocabulary. The online vocabulary database used for this standard is
33、 maintained by the ISO/IEC JTC 1/SC7/SWG 22 Vocabulary Validation Team in cooperation with the IEEE Computer Society at puter.org/sevocab ISO/IEC/IEEE 24765 1 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Systems and software engineering Vocabulary 1Scope 1.1 General Consistent with
34、 ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. This document provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO/IEC JTC 1/SC 7, Systems and software engineeri
35、ng, and the IEEE Computer Society Systems and Software Engineering Standards Committee (IEEE-CS S2ESC). The scope of each concept defined has been chosen to provide a definition that is suitable for general application. In those circumstances where a restricted application is concerned, a more speci
36、fic definition might be needed. Terms have been excluded if they were: considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the def initions of the component words; and terms whose meaning in the inf ormati
37、on technology (IT) field could be directly inferred from their common English dictionary meaning. 1.2 Relationship of the print and internet-accessible versions The primary tool for maintaining this vocabulary is a database that is modified in a controlled fashion. Hosted by the IEEE Computer Societ
38、y, the SEVOCAB (systems and software engineering vocabulary) database is publicly accessible at puter.org/sevocab . ISO/IEC 24765 is issued periodically as a formal, published document reflecting a “snapshot“ of the database. The copyright notice provided with the database permits users to copy defi
39、nitions from the database as long as the source of the definition is cited. Permitting public use of the definitions in the database is intended to encourage the use of other ISO/IEC JTC 1 and IEEE systems and software engineering standards. 1.3 Vocabulary structure Entries in the vocabulary are arr
40、anged alphabetically. Blanks precede all other characters in alphabetizing. Hyphens and slashes (- and /) follow all other characters in alphabetizing. Preferred terms are shown in bold. Synonyms or admitted terms (terms with the same meaning as the preferred term), are listed under the preferred te
41、rm in plain text, and can be located by searching. Terms, definitions, and notes use spelling preferred in the US. The use of capital letters has been minimized and generally limited to proper names and acronyms. In some cases, the source standard uses another correct spelling (such as behaviour rat
42、her than behavior, on-line rather than online). Technical terms in English often change form from two words to a hyphenated word to a single word as they become more familiar, e.g., real time to real-time to realtime. Hence, other correct spellings and capitalization of the terms, according to a nat
43、ional standard, an authoritative general dictionary or accepted style guide, can be used with the definitions. An entry can consist of a single word, such as “software“; a phrase or compound term, such as “test case“; or an abbreviated term, such as “CDR“. Phrases are given in their natural order (t
44、est plan) rather than in reversed order (plan, test). Abbreviated terms can be listed separately as well as in parentheses following the source term. Terms that are verbs are shown without the infinitive marker “to“. ISO/IEC/IEEE 24765 2 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved
45、 Numerous terms collected in this vocabulary have multiple definitions from different sources in the broad domain of systems and software engineering. The domain of the definition is clarified by its source, listed immediately following the definition. After each term, numbered definitions are liste
46、d in order of preference, or from the most general to the more specific usages. The different definitions can show the use of a term as a noun, verb and adjective. This document includes references to the active source standards for each definition, so that the use of the term can be further explore
47、d. The sources of most of the definitions are ISO JTC 1/SC 7 or IEEE Computer Society standards and the PMI Glossary, Fifth Edition. Sources are listed in the Bibliography. Additional sources for definitions drawn from outside the scope of systems and software engineering are in Annex A, List of Ref
48、erences. In some cases, the same definition can also be found in other active or withdrawn standards. No source is shown if the original source standard has been withdrawn or archived and the definition has been retained in this vocabulary. Notes (comments), Examples, and Figures taken from the sour
49、ce standards have been included to clarify selected definitions. Cross-references are used to show a terms relationship to other terms in the dictionary: cf. refers to related terms that are not synonyms. 1.4 PMI Glossary provisions The Project Management Institute (PMI) Glossary definitions have been included without alteration in accordance with the copyright agreement. Some of these terms and de
