IDEF1X

Uses your system voice; voice and rate in settings.

Snapshot

≈ 5 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

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. 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.

Evidence and sources

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. 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.

File:1 Entity Syntax.svg|Entity syntax File:2 Example of a Domain Hierarchy.svg|Domain hierarchy File:A3 11 Attribute Examples.jpg|Attribute example File:3 Attribute and Primary Key Syntax.svg|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.

Background

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.

File:4 Relationship Cardinality Syntax.jpg|Relationship cardinality syntax File:5 Identifying Relationship Syntax.jpg|Identifying relationship syntax File:8 Categorization Relationship Syntax.svg|Categorization relationship syntax File:9 Non-Specific Relationship Syntax.jpg|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.

File:A3 4 Entity Relationship Matrix.jpg|Entity relationship matrix File:A3 5 Entity Level Diagram.jpg|Entity level diagram File:A3 6 Phase Two (Entity Level) Diagram Example.jpg|Entity level diagram example File:A3 7 Reference Diagram (FEO).jpg|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.

File:A3 8 Example Reference Diagram.jpg|Example reference diagram File:A3 9 Non-Specific Relationship Refinement.jpg|Non-specific relationship refinement File:A3 10 Scope of a Function View.jpg|Scope of a function view File:A3 11 Attribute Examples.jpg|Attribute examples File:A3 16 No-Repeat Rule Refinement.jpg|No-repeat rule refinement File:A3 17 Rule Refinement.jpg|Rule refinement File:A3 19 Path Assertions.jpg|Path assertions File:A3 21 Example of Phase Three Function View Diagram.jpg|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 non-key attributes Validate and refine the data structure.

File:A3 23 Phase Four - Applying the No Repeat Rule.jpg|Applying the no repeat rule File:A3 24 Example of Phase Four Function.jpg|Example of phase four function

Text derived from https://en.wikipedia.org/w/index.php?oldid=1354175508 under CC BY-SA 4.0; modifications have been made.

Sources cited in this revision

6 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.