1、 Reference numberISO/IEC/IEEE 24765:2010(E)ISO/IEC 2010IEEE 2010INTERNATIONAL STANDARD ISO/IEC/IEEE24765First edition2010-12-15Systems and software engineering Vocabulary Ingnierie des systmes et du logiciel Vocabulaire ISO/IEC/IEEE 24765:2010(E) PDF disclaimer This PDF file may contain embedded typ
2、efaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infr
3、inging Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were opt
4、imized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2010 IEEE 2010 All rig
5、hts reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO or IEEE at the respective address below. ISO copyright office
6、 Institute of Electrical and Electronics Engineers, Inc. Case postale 56 CH-1211 Geneva 20 3 Park Avenue, New York NY 10016-5997, USA Tel. + 41 22 749 01 11 E-mail stds.iprieee.org Fax + 41 22 749 09 47 Web www.ieee.org E-mail copyrightiso.org Web www.iso.org Published by ISO in 2011 Published in Sw
7、itzerland ii ISO/IEC 2010 All rights reserved IEEE 2010 All rights reservedISO/IEC/IEEE 24765:2010(E) ISO/IEC 2010 All rights reserved IEEE 2010 All rights reserved iiiContents Page Foreword . v Introduction vi 1 Scope 1 1.1 Relationship of the print and internet-accessible versions 1 1.2 Vocabulary
8、 structure . 1 1.3 PMI Glossary provisions. 2 2 Conformance . 2 3 Terms and definitions . 2 Annex A (informative) List of Source Standards . 404 Annex B (informative) List of References . 409 ISO/IEC/IEEE 24765:2010(E) iv ISO/IEC 2010 All rights reserved IEEE 2010 All rights reservedList of Figures
9、Page Figure 1 Activity . 9 Figure 2 Block Diagram . 35 Figure 3 Box diagram 38 Figure 4 Bubble chart 39 Figure 5 Call graph 42 Figure 6 Case construct 45 Figure 7 Categorization of software 46 Figure 8 Data flow diagram . 90 Figure 9 Data structure diagram . 92 Figure 10 Directed graph 110 Figure 11
10、 Documentation tree . 113 Figure 12 Flowchart . 145 Figure 13 Graph 158 Figure 14 If-then-else construct 168 Figure 15 Input-process-output chart 178 Figure 16 Modification request 222 Figure 17 Structure chart 349 Figure 18 UNTIL 387 Figure 19 Web site 399 Figure 20 WHILE . 400 ISO/IEC/IEEE 24765:2
11、010(E) ISO/IEC 2010 All rights reserved IEEE 2010 All rights reserved vForeword 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 p
12、articipate 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, governm
13、ental 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 Commit
14、tees 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
15、. Volunteers 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 inform
16、ation contained in its standards. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to n
17、ational bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. 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
18、this standard, no position is taken 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
19、 patents or patent claims or determining 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
20、 are expressly advised that determination 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. ISO/IEC/IEEE 24765 was prepared by Joint Technical Commit
21、tee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Software company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; terms whose meaning in the information te
22、chnology (IT) field could be directly inferred from their common English meaning. 1.1 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 Society, the SEVOCAB (
23、systems and software engineering vocabulary) database is publicly accessible at puter.org/sevocab. ISO/IEC 24765 is issued periodically as a formal, published International Standard reflecting a “snapshot“ of the database. The copyright notice provided with the database permits users to copy definit
24、ions 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.2 Vocabulary structure Entries in the vocabulary are arrang
25、ed alphabetically. Blanks precede all other characters in alphabetizing. Hyphens and slashes (- and /) follow all other characters in alphabetizing. An entry can consist of a single word, such as “software“; a phrase, such as “test case“; or an acronym, such as “CDR“. Phrases are given in their natu
26、ral order (test plan) rather than in reversed order (plan, test). Acronyms can be listed separately as well as in parentheses following the source term. Terms that are verbs are shown without the infinitive marker “to“. After each term, numbered definitions are listed in order of preference, or from
27、 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 International Standard includes references to the active source standards for each definition, so that the use of the term can be further explored. The sources of m
28、ost of the definitions are ISO JTC 1/SC 7 or IEEE Computer Society standards and the PMI Glossary, Fourth Edition. Sources are listed in Annex A. In some ISO/IEC/IEEE 24765:2010(E) 2 ISO/IEC 2010 All rights reserved IEEE 2010 All rights reservedcases, the same definition can also be found in other a
29、ctive 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 illustrations taken from the source standards have been included to clarify selected definitions. T
30、he following cross-references are used to show a terms relationship to other terms in the dictionary. Syn refers to a synonym: a term with the same meaning. Synonyms are listed under the preferred term and can be located by searching. cf. refers to related terms that are not synonyms. 1.3 PMI Glossa
31、ry provisions The Project Management Institute (PMI) Glossary definitions have been included without alteration in accordance with the copyright agreement. Many of these definitions include explanatory material. For other terms and other definitions that have ISO/IEC and IEEE standards as their sour
32、ce, explanatory matter is shown in the Notes and Examples. Many of the definitions from the PMI Glossary begin with a word or phrase in brackets, such as Process, Output/Input, Technique. These bracketed entries refer to the schema of the Project Management Institute, A Guide to the Project Manageme
33、nt Body of Knowledge (PMBOK1)Guide) Fourth Edition, which provides further explanation. 2 Conformance The definitions in this International Standard are drawn from normative standards and informative guidance documents, including ISO Technical Reports (TR). This International Standard may be used as
34、 a normative document for projects and organizations claiming conformance to the normative source standards. Where terms have multiple definitions, users should consult the source standards for further information on appropriate usage within a specific context. Annex B lists other references. Terms,
35、 definitions, and notes use spelling preferred in the USA. 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 rather than behavior, on-line rather than online). Other cor
36、rect spellings and capitalization of the terms, according to a national standard, an authoritative general dictionary or accepted style guide may be used with the definitions. 3 Terms and definitions 3.1 language 1. definitions of concepts and rules for the specification of an ODP system from the vi
37、ewpoint. ISO/IEC 10746-3:1996 Information technology Open Distributed Processing Reference Model: Architecture.4.2.1.1 NOTE Thus, engineering language is defined as “definitions of concepts and rules for the specification of an ODP system from the engineering viewpoint“. 1) PMBOK is a trademark of t
38、he Project Management Institute, Inc. which is registered in the United States and other nations. ISO/IEC/IEEE 24765:2010(E) ISO/IEC 2010 All rights reserved IEEE 2010 All rights reserved 33.2 federation 1. a community of domains. ISO/IEC 10746-3:1996, Information technology Open Distributed Process
39、ing Reference Model: Architecture.5.1.2 3.3 interceptor 1. an engineering object in a channel, placed at a boundary between domains. ISO/IEC 10746-3:1996, Information technology Open Distributed Processing Reference Model: Architecture.8.1.11 NOTE An interceptor performs checks to enforce or monitor
40、 policies on permitted interactions between basic engineering objects in different domains; performs transformations to mask differences in interpretation of data by basic engineering objects in different domains. An inter-subnetwork relay is an example of an interceptor. 3.4 1GL 1. first-generation
41、 language cf. machine language 3.5 2GL 1. second-generation language cf. assembly language 3.6 3GL 1. third-generation language cf. high order language 3.7 4GL 1. fourth-generation language 3.8 5GL 1. fifth-generation language 3.9 A-0 context diagram 1. the only context diagram that is a required fo
42、r a valid IDEF0 model, the A-0 diagram contains one box, which represents the top-level function being modeled, the inputs, controls, outputs, and mechanisms attached to this box, the full model name, the model name abbreviation, the models purpose statement, and the models viewpoint statement. IEEE
43、 Std 1320.1-1998 (R2004) IEEE Standard for Functional Modeling Language Syntax and Semantics for IDEF0 3.10 A4, A5 1. International Standard paper sizes. ISO/IEC 15910:1999, Information technology Software user documentation process.4.1 NOTE A4 is 210 mm by 297 mm and A5 is 148 mm by 210 mm; see ISO
44、 216:2007. 3.11 abend 1. abbreviation for abnormal end ISO/IEC/IEEE 24765:2010(E) 4 ISO/IEC 2010 All rights reserved IEEE 2010 All rights reserved3.12 abnormal end (abend) 1. termination of a process prior to completion cf. abort, exception 3.13 abort 1. to terminate a process prior to completion cf
45、. abnormal end (abend), exception 3.14 absolute address 1. an address that is permanently assigned to a device or storage location and that identifies the device or location without the need for translation or calculation. Syn: explicit address, specific address cf. relative address, relocatable add
46、ress, symbolic address, absolute assembler, absolute code, absolute instruction 3.15 absolute assembler 1. an assembler that produces absolute code cf. relocating assembler 3.16 absolute code 1. code in which all addresses are absolute addresses. Syn: specific code cf. relocatable code 3.17 absolute
47、 instruction 1. a computer instruction in which all addresses are absolute addresses cf. direct instruction, effective instruction, immediate instruction, indirect instruction 3.18 absolute loader 1. a loader that reads absolute machine code into main memory, beginning at the initial address assigne
48、d to the code by the assembler or compiler, and performs no address adjustments on the code cf. relocating loader 3.19 abstract class 1. a class that cannot be instantiated independently. IEEE Std 1320.2-1998 (R2004) IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97 (I
49、DEFobject).3.1.1 NOTE That is, instantiation must be accomplished via a subclass. A class for which every instance must also be an instance of a subclass in the cluster (a total cluster) is called an abstract class with respect to that cluster. 3.20 abstract data type 1. a data type for which only the properties of the data and the operations to be performed on the data are specified, without concern for how the data will be represented
