《IEEE-1320.2-1998.pdf》由会员分享，可在线阅读，更多相关《IEEE-1320.2-1998.pdf（316页珍藏版）》请在三一文库上搜索。
1、 The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright 1999 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 25 February 1999. Printed in the United States of America. Print: ISBN 0-7381-0
2、341-1 SH94663 PDF: ISBN 0-7381-1405-7SS94663 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 Std 1320.2-1998 IEEE Standard for Conceptual Modeling Language Syntax and Semantics for
3、IDEF1X 97 (IDEF object ) Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved 25 June 1998 IEEE-SA Standards Board Abstract: IDEF1X 97 consists of two conceptual modeling languages. The key-style language sup- ports data/information modeling and is downward compatib
4、le with the US governments 1993 stan- dard, FIPS PUB 184. The identity-style language is based on the object model with declarative rules and constraints. IDEF1X 97 identity style includes constructs for the distinct but related components of object abstraction: interface, requests, and realization;
5、 utilizes graphics to state the interface; and defines a declarative, directly executable Rule and Constraint Language for requests and realiza- tions. IDEF1X 97 conceptual modeling supports implementation by relational databases, extended relational databases, object databases, and object programmi
6、ng languages. IDEF1X 97 is formally defined in terms of first order logic. A procedure is given whereby any valid IDEF1X 97 model can be transformed into an equivalent theory in first order logic. That procedure is then applied to a meta model of IDEF1X 97 to define the valid set of IDEF1X 97 models
7、. Keywords: conceptual schema, data model, IDEF1X, IDEF1X 97 , identity style, information model, key style, object model 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
8、of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed 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 int
9、er- est in participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard 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 St
10、andard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is sub- jected to review at least every fi ve years for rev
11、ision or reaffi rmation. When a document is more than fi ve years old and has not been reaffi rmed, it is reasonable to conclude that its contents, although still of some value, do not wholly refl ect the present state of the art. Users are cautioned to check to determine that they have the latest e
12、dition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affi liation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpr
13、etations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specifi c applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards rep- re
14、sent a consensus of all concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to inte
15、rpretation requests except in those cases where the matter has previously received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA Authorization to photoc
16、opy portions of any individual standard for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center,
17、 Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (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 t
18、his standard may require 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. The IEEE shall not be responsible for identifying patents for which a license may be
19、required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Copyright 1999 IEEE. All rights reserved. iii Introduction This introduction is not a part of IEEE Std 1320.2-1998, IEEE Standard for Conceptual Modeling Lang
20、uage Syntax and Semantics for IDEF1X 97 (IDEF object ) . Background The need for semantic models to represent conceptual schemas was recognized by the US Air Force in the mid 1970s as a result of the Integrated Computer Aided Manufacturing (ICAM) Program. The objective of this program was to increas
21、e manufacturing productivity through the systematic application of computer technology. The ICAM program identifi ed 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 of techniques k
22、nown as the ICAM Defi nition (IDEF) methods, which included the following: a)IDEF0, a technique used to produce a “function model,” which is a structured representation of the activities or processes within the environment or system. b)IDEF1, a technique used to produce an “information model,” which
23、 represents the structure and semantics 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
24、 extensively in various government and industry settings. IDEF2 is no longer used to any signifi cant 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. 1 The theoretical roots for this approa
25、ch stemmed from the 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 revi
26、ew and infl uence by Mr. 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 (I 2 S 2 ) project under the ICAM program. The objective of this project was to provide the enabling technology to in
27、tegrate a network of het- erogeneous computer hardware and software both logically and physically. As a result of this project and industry experience, the need for an enhanced technique for information modeling was recognized. Application within industry had led to the development in 1982 of a Logi
28、cal Database Design Technique (LDDT) by R. G. Brown of the Database Design Group. The technique was also based on the relational model 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
29、provided multiple levels of models and a set of graphics for representing the conceptual view of information within an enterprise. It had a high degree of overlap with IDEF1 features, included additional semantic and graphical constructs, and addressed informa- tion modeling enhancement requirements
30、 that had been identifi ed under the I 2 S 2 program. Under the techni- cal leadership of Dr. M. E. S. Loomis of D. Appleton Company, a substantial subset of LDDT was combined with the methodology of IDEF1 and published by the ICAM program in 1985 B15. This technique was called IDEF1 Extended or, si
31、mply, IDEF1X. In December 1993, the US government released a Federal Information Processing Standard (FIPS) for IDEF1X. FIPS PUB 184 B13 was based on the ICAM program description of IDEF1X and additional fea- tures originally included in LDDT. The FIPS clarifi ed and corrected points in the ICAM pub
32、lication, sepa- 1 The numbers in brackets correspond to those of the bibliography items listed in Annex A. iv Copyright 1999 IEEE. All rights reserved. rated language syntax and semantics defi nition from practice and use issues, and provided a formal fi rst- order language defi nition of IDEF1X. IE
33、EE Std 1320.2-1998 continues the evolution of the IDEF1X language. It is driven by two needs. First, development of a national standard for the language makes the defi nition more accessible to organizations that do not follow US government standards and allows consideration and inclusion of feature
34、s needed out- side the US federal 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 concepts earlier than others. To be valuable to the widest set of users, this standa
35、rd needs to support a range of prac- 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 ope
36、rations performed on that data. The emerging object modeling approaches seek to treat all activities as performed by collaborating objects that encompass both the data and the operations that can be performed against that data. There is increasing interest in these approaches in both the government
37、and private sectors. Original work done 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 of object modeling B5. Th
38、e DBDG work analyzed the 1993 defi nition of IDEF1X and compared to it to the emerging consensus object 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, a
39、nd The object model contains signifi cant 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. The evolutionary features of IDEF1X descr
40、ibed in this standard draw heavily from the DBDG work done for NIST. Base documents The following documents served as base documents for the parts of IEEE Std 1320.2-1998 indicated: a) From IDEF1X to IDEF object , 1995, by Robert G. Brown, The Database Design Group, Newport Beach, CA, is the base do
41、cument for the Class and Responsibility clauses. Partial fi nancial support was provided by the National Institute of Standards and Technology (NIST) B5. b) IDEF1X 97 Rule and Constraint Language (RCL), 1997, by Robert G. Brown, The Database Design Group, Newport Beach, CA, is the base document for
42、the RCL clause. Partial fi nancial support was provided by the Defense Information Systems Agency (DISA) B6. c) IDEF1X 97 Formalization, 1998, by Valdis Berzins, Naval Postgraduate School, Monterey, CA, and Robert G. Brown, The Database Design Group, Newport Beach, CA, is the base document for the F
43、ormalization clause. Partial fi nancial support was provided by DISA and the Defense Modeling and Simulations Offi ce (DMSO) B7. The IDEF1X approach A principal objective of IDEF1X is to support integration. The “IDEF1X approach” to integration focuses on the capture, management, and use of a single
44、 semantic defi nition of the data resource referred to as a concep- tual schema . The conceptual schema provides a single integrated defi nition of the concepts relevant to an enterprise, unbiased toward any particular application. The primary objective of this conceptual schema is to Copyright 1999
45、 IEEE. All rights reserved. v provide a consistent defi nition of the meanings and interrelationship of concepts. This defi nition can then be used to integrate, share, and manage the integrity of the concepts. A conceptual schema must have three important characteristics: It must be consistent with
46、 the infrastructure of the business and be true across all application areas. It must be extendible, such that, new concepts can be defi ned without disruption to previously defi ned concepts. It must be transformable to both the required user views and to a variety of implementation environ- ments.
47、 IDEF1X is the semantic modeling technique described by IEEE Std 1320.2-1998. The IDEF1X technique was developed to meet the following requirements: Support the development of conceptual schemas. Be a coherent language. Be teachable. Be well-tested and proven. Be automatable. Organization of this do
48、cument This document begins with an explanation of the scope and purpose of this version of the IDEF1X standard. Clause 1 also describes the evolution of the IDEF1X standard. It provides a context for understanding the approach and constructs presented in the rest of this standard. Clause 2 identifi
49、 es additional references that must be on hand and available to the reader of this standard for its implementation. Other documentation and related references that might be of interest to the reader or that were used in preparing this standard are included in the bibliography (see Annex A). This document uses words in accordance with their defi nitions in the Merriam-Websters Collegiate Dictio- nary B26. A defi nitions clause (see Clause 3) is provided for the convenience of those not already familiar with the terminology in question. It also contains a