IDEF1X

From Wikipedia, the free encyclopedia
Not to be confused with Idefix.
Example of an IDEF1X diagram.

Integration DEFinition for information modeling (IDEF1X) is a data modeling language for the development of semantic data models. IDEF1X is used to produce a graphical information model which represents the structure and semantics of information within an environment or system.[1]

IDEF1X permits the construction of semantic data models which may serve to support the management of data as a resource, the integration of information systems, and the building of computer databases. This standard is part of the IDEF family of modeling languages in the field of software engineering.

Overview[]

A data modeling technique is used to model data in a standard, consistent and predictable manner in order to manage it as a resource. It can be used in projects requiring a standard means of defining and analyzing the data resources within an organization. Such projects include the incorporation of a data modeling technique into a methodology, managing data as a resource, integrating information systems, or designing computer databases. The primary objectives of the IDEF1X standard are to provide:[1]

  • Means for completely understanding and analyzing an organization's data resources
  • Common means of representing and communicating the complexity of data
  • A technique for presenting an overall view of the data required to run an enterprise
  • Means for defining an application-independent view of data which can be validated by users and transformed into a physical database design
  • A technique for deriving an integrated data definition from existing data resources.

A principal objective of IDEF1X is to support integration. The approach to integration focuses on the capture, management, and use of a single semantic definition of the data resource referred to as a “conceptual schema.” The “conceptual schema” provides a single integrated definition of the data within an enterprise which is not biased toward any single application of data and is independent of how the data is physically stored or accessed. The primary objective of this conceptual schema is to provide a consistent definition of the meanings of and interrelationships between data that can be used to integrate, share, and manage the integrity of data. A conceptual schema must have three important characteristics:[1]

  • Consistent with the infrastructure of the business and true across all application areas
  • Extendible, such that new data can be defined without altering previously defined data
  • Transformable to both the required user views and to a variety of data storage and access structures.

History[]

The need for semantic data models was first recognized by the U.S. Air Force in the mid-1970s as a result of the Integrated Computer Aided Manufacturing (ICAM) Program. The objective of this program was to increase manufacturing productivity through the systematic application of computer technology. The ICAM Program identified a need for better analysis and communication techniques for people involved in improving manufacturing productivity. As a result, the ICAM Program developed a series of techniques known as the IDEF (ICAM Definition) Methods which included the following:[1]

  • IDEF0 used to produce a “function model” which is a structured representation of the activities or processes within the environment or system
  • IDEF1 used to produce an “information model” which represents the structure and semantics of information within the environment or system
  • IDEF2 used to produce a “dynamics model”.

The initial approach to IDEF information modeling (IDEF1) was published by the ICAM program in 1981, based on current research and industry needs. The theoretical roots for this approach stemmed from the early work of Edgar F. Codd on Relational model theory and Peter 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 Aircraft and Mr D. S. Coleman of D. Appleton Company (DACOM), with critical review and influence by Charles Bachman, Peter Chen, Dr M. A. Melkanoff, and Dr G.M. Nijssen.[1]

In 1983, the U.S. Air Force initiated the Integrated Information Support System (I2S2) project under the ICAM program. The objective of this project was to provide the enabling technology to logically and physically integrate a network of heterogeneous computer hardware and software. As a result of this project, and industry experience, the need for an enhanced technique for information modeling was recognized.[1]

From the point of view of the contract administrators of the Air Force IDEF program, IDEF1X was a result of the ICAM IISS-6201 project and was further extended by the IISS-6202 project. To satisfy the data modeling enhancement requirements that were identified in the IISS-6202 project, a sub-contractor, DACOM, obtained a license to the Logical Database Design Technique (LDDT) and its supporting software (ADAM). From the point of view of the technical content of the modeling technique, IDEF1X is a renaming of LDDT.

On September 2, 2008, the associated NIST standard, FIPS 184, has been withdrawn (decision on Federal Register vol. 73 / page 51276 [1]).

Since September 2012, IDEF1X is part of the international standard ISO/IEC/IEEE 31320-2:2012.[2] The standard describes the syntax and semantics of IDEF1X97, which consists of two conceptual modeling languages: a “key-style” language downward compatible with FIPS 184, which supports relational and extended relational databases, and a newer “identity-style” language suitable for object databases and object-oriented modeling.

Logical database design technique[]

The logical database design technique (LDDT) had been developed in 1982 by Robert G. Brown of The Database Design Group entirely outside the IDEF program and with no knowledge of IDEF1. Nevertheless, the central goal of IDEF1 and LDDT was the same: to produce a database-neutral model of the persistent information needed by an enterprise by modeling the real-world entities involved. LDDT combined elements of the relational data model, the E-R model, and data generalization in a way specifically intended to support data modeling and the transformation of the data models into database designs.

LDDT included an environmental (namespace) hierarchy, multiple levels of model, the modeling of generalization/specialization, and the explicit representation of relationships by primary and foreign keys, supported by a well defined role naming facility. The primary keys and unambiguously role-named foreign keys expressed sometimes subtle uniqueness and referential integrity constraints that needed to be known and honored by whatever type of database was ultimately designed. Whether the database design used the integrity constraint based keys of the LDDT model as database access keys or indexes was an entirely separate decision. The precision and completeness of the LDDT models was an important factor in enabling the relatively smooth transformation of the models into database designs. Early LDDT models were transformed into database designs for IBM's hierarchical database, IMS. Later models were transformed into database designs for Cullinet's network database, IDMS, and many varieties of relational database.

The LDDT software, ADAM, supported view (model) entry, view merging, selective (subset) viewing, namespace inheritance, normalization, a quality assurance analysis of views, entity relationship graph and report generation, transformation to a relational database expressed as SQL data declaration statements, and referential integrity checking SQL. Logical models were serialized with a structural modeling language.

The graphic syntax of LDDT differed from that of IDEF1 and, more importantly, LDDT contained many interrelated modeling concepts not present in IDEF1. Therefore, instead of extending IDEF1, Mary E. Loomis of DACOM wrote a concise summary of the syntax and semantics of a substantial subset of LDDT, using terminology compatible with IDEF1 wherever possible. DACOM labeled the result IDEF1X and supplied it to the ICAM program, which published it in 1985. (IEEE 1998, p. iii) (Bruce 1992, p. xii)[1] DACOM also converted the ADAM software to C and sold it under the name Leverage.

IDEF1X building blocks[]

  • Entity syntax

  • Domain hierarchy

  • Attribute example

  • Primary key syntax

Entities
The representation of a class of real or abstract things (people, objects, places, events, ideas, combination of things, etc.) that are recognized as instances of the same class because they share the same characteristics and can participate in the same relationships.
Domains
A named set of data values (fixed, or possibly infinite in number) all of the same data type, upon which the actual value for an attribute instance is drawn. Every attribute must be defined on exactly one underlying domain. Multiple attributes may be based on the same underlying domain.
Attributes
A property or characteristic that is common to some or all of the instances of an entity. An attribute represents the use of a domain in the context of an entity.
Keys
An attribute, or combination of attributes, of an entity whose values uniquely identify each entity instance. Each such set constitutes a candidate key.
Primary keys
The candidate key selected as the unique identifier of an entity.
Foreign keys
An attribute, or combination of attributes of a child or category entity instance whose values match those in the primary key of a related parent or generic entity instance. A foreign key can be viewed as the result of the "migration" of the primary key of the parent or generic entity through a specific connection or categorization relationship. An attribute or combination of attributes in the foreign key can be assigned a role name reflecting its role in the child or category entity.

  • Relationship cardinality syntax

  • Identifying relationship syntax

  • Categorization relationship syntax

  • Non-specific relationship syntax

Relationships
An association between the instances of two entities or between instances of the same entity.
Connection relationships
A relationship having no semantics in addition to association. See constraint, cardinality.
Categorization relationships
A relationship in which instances of both entities represent the same real or abstract thing. One entity (generic entity) represents the complete set of things, the other (category entity) represents a sub-type or sub-classification of those things. The category entity may have one or more characteristics, or a relationship with instances of another entity, not shared by all generic entity instances. Each instance of the category entity is simultaneously an instance of the generic entity.
Non-specific relationships
A relationship in which an instance of either entity can be related to any number of instances of the other.
View levels
Three levels of view are defined in IDEF1X: entity relationship (ER), key-based (KB), and fully attributed (FA). They differ in level of abstraction. The ER level is the most abstract. It models the most fundamental elements of the subject area - the entities and their relationships. It is usually broader in scope than the other levels. The KB level adds keys and the FA level adds all the attributes.

IDEF1X topics[]

The three schema approach[]

The three schema approach .[3]

The three-schema approach in software engineering is an approach to building information systems and systems information management, that promotes the conceptual model as the key to achieving data integration.[4]

A schema is a model, usually depicted by a diagram and sometimes accompanied by a language description. The three schemas used in this approach are:[5]

  • External schema for user views
  • Conceptual schema integrates external schemata
  • Internal schema that defines physical storage structures.

At the center, the conceptual schema defines the ontology of the concepts as the users think of them and talk about them. The physical schema describes the internal formats of the data stored in the database, and the external schema defines the view of the data presented to the application programs.[6] The framework attempted to permit multiple data models to be used for external schemata.[7]

Modeling guidelines[]

Synthesizing an entity in phase one – entity definition

The modeling process can be divided into five stages of model developing.

Phase zero – project Initiation
The objectives of the project initiation phase include:
  • Project definition – a general statement of what has to be done, why, and how it will get done
  • Source material – a plan for the acquisition of source material, including indexing and filing
  • Author conventions – a fundamental declaration of the conventions (optional methods) by which the author chooses to make and manage the model.
Phase one – entity definition
The objective of the entity definition phase is to identify and define the entities that fall within the problem domain being modeled.
Phase two – relationship definition
The objective of the relationship definition phase is to identify and define the basic relationships between entities. At this stage of modeling, some relationships may be non-specific and will require additional refinement in subsequent phases. The primary outputs from phase two are:
  • Relationship matrix
  • Relationship definitions
  • Entity-level diagrams.

  • Entity relationship matrix

  • Entity level diagram

  • Entity level diagram example

  • Reference diagram

Phase three - key definitions
The objectives of the key definitions phase are to:
  • Refine the non-specific relationships from phase two
  • Define key attributes for each entity
  • Migrate primary keys to establish foreign keys
  • Validate relationships and keys.

  • Example reference diagram

  • Non-specific relationship refinement

  • Scope of a function view

  • Attribute examples

  • No-repeat rule refinement

  • Rule refinement

  • Path assertions

  • Example of phase three function view diagram

Phase four - attribute definition
The objectives of the attribute definition phase are to:
  • Develop an attribute pool
  • Establish attribute ownership
  • Define monkey attributes
  • Validate and refine the data structure.

  • Applying the no repeat rule

  • Example of phase four function

IDEF1X meta model[]

Meta model of IDEF1X.

A meta model is a model of the constructs of a modeling system. Like any model, it is used to represent and reason about the subject of the model - in this case IDEF1X. The meta model is used to reason about IDEF1X, i.e., what the constructs of IDEF1X are and how they relate to one another. The model shown is an IDEF1X model of IDEF1X. Such meta models can be used for various purposes, such as repository design, tool design, or in order to specify the set of valid IDEF1X models. Depending on the purpose, somewhat different models result. There is no “one right model.” For example, a model for a tool that supports building models incrementally must allow incomplete or even inconsistent models. The meta model for formalization, however, emphasizes alignment with the concepts of the formalization and hence incomplete or inconsistent models are not allowed.

Meta models have two important limitations. First, they specify syntax but not semantics. Second, a meta model must be supplemented with constraints in natural or formal language. The formal theory of IDEF1X provides both the semantics and a means to precisely express the necessary constraints.

A meta model for IDEF1X is given in the adjacent figure. The name of the view is mm. The domain hierarchy and constraints are also given. The constraints are expressed as sentences in the formal theory of the meta model. The meta model informally defines the set of valid IDEF1X models in the usual way, as the sample instance tables that correspond to a valid IDEF1X model. The meta model also formally defines the set of valid IDEF1X models in the following way. The meta model, as an IDEF1X model, has a corresponding formal theory. The semantics of the theory are defined in the standard way. That is, an interpretation of a theory consists of a domain of individuals and a set of assignments:

  • To each constant in the theory, an individual in the domain is assigned
  • To each n-ary function symbol in the theory, an n-ary function over the domain is assigned
  • To each n-ary predicate symbol in the theory, an n-ary relation over the domain is assigned.

In the intended interpretation, the domain of individuals consists of views, such as production; entities, such as part and vendor; domains, such as qty_on_hand; connection relationships; category clusters; and so on. If every axiom in the theory is true in the interpretation, then the interpretation is called a model for the theory. Every model for the IDEF1X theory corresponding to the IDEF1X meta model and its constraints is a valid IDEF1X model.

See also[]

References[]

Public Domain This article incorporates public domain material from the National Institute of Standards and Technology website https://www.nist.gov.

  1. ^ Jump up to: a b c d e f g FIPS Publication 184 Archived 2013-12-03 at the Wayback Machine released of IDEF1X by the Computer Systems Laboratory of the National Institute of Standards and Technology (NIST). 21 December 1993.
  2. ^ ISO/IEC/IEEE 31320-2:2012 Information technology — Modeling Languages — Part 2: Syntax and Semantics for IDEF1X97 (IDEFobject).
  3. ^ itl.nist.gov (1993) Integration Definition for Information Modeling (IDEFIX) Archived 2013-12-03 at the Wayback Machine. 21 Dec 1993.
  4. ^ STRAP SECTION 2 APPROACH. Retrieved 30 September 2008.
  5. ^ Mary E.S. Loomis (1987). The Database Book. p. 26.
  6. ^ John F. Sowa (2004). [ "The Challenge of Knowledge Soup"]. published in: Research Trends in Science, Technology and Mathematics Education. Edited by J. Ramadas & S. Chunawala, Homi Bhabha Centre, Mumbai, 2006.
  7. ^ Gad Ariav & James Clifford (1986). New Directions for Database Systems: Revised Versions of the Papers. New York University Graduate School of Business Administration. Center for Research on Information Systems, 1986.

Further reading[]

External links[]

Retrieved from ""