Made with

IDEF1X Standard

IDEF1x standard is developed for work with relational data bases. In particular IDEF1x standard is meant for constructing of conceptual schemes which represent the structure of data in the context of the concerned system, for example, a commercial organization. IDEF1x standard is a static method and is not intended for dynamic analysis, but it can be used for this, as an alternative to IDEF1 standard.
It is necessary to remember that IDEF1x standard is developed specially for construction of data base structure and that for work it requires an entering of definite data which is not necessary for work with other objects. For example, it requires an entering of dominant attributes to distinguish entities, which is not necessary in the object-oriented projection, so for such projection it is better to use the corresponding IDEF4 standard.

In general the terminology of IDEF1x standard coincides with the terminology of IDEF1 standard, however there are some differences. In IDEF1x the entity is a totality of objects of the real world similar by key properties. Each concrete object in this case is a realization of this entity. For instance an entity COMPUTER represents the totality of all computers of an organization. Each copy of the COMPUTER entity must contain definite information such as computer ID, the name in the network, characteristics, etc. This information is called attributes of an entity.

In IDEF1x entities are connected between each other with links, ties and associations. Ties are called in the verb form. Names of ties show entities relations. For example an ORGANIZATION COMPUTERS, AUTOMOBILE food stuffs, etc.

IDEF1X Standard *

The first entity in the above mentioned examples is connected with several entities of the second type therefore such tie is called ‘one to many’. At that, the first entity is called parental, and subsequent are daughters. (Child?) On the diagram ties are represented in the form of lines with the dot at the end and with the name specification. Also there are ties of the type ‘many to many’. They are used at the starting stage of the projection and represented in the form of lines with dots at both ends. As an example of such tie is the tie between the mass of PASSNGERS which by a number of BUSES. In future such ties must be necessarily elaborated in details.

Accordingly to IDEF1x standard entities are represented in the form of rectangles with definite fields. At the upper part of the rectangle the key information of the entity, also called the primary key, is located. This information is selected for unique entity identification, e.g. ID of a computer. At the lower part an area with non key attributes is located, e.g. the name of the computer in the network, the current worker, who works with the computer, works fulfilled on the given computer and computer characteristics. At the left bottom part an area with the entity name on the diagram is located, e.g. COMPUTER, WORKER or DEPARTMENT.

In the capacity of key attributes several attributes or even attribute groups can be chosen. Attributes, which can be key attributes, are called candidates of key attributes. Key attributes selection rules consist in the following:

  • Key attributes must uniquely identify an entity;
  • Key attributes mustn’t contain empty or NULL values;
  • Key attributes can’t change with time. At key attributes change the entity changes also;
  • Key attributes must be brief as far as possible for convenience of the further processing or indexation. For instance these can be alphanumeric symbols of the entity ID.

At choice of the primary key it is often used the so-called surrogate key, which represents an arbitrary number, existing only within the limits of the concrete data base and is unique for each

If entities on the IDEF1x diagram are connected one to each other, then the parent entity transfers key attributes to a child entity. Such attributes are called migratory or external keys. For example, COMPUTER which is on DEPARTMENT balance will have as an external key one of its key attributes the DEPARTMENT ID. Such child entities are called dependent as their identification depends on the key attributes of the parent entity. Dependent entities are divided into those entities which cannot exist without parent entity and those that can’t be identified without parent entity. For example, the INFORMATION on the COMPUTER cannot exist without it or without an external carrier, which are parent entities for it. In its turn, COMPUTER can exist without a DEPARTMENT, but accordingly to the accepted notations, cannot be identified not being the part of any department. Independent entities are those which are not dependent in identification on other entities. These are entities into which the system is divided in the first place and further structuring will happen within the limits of these entities. For example as a rule an organization is divided into DEPARTMENTS which are independent entities as they have its unique identifier not dependent on other entities. All other entities in their identification will depend on ID of the department they belong to.

Accordingly to IDEF1x standard, dependent entities are represented in the form of rounded rectangles, and non-dependent – in the form of usual rectangles.

The ties between entities can be identifying (transferring the external key to a child entity) and non-identifying (transferring data to the area of child entity data). Identifying ties are represented with a solid line, and non-identifying- with dotted line. As an example of identifying tie can be the tie between the DEPARTMENT and any of the resources, which is allotted between DEPARTMENTS and belong not to any of the DEPARTMENTS but to the organization as a whole.

The main advantage of the IDEF1X is the rigid and strict standardization of modeling. Such standardization allows to avoid misunderstandings during the analysis of the constructed model which is the significant advantage against other modeling methods without data bases.


Why People Select ConceptDraw MINDMAP  →

ConceptDraw MINDMAP an Alternative to MindJet MindManager - The power, economy, and versatility of ConceptDraw MINDMAP takes personnel and team productivity to another level. Discover today what this means to you.Why People Select ConceptDraw MINDMAP  *
Picture: Why People Select ConceptDraw MINDMAP
Related Solution:

ER Diagram Styles →

When creating ER diagrams, you can apply different color ER diagram styles and also notation styles. ConceptDraw DIAGRAM enhanced with Entity-Relationship Diagram (ERD) Solution gives the ability to draw visual and attractive ER Diagrams using the style icons from Crow’s Foot notation and Chen's notation professionally designed and offered by ERD Chen's Notation and ERD Crow’s Foot Notation libraries.ER Diagram Styles *
Picture: ER Diagram Styles
Related Solution:

Wireframing →

Website wireframe is a detailed view of design or its skeleton. It shows all the important elements of the final website, the main groups of contents, information structure, describes the user's interaction with interface and its estimated visualisation. ConceptDraw DIAGRAM extended with Website Wireframe solution from the Software Development area is the best wireframing software. Using the wireframe tools, libraries of vector objects, template and examples which offers a Website Wireframe solution, you will easily design the websites wireframes of any complexity.Wireframing *
Picture: Wireframing
Related Solution:

Chart Audit →

ConceptDraw DIAGRAM enhanced with Audit Flowcharts solution from the Finance and Accounting area of ConceptDraw Solution Park is a powerful diagramming and vector drawing software for designing professional looking Chart Audit of any complexity. Chart Audit is incredibly convenient for representing important information about audit process and audit planning process. It also helps auditors to define the problem areas and to elaborate the ways of their solving and effectiveness improvement.Chart Audit *
Picture: Chart Audit
Related Solution:

UML Sequence Diagram Example. SVG Vectored UML Diagrams Tools →

This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Sequence Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park. This sample shows the interactions of the customer with the system and is used at the registration on the sites.UML Sequence Diagram Example. SVG Vectored UML Diagrams Tools *
Picture: UML Sequence Diagram Example. SVG Vectored UML Diagrams Tools
Related Solution:

Data Flow Diagram Symbols. DFD Library →

Any information system receives data flows from external sources. In order to visualize them there is a list of data flow diagram symbols that describes how the system components cooperate. If you want to create a data flow diagram, ConceptDraw DIAGRAM Solution Park has DFD Library that contains both Yourdon and Gane-Sarson notations. This figure shows the content of vector libraries, delivered with ConceptDraw solution for data flow diagram (DFD). There are three libraries composed from about 50 vector objects used to make data flow diagrams. They include a complete set of objects utilized by Yourdon-Coad and Gane-Sarson notations - two primary notations that are apply for data flow diagramming. Also, one can discover additional "Data flow diagram (DFD)" library that provides a data flow diagram elements for designing level 1 and context-level data flow diagrams.Data Flow Diagram Symbols. DFD Library *
Picture: Data Flow Diagram Symbols. DFD Library
Related Solution:

Symboles Organigramme →

Les organigrammes sont parfaits pour représenter visuellement des processus operationnels. Par exemple, si vous avez besoin d'afficher le flux d'un processus d'ordre personnalisé par l'entremise de divers opérateurs au sein de votre organisation, vous pouvez utiliser un organigramme. Voir aussi d'autres symboles organigramme: Symboles ordinogramme standard, symboles du flux de travail, Vérification Les symboles du schéma fonctionnel, sOrganigramme comptables des symboles, Organigramme de vente des symboles, Symboles pour organigramme des RH, Carte des symboles de processus, Diagramme de processus opérationnels, Symboles utilisés dans le schéma IDEF0.Symboles Organigramme
Picture: Symboles Organigramme
Related Solution:

EPC - Business Processes in Terms of Work Flows →

The Event-driven Process Chain ( EPC ) Diagrams allows users to present business process models in terms of work flows. The EPC diagram can shows various vayes how to reach positive company performance.EPC - Business Processes in Terms of Work Flows *
Picture: EPC - Business Processes in Terms of Work Flows
Related Solution:

Venn Diagram Examples for Problem Solving →

In the Venn Diagrams solution, there are the pre-made examples that can be always used for making the unique, great looking diagrams, such as the 2-set Venn ones of any needed colour, the 3-set one, the 4-set ones and the 5-set ones. Having the already previously created samples of the Venn diagrams can help any ConceptDraw DIAGRAM user make it possible to make the needed drawing within only a few minutes by editing the existing ones.Venn Diagram Examples for Problem Solving — BQP Complexity
Picture: Venn Diagram Examples for Problem Solving
Related Solution: