IEEE 31320-1-2012 Information technology - Modeling Languages - Part 1 Syntax and Semantics for IDEF0.pdf

1、 Reference numberISO/IEC/IEEE 31320-1:2012(E)IEEE 1998INTERNATIONAL STANDARD ISO/IEC/IEEE31320-1First edition2012-09-15Information technology Modeling Languages Part 1: Syntax and Semantics for IDEF0 Technologies de linformation Langages de modlisation Partie 1: Syntaxe et smantique pour IDEF0 ISO/I

2、EC/IEEE 31320-1:2012(E) COPYRIGHT PROTECTED DOCUMENT IEEE 1998 All rights 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 IS

3、O, IEC or IEEE at the respective address below. ISO copyright office IEC Central Office Institute of Electrical and Electronics Engineers, Inc. Case postale 56 3, rue de Varemb 3 Park Avenue, New York CH-1211 Geneva 20 CH-1211 Geneva 20 NY 10016-5997, USA Tel. + 41 22 749 01 11 Switzerland E-mail st

4、ds.iprieee.org Fax + 41 22 749 09 47 E-mail inmailiec.ch Web www.ieee.org E-mail copyrightiso.org Web www.iec.ch Web www.iso.org Published in Switzerland ii IEEE 1998 All rights reservedISO/IEC/IEEE 31320-1:2012(E) IEEE 1998 All rights reserved iiiForeword ISO (the International Organization for Sta

5、ndardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organiz

6、ation to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology

7、, 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 of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus devel

8、opment process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the pr

9、ocess 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 information contained in its standards. The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International

10、 Standards adopted by the joint technical committee are circulated to national 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

11、 the use of subject matter covered by patent rights. By publication of 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

12、 required, for conducting inquiries into the legal validity or scope of 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

13、agreements are reasonable or non-discriminatory. Users of this standard 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

14、 Association. ISO/IEC/IEEE 31320-1 was prepared by the Software (978) 750-8400. Permis-sion to photocopy portions of any individual standard for educational classroom use can also be obtainedthrough the Copyright Clearance Center.Note: Attention is called to the possibility that implementation of th

15、is standard may requireuse of subject matter covered by patent rights. By publication of this standard, no position istaken with respect to the 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 requ

16、iredby an IEEE standard or for conducting inquiries into the legal validity or scope of thosepatents that are brought to its attention.Copyright 1998 IEEE. All rights reserved.iiISO/IEC/IEEE 31320-1:2012(E) Copyright 1998 IEEE. All rights reserved. iiiIntroduction(This introduction is not part of IE

17、EE Std 1320.1-1998, IEEE Standard for Functional Modeling LanguageSyntaxand Semantics for IDEF0.)This standard formally documents the Integration Definition 0 (IDEF0) language for function models intwo parts. The body of this standard describes the syntax and semantics of the IDEF0 language that are

18、required to draw the physical diagrams of a specific IDEF0 model. Annex B describes the syntax andsemantics of the IDEF0 language as an abstract formal structure and, therefore, provides the foundationfor the specifics found in the body of the standard. The diagrams discussed by the standard are rea

19、linstantiations in a concrete model of the mathematical formalisms of the IDEF0 Language AbstractFormalization (the “language formalization”).BackgroundDuring the 1970s, the US Air Force Program for Integrated Computer Aided Manufacturing (ICAM)sought to increase manufacturing productivity through s

20、ystematic application of computer technology.The ICAM program identified the need for better analysis and communication techniques for peopleinvolved in improving manufacturing productivity.As a result, the ICAM program developed a series of modeling methodologies known as the ICAMDefinition (IDEF)

21、methods, which includea) IDEF0, used to produce a function model. A function model is a structured representation of thefunctions within a system or subject area.b) IDEF1, used to produce an information model. An information model represents the structureand semantics of information within a system

22、or subject area.c) IDEF2, used to produce a dynamics model. A dynamics model represents the behavior of asystem or subject area as it varies over time.IDEF0 was derived from a well-established graphical modeling method known as the Structured Analysisand Design Technique (SADT). IDEF0 was developed

23、by the originators of SADT, notably Douglas T.Ross, under the ICAM program. In 1983, the US Air Force Integrated Information Support Systemprogram enhanced the IDEF1 information modeling technique to develop IDEF1 extended (IDEF1X), asemantic data modeling method.Continued IDEF method developments f

24、ollowed to address needs for additional analytic methods. Thesefollow-on developments have been directed toward providing a mutually supportive family of methods thatare applicable to a broad range of enterprise improvement and integration strategies (e.g., concurrentengineering, total quality manag

25、ement, business reengineering). Reflecting this general applicability, theIDEF acronym has been recast to refer to an integrated family of Integration Definition methods.Currently, IDEF0 and IDEF1X techniques are widely used in the government, industrial, and commercialsectors, supporting modeling e

26、fforts for a wide range of enterprises and application domains. IDEF0 hasbeen widely adopted as the function modeling method of choice in large number of both military andnonmilitary organizations in both North America and Europe.In 1991, the National Institute of Standards and Technology (NIST) rec

27、eived support from the USDepartment of Defense, Office of Corporate Information Management (DoD/CIM), to develop FederalInformation Processing Standards (FIPS) for modeling techniques for use by the federal government. OneCopyright 1998 IEEE. All rights reserved.ivproduct of this effort was FIPS PUB

28、 183, Integration Definition for Function Modeling (IDEF0) B2. aThis FIPS document was based on the IDEF specification manuals published by the US Air Force in theearly 1980s. At the same time, NIST also published FIPS PUB 184, Integration Definition for InformationModeling (IDEF1X) B3, to support d

29、ata modeling for the federal government.In 1993, the Institute of Electrical and Electronics Engineers (IEEE) Computer Society initiated a projectto establish IDEF standards across both industry and government within the standards framework of theAmerican National Standards Institute (ANSI). IEEE St

30、d 1320.1-1998 for IDEF0 function models, basedon FIPS PUB 183 B2, is a result of that effort.This standard is explicitly oriented to the presentation of an IDEF0 model on paper pages; development ofan IDEF0 standard for other presentation media is deliberately not addressed by this document. However

31、,integrated into this standard is a mathematically founded formalization of an IDEF0 model. Thisformalization allows users to separate what they conceive in conceptual space, that is, the model itself,from their presentation of that model and from their presentation media. In earlier work, the IDEF0

32、diagram was not considered as something that should or could be distinguished from the paper page thatpresents that diagram. However, the current formalization allows (indeed, forces) users to separate theabstract structure of an IDEF0 model from the physical structure of the presentation of that mo

33、del usingsheets of paper. An important conceptual and notational difference between this work and earlier work isthe clear distinction between an IDEF0 graphic diagram and the medium, e.g., a page of paper, that isused to present that diagram.New terminology has been presented to ensure that this di

34、stinction can be easily maintained, and a morerobust categorization of both the components of an IDEF0 model and of an IDEF0 diagram has beenintroduced. This terminology ensures that the usage presented in the body of this standard is consistentwith the formalization presented in Annex B. In additio

35、n, these changes to the IDEF0 vocabulary willfacilitate the development of IDEF0 presentations in digital or other media.The IDEF0 approachIDEF0 includes both a modeling language and a comprehensive methodology for developing models . Thisstandard addresses only the syntax and semantics of the model

36、ing language itself.In addition to definition of the IDEF0 language, the IDEF0 methodology also prescribes procedures andtechniques for developing and interpreting models, including ones for data gathering, diagramconstruction, review cycles, and documentation.IDEF0 function modeling is designed to

37、represent the decisions, actions, and activities of an existing orprospective organization or system. For all its apparent simplicity, the method is surprisingly powerfuland effective. Like most modeling methods, the primary component of IDEF0 is a graphical languagewhose constructs are intended to

38、convey information of a certain sort. IDEF0 graphics and accompanyingtext s are presented in an organized and systematic way to gain understanding, support analysis, providelogic for potential changes, specify requirements, and support systems-level design and integrationactivities. IDEF0 may be use

39、d 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 requirements andto specify functions to be car

40、ried out by the future system. As the basis of this architecture , IDEF0 maythen be used to design an implementation that meets the se requirements and performs the se functions. Fora The numbers in brackets correspond to those of the bibliography in Annex A.ISO/IEC/IEEE 31320-1:2012(E) Copyright 19

41、98 IEEE. All rights reserved. vexisting systems, IDEF0 can be used to analyze the functions that the system performs and to record themeans by which these are done.The result of applying IDEF0 to a system is a model that consists of a hierarchical series of diagrams, withaccompanying explanatory tex

42、t, illuminating graphical, and defining glossary pages that are cross-referenced to these diagrams . The two primary modeling components of a diagram are functions(represented by named boxes) and the physical and data objects that interrelate those functions(represented by labeled arrows).As a funct

43、ion modeling language, IDEF0 has the se characteristics:a) It is comprehensive and expressive, capable of graphically representing a wide variety ofbusiness, manufacturing , and other types of enterprise operations to any level of detail.b) It is a coherent and simple language, allowing rigorous and

44、 precise expression and promotingconsistency of usage and interpretation.c) It enhances communication among analysts, architects, developers, managers, and users throughits ease of learning and its emphasis on hierarchical exposition of detail.d) It is well-tested and proven through many years of us

45、e by the USAir Force and other governmentagencies and by private industry.e) It can be generated by a variety of computer -based tools; several commercial products specificallysupport development and analysis of IDEF0 diagrams and models.As a system engineering technique, IDEF 0 may be used for perf

46、orming and managing needs analysis,benefits analysis, requirements definition, functional analysis, systems design, maintenance, and baselinesfor continuous improvement. IDEF0 models provide a “blueprint ” of functions and their interfaces thatmust be captured and understood in order to make systems

47、 engineering decisions that are logical,affordable, integratable , and achievable. When used in a systematic way, IDEF 0 provides a systemsengineering approach toa) Performing systems analysis and design at all levels , including the entire enterprise, a system, ora subject area;b) Producing referen

48、ce documentation concurrent with development to serve as a basis forintegrating new systems or improving existing systems;c) Allowing collaborative team consensus to be achieved by shared understanding;d) Managing large and complex projects using qualitative measures of progress; ande) Providing a r

49、eference architecture for enterprise analysis, information engineering , and resourcemanagement.Typographic conventionsA word that has a special meaning for IDEF0 is italicized the first time that it is used in its specific sensefor IDEF0. There will be an entry in Clause 2 for each italicized word.ISO/IEC/IEEE 31320-1:2012(E) Copyright 1998 IEEE. All rights reserved.viFigure conventionsThe figures in this document have been prepared using the IDEF standard diagram form (SDF). The SDFand its use are documented by both FIPS PUB 183 B2 and FIPS PUB