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.


Software Diagram Examples and Templates →

ConceptDraw DIAGRAM is a powerful tool for business and technical diagramming. Software Development area of ConceptDraw Solution Park provides 5 solutions: Data Flow Diagrams, Entity-Relationship Diagram (ERD), Graphic User Interface, IDEFO Diagrams, Rapid UML.Software Diagram Examples and Templates *
Picture: Software Diagram Examples and Templates
Related Solution:

Marketing Organization Chart →

You need design the Marketing Organization Chart and look for effective software? Now it's incredibly easy to do this in ConceptDraw DIAGRAM which was supplied with Marketing Diagrams Solution from the Marketing Area of ConceptDraw Solution Park.Marketing Organization Chart *
Picture: Marketing Organization Chart
Related Solution:

Solar System Symbols →

Astronomy solution provides the Stars and Planets library with wide variety of solar system symbols. You can find here vector objects of solar system, of stars and planets of the universe. To quickly draw any astronomy illustration: create new document and simply drag the needed solar system symbols from the Stars and Planets library, arrange them and add the text. You can also use the predesigned templates and samples from the ConceptDraw STORE as the base for your own sun solar system illustrations, astronomy and astrology drawings.Solar System Symbols *
Picture: Solar System Symbols
Related Solution:

Object-Oriented Development (OOD) Method →

This sample shows the Booch OOD diagram of the environment. The Booch method (developed by Grady Booch) is an object modeling language and methodology used in software engineering. This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park.Object-Oriented Development (OOD) Method *
Picture: Object-Oriented Development (OOD) Method
Related Solution:

Entity-Relationship Diagram →

Entity Relationship Diagram (ERD) is the world-known way to show the logical structure of databases in visual manner. The best software tool for drawing Entity-Relationship Diagram is ConceptDraw DIAGRAM vector graphics software with Entity-Relationship Diagram (ERD) solution from Software Development area which gives the ability to describe a database using the Entity-Relationship model. The vector graphic diagrams produced using this solution can be successfully used in whitepapers, presentations, datasheets, posters, or any technical materials.Entity-Relationship Diagram *
Picture: Entity-Relationship Diagram
Related Solution:

Business Process Reengineering Examples →

This sample shows the Business Process Reengineering Diagram. Reengineering is the process of the business processes optimizations. This sample can be used in business process management, quality management, project management and program management.Business Process Reengineering Examples *
Picture: Business Process Reengineering Examples
Related Solution:

Food Art →

Food courts are very popular places. You want to increase attendance, advertise and invite attention to your food court? Make interesting design and create pictorial and bright food art posters and signboards, and don't forget to decorate your menu with images of tasty treats! ConceptDraw DIAGRAM diagramming and vector software supplied with Food Court solution from the Food and Beverage area of ConceptDraw Solution Park offers powerful drawing tools for effective food art.Food Art *
Picture: Food Art
Related Solution: