IEEE 31320-2-2012 Information technology - Modeling Languages - Part 2 Syntax and Semantics for IDEF1X97 (IDEFobject).pdf

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

2、our IDEF1X97(IDEFobject) ISO/IEC/IEEE 31320-2:2012(E) COPYRIGHT PROTECTED DOCUMENT IEEE 1999 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

3、 permission in writing from ISO, 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 7

4、49 01 11 Switzerland E-mail stds.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 1999 All rights reservedISO/IEC/IEEE 31320-2:2012(E) IEEE 1999 All rights reserved iiiForeword ISO (the Inte

5、rnational 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 participate in the development of International Standards through technical committees establi

6、shed 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, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the f

7、ield 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 of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its stand

8、ards 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. Volunteers are not necessarily members of the Institute and serve without compensation. Whi

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

10、Standards. Draft International 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 implementatio

11、n of this standard may require 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 cla

12、ims for which a license may be 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

13、, if any, or in any licensing 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

14、from ISO or the IEEE Standards Association. ISO/IEC/IEEE 31320-2 was prepared by the Software utilizes graphics to state the interface; and defines a declarative,directly executable Rule and Constraint Language for requests and realizations. IDEF1X97conceptualmodeling supports implementation by rela

15、tional databases, extended relational databases, objectdatabases, and object programming languages. IDEF1X97is formally defined in terms of first order logic. Aprocedure is given whereby any valid IDEF1X97model can be transformed into an equivalent theory in firstorder logic. That procedure is then

16、applied to a meta model of IDEF1X97to define the valid set of IDEF1X97models.Keywords: conceptual schema, data model, IDEF1X, IDEF1X97, identity style, information model, keystyle, object modelThe Institute of Electrical and Electronics Engineers, Inc.345 East 47th Street, New York, NY 10017-2394, U

17、SACopyright 1997 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 1997. Printed in the United States of AmericaPrint ISBN 0-7381-0341-1 SH94663PDF ISBN 0-7381-1405-7 SS94663No part of this publication may be reproduced in any form, in an electronic retriev

18、al system or otherwise, without theprior written permission of the publisher.ISO/IEC/IEEE 31320-2:2012(E) IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinat-ing Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of thecommittees

19、serve voluntarily and without compensation. They are not necessarily members of theInstitute. The standards developed within IEEE represent a consensus of the broad expertise on thesubject within the Institute as well as those activities outside of IEEE that have expressed an inter-est in participat

20、ing in the development of the standard.Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not implythat there are no other ways to produce, test, measure, purchase, market, or provide other goods andservices related to the scope of the IEEE Standard. Furthermore, the

21、 viewpoint expressed at thetime a standard is approved and issued is subject to change brought about through developments inthe state of the art and comments received from users of the standard. Every IEEE Standard is sub-jected to review at least every five years for revision or reaffirmation. When

22、 a document is morethan five years old and has not been reaffirmed, it is reasonable to conclude that its contents,although still of some value, do not wholly reflect the present state of the art. Users are cautioned tocheck to determine that they have the latest edition of any IEEE Standard.Comment

23、s for revision of IEEE Standards are welcome from any interested party, regardless ofmembership affiliation with IEEE. Suggestions for changes in documents should be in the form of aproposed change of text, together with appropriate supporting comments.Interpretations: Occasionally questions may ari

24、se regarding the meaning of portions of standards asthey relate to specific applications. When the need for interpretations is brought to the attention ofIEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards rep-resent a consensus of all concerned interests,

25、 it is important to ensure that any interpretation hasalso received the concurrence of a balance of interests. For this reason, IEEE and the members of itssocieties and Standards Coordinating Committees are not able to provide an instant response tointerpretation requests except in those cases where

26、 the matter has previously received formalconsideration.Comments on standards and requests for interpretations should be addressed to:Secretary, IEEE-SA Standards Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 08855-1331USAAuthorization to photocopy portions of any individual standard for internal or

27、 personal use isgranted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriatefee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contactCopyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 U

28、SA;(978) 750-8400. Permission to photocopy portions of any individual standard for educational class-room use can also be obtained through the Copyright Clearance Center.Note: Attention is called to the possibility that implementation of this standard mayrequire use of subject matter covered by pate

29、nt rights. By publication of this standard,no position is taken with respect to the existence or validity of any patent rights inconnection therewith. The IEEE shall not be responsible for identifying patents forwhich a license may be required by an IEEE standard or for conducting inquiries intothe

30、legal validity or scope of those patents that are brought to its attention.ISO/IEC/IEEE 31320-2:2012(E) ii Copyright 1999 IEEE. All rights reserved.Copyright 1999 IEEE. All rights reserved. iiiIntroductionThis introduction is not a part of IEEE Std 1320.2-1998, IEEE Standard for Conceptual Modeling

31、Language Syntax andSemantics for IDEF1X97(IDEFobject).BackgroundThe need for semantic models to represent conceptual schemas was recognized by the US Air Force in themid 1970s as a result of the Integrated Computer Aided Manufacturing (ICAM) Program. The objective ofthis program was to increase manu

32、facturing productivity through the systematic application of computertechnology. The ICAM program identified a need for better analysis and communication techniques for peo-ple involved in improving manufacturing productivity. As a result, the ICAM program developed a series oftechniques known as th

33、e ICAM Definition (IDEF) methods, which included the following: a) IDEF0, a technique used to produce a “function model,” which is a structured representation of theactivities or processes within the environment or system.b) IDEF1, a technique used to produce an “information model,” which represents

34、 the structure andsemantics of information within the environment or system.c) IDEF2, a technique used to produce a “dynamics model,” which represents the time-varying behav-ioral characteristics of the environment or system.IDEF0 and IDEF1X (the successor to IDEF1) continue to be used extensively i

35、n various government andindustry settings. IDEF2 is no longer used to any significant extent. The initial approach to IDEF information modeling (IDEF1) was published by the ICAM program in 1981,based on current research and industry needs B23.1The theoretical roots for this approach stemmed fromthe

36、early work of Dr. E. F. Codd on relational theory and Dr. P. P. S. Chen on the entity-relationship model.The initial IDEF1 technique was based on the work of Dr. R. R. Brown and Mr. T. L. Ramey of Hughes Air-craft and Mr. D. S. Coleman of D. Appleton Company, with critical review and influence by Mr

37、. C. W. Bach-man, Dr. P. P. S. Chen, Dr. M. A. Melkanoff, and Dr. G. M. Nijssen.In 1983, the US Air Force initiated the Integrated Information Support System (I2S2) project under the ICAMprogram. The objective of this project was to provide the enabling technology to integrate a network of het-eroge

38、neous computer hardware and software both logically and physically. As a result of this project andindustry experience, the need for an enhanced technique for information modeling was recognized. Application within industry had led to the development in 1982 of a Logical Database Design Technique(LD

39、DT) by R. G. Brown of the Database Design Group. The technique was also based on the relationalmodel of Dr. E. F. Codd and the entity-relationship model of Dr. P. P. S. Chen, with the addition of the gen-eralization concepts of J. M. Smith and D. C. P. Smith. LDDT provided multiple levels of models

40、and a setof graphics for representing the conceptual view of information within an enterprise. It had a high degree ofoverlap with IDEF1 features, included additional semantic and graphical constructs, and addressed informa-tion modeling enhancement requirements that had been identified under the I2

41、S2program. Under the techni-cal leadership of Dr. M. E. S. Loomis of D. Appleton Company, a substantial subset of LDDT was combinedwith the methodology of IDEF1 and published by the ICAM program in 1985 B15. This technique wascalled IDEF1 Extended or, simply, IDEF1X. In December 1993, the US governm

42、ent released a Federal Information Processing Standard (FIPS) forIDEF1X. FIPS PUB 184 B13 was based on the ICAM program description of IDEF1X and additional fea-tures originally included in LDDT. The FIPS clarified and corrected points in the ICAM publication, sepa-1The numbers in brackets correspon

43、d to those of the bibliography items listed in Annex A.ISO/IEC/IEEE 31320-2:2012(E) iv Copyright 1999 IEEE. All rights reserved.rated language syntax and semantics definition from practice and use issues, and provided a formal first-order language definition of IDEF1X. IEEE Std 1320.2-1998 continues

44、 the evolution of the IDEF1X language. It is driven by two needs. First,development of a national standard for the language makes the definition more accessible to organizationsthat do not follow US government standards and allows consideration and inclusion of features needed out-side the US federa

45、l government sector. Second, the needs of the users of a standard change over time as sys-tem development techniques and available technology continue to evolve. Some users adopt new conceptsearlier than others. To be valuable to the widest set of users, this standard needs to support a range of pra

46、c-tices, from those supported by the FIPS to those that are emerging as future drivers of integration. The change in the drivers of integration is being recognized by both government and private sector organiza-tions. Integration involves not only data but the operations performed on that data. The

47、emerging objectmodeling approaches seek to treat all activities as performed by collaborating objects that encompass boththe data and the operations that can be performed against that data. There is increasing interest in theseapproaches in both the government and private sectors. Original work done

48、 for the National Institute of Stan-dards and Technology (NIST) in 1994 and early 1995 by Robert G. Brown of the Database Design Group(DBDG) provides the basic elements required for a graceful evolution of IDEF1X toward full coverage ofobject modeling B5. The DBDG work analyzed the 1993 definition o

49、f IDEF1X and compared to it to the emerging consensusobject model. The analysis showed that The concepts of the current IDEF1X were a subset of those of the object model, The current IDEF1X contained restrictions that are unnecessary in the object model, and The object model contains significant new concepts. The work also showed that if the concepts of IDEF1X were more fully developed, the restrictions dropped,and the new concepts added, the result would be an upwardly compatible object modeling technique. Theevolutionary features of IDEF1X de