《IEEE-1320.1-1998.pdf》由会员分享,可在线阅读,更多相关《IEEE-1320.1-1998.pdf(115页珍藏版)》请在三一文库上搜索。
1、IEEE Std 1320.1-1998 IEEE Standard for Functional Modeling LanguageSyntax and Semantics for IDEF0 Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved 25 June 1998 IEEE-SA Standards Board Abstract: IDEF0 function modeling is designed to represent the decisions, acti
2、ons, and activities of an existing or prospective organization or system. IDEF0 graphics and accom-panying texts are presented in an organized and systematic way to gain understanding, support analysis, provide logic for potential changes, specify requirements, and support system-level design and in
3、tegration activities. IDEF0 may be used to model a wide variety of systems, composed of people, machines, materials, computers, and information of all varieties and structured by the relationships among them, both automated and nonautomated. For new systems, IDEF0 may be used first to define require
4、ments and to specify functions to be carried out by the future system. As the basis of this architecture, IDEF0 may then be used to design an implementation that meets these requirements and performs these functions. For existing systems, IDEF0 can be used to analyze the functions that the system pe
5、rforms and to record the means by which these are done. Keywords: enterprise, functional modeling language, IDEF0, language, modeling language _ The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright 1998 by the Institute of Electrica
6、l and Electronics Engineers, Inc. All rights reserved. Published 1998. Printed in the United States of America. ISBN 0-7381-0340-3 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE St
7、andards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards deve
8、loped within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an interest in participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE St
9、andard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through
10、 developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its c
11、ontents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affilia
12、tion with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the n
13、eed for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of all concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of
14、 interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. Comments on standards and requests for
15、interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc.,
16、provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (978) 750-8400. Permis- sion to photocopy portions of any individual standard for
17、educational classroom use can also be obtained through the Copyright Clearance Center. Note: Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to t
18、he existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Co
19、pyright 1998 IEEE. All rights reserved. iii Introduction (This introduction is not part of IEEE Std 1320.1-1998, IEEE Standard for Functional Modeling LanguageSyntax and Semantics for IDEF0.) This standard formally documents the Integration Definition 0 (IDEF0) language for function models in two pa
20、rts. The body of this standard describes the syntax and semantics of the IDEF0 language that are required to draw the physical diagrams of a specific IDEF0 model. Annex B describes the syntax and semantics of the IDEF0 language as an abstract formal structure and, therefore, provides the foundation
21、for the specifics found in the body of the standard. The diagrams discussed by the standard are real instantiations in a concrete model of the mathematical formalisms of the IDEF0 Language Abstract Formalization (the “language formalization”). Background During the 1970s, the US Air Force Program fo
22、r Integrated Computer Aided Manufacturing (ICAM) sought to increase manufacturing productivity through systematic application of computer technology. The ICAM program identified the need for better analysis and communication techniques for people involved in improving manufacturing productivity. As
23、a result, the ICAM program developed a series of modeling methodologies known as the ICAM Definition (IDEF) methods, which include a) IDEF0, used to produce a function model. A function model is a structured representation of the functions within a system or subject area. b) IDEF1, used to produce a
24、n information model. An information model represents the structure and semantics of information within a system or subject area. c) IDEF2, used to produce a dynamics model. A dynamics model represents the behavior of a system or subject area as it varies over time. IDEF0 was derived from a well-esta
25、blished graphical modeling method known as the Structured Analysis and Design Technique (SADT). IDEF0 was developed by the originators of SADT, notably Douglas T. Ross, under the ICAM program. In 1983, the US Air Force Integrated Information Support System program enhanced the IDEF1 information mode
26、ling technique to develop IDEF1 extended (IDEF1X), a semantic data modeling method. Continued IDEF method developments followed to address needs for additional analytic methods. These follow-on developments have been directed toward providing a mutually supportive family of methods that are applicab
27、le to a broad range of enterprise improvement and integration strategies (e.g., concurrent engineering, total quality management, business reengineering). Reflecting this general applicability, the IDEF acronym has been recast to refer to an integrated family of Integration Definition methods. Curre
28、ntly, IDEF0 and IDEF1X techniques are widely used in the government, industrial, and commercial sectors, supporting modeling efforts for a wide range of enterprises and application domains. IDEF0 has been widely adopted as the function modeling method of choice in large number of both military and n
29、onmilitary organizations in both North America and Europe. In 1991, the National Institute of Standards and Technology (NIST) received support from the US Department of Defense, Office of Corporate Information Management (DoD/CIM), to develop Federal Information Processing Standards (FIPS) for model
30、ing techniques for use by the federal government. One Copyright 1998 IEEE. All rights reserved. iv product of this effort was FIPS PUB 183, Integration Definition for Function Modeling (IDEF0) B2.a This FIPS document was based on the IDEF specification manuals published by the US Air Force in the ea
31、rly 1980s. At the same time, NIST also published FIPS PUB 184, Integration Definition for Information Modeling (IDEF1X) B3, to support data modeling for the federal government. In 1993, the Institute of Electrical and Electronics Engineers (IEEE) Computer Society initiated a project to establish IDE
32、F standards across both industry and government within the standards framework of the American National Standards Institute (ANSI). IEEE Std 1320.1-1998 for IDEF0 function models, based on FIPS PUB 183 B2, is a result of that effort. This standard is explicitly oriented to the presentation of an IDE
33、F0 model on paper pages; development of an IDEF0 standard for other presentation media is deliberately not addressed by this document. However, integrated into this standard is a mathematically founded formalization of an IDEF0 model. This formalization allows users to separate what they conceive in
34、 conceptual space, that is, the model itself, from their presentation of that model and from their presentation media. In earlier work, the IDEF0 diagram was not considered as something that should or could be distinguished from the paper page that presents that diagram. However, the current formali
35、zation allows (indeed, forces) users to separate the abstract structure of an IDEF0 model from the physical structure of the presentation of that model using sheets of paper. An important conceptual and notational difference between this work and earlier work is the clear distinction between an IDEF
36、0 graphic diagram and the medium, e.g., a page of paper, that is used to present that diagram. New terminology has been presented to ensure that this distinction can be easily maintained, and a more robust categorization of both the components of an IDEF0 model and of an IDEF0 diagram has been intro
37、duced. This terminology ensures that the usage presented in the body of this standard is consistent with the formalization presented in Annex B. In addition, these changes to the IDEF0 vocabulary will facilitate the development of IDEF0 presentations in digital or other media. The IDEF0 approach IDE
38、F0 includes both a modeling language and a comprehensive methodology for developing models. This standard addresses only the syntax and semantics of the modeling language itself. In addition to definition of the IDEF0 language, the IDEF0 methodology also prescribes procedures and techniques for deve
39、loping and interpreting models, including ones for data gathering, diagram construction, review cycles, and documentation. IDEF0 function modeling is designed to represent the decisions, actions, and activities of an existing or prospective organization or system. For all its apparent simplicity, th
40、e method is surprisingly powerful and effective. Like most modeling methods, the primary component of IDEF0 is a graphical language whose constructs are intended to convey information of a certain sort. IDEF0 graphics and accompanying texts are presented in an organized and systematic way to gain un
41、derstanding, support analysis, provide logic for potential changes, specify requirements, and support systems-level design and integration activities. IDEF0 may be used to model a wide variety of systems, composed of people, machines, materials, computers, and information of all varieties and struct
42、ured by the relationships among them, both automated and nonautomated. For new systems, IDEF0 may be used first to define requirements and to specify functions to be carried out by the future system. As the basis of this architecture, IDEF0 may then be used to design an implementation that meets the
43、se requirements and performs these functions. For aThe numbers in brackets correspond to those of the bibliography in Annex A. Copyright 1998 IEEE. All rights reserved. v existing systems, IDEF0 can be used to analyze the functions that the system performs and to record the means by which these are
44、done. The result of applying IDEF0 to a system is a model that consists of a hierarchical series of diagrams, with accompanying explanatory text, illuminating graphical, and defining glossary pages that are cross- referenced to these diagrams. The two primary modeling components of a diagram are fun
45、ctions (represented by named boxes) and the physical and data objects that interrelate those functions (represented by labeled arrows). As a function modeling language, IDEF0 has these characteristics: a) It is comprehensive and expressive, capable of graphically representing a wide variety of busin
46、ess, manufacturing, and other types of enterprise operations to any level of detail. b) It is a coherent and simple language, allowing rigorous and precise expression and promoting consistency of usage and interpretation. c) It enhances communication among analysts, architects, developers, managers,
47、 and users through its ease of learning and its emphasis on hierarchical exposition of detail. d) It is well-tested and proven through many years of use by the USAir Force and other government agencies and by private industry. e) It can be generated by a variety of computer-based tools; several comm
48、ercial products specifically support development and analysis of IDEF0 diagrams and models. As a system engineering technique, IDEF0 may be used for performing and managing needs analysis, benefits analysis, requirements definition, functional analysis, systems design, maintenance, and baselines for
49、 continuous improvement. IDEF0 models provide a “blueprint” of functions and their interfaces that must be captured and understood in order to make systems engineering decisions that are logical, affordable, integratable, and achievable. When used in a systematic way, IDEF0 provides a systems engineering approach to a) Performing systems analysis and design at all levels, including the entire enterprise, a system, or a subject area; b) Producing reference documentation concurrent with development to serve as a basis for integrating new systems or improving e
链接地址:https://www.31doc.com/p-3772174.html