Made with
ConceptDraw
DIAGRAM 14

IDEF3 Standard

In contrast to IDEF0 standard, IDEF3 standard is more particularly specialized. This standard is intended for description and further analysis of technological processes of an enterprise. Using IDEF3 standard it is possible to examine and model scenarios of technological processes. Scenario is a description of consecution of properties changes of an object which takes part in the technological process, e.g. half-finished product which is under processing. Each scenario is documented correspondingly. For documenting of the scenario there are two types of documents: documents, which describe properties and consecution of the process execution (standards, methods and technologies description) and documents, which describe results of the process execution (reports and work statistics). IDEF3 standard allows to get information about process and attendant documentation and to analyze it for increasing of the process management effectiveness. Using IDEF3 standard you can collect and document information about processes key points, define the degree of influence on the course of processes execution and model scenarios without change of the production process itself.

There are two types of diagrams in IDEF3 standard. These diagrams describe the same technological process from different sides. First type of diagram is Process Flow Description Diagrams (PFDD). The second type - Object State Transition Network (OSTN) diagrams.

For instance if it is necessary to describe the process of stamping the detail from a billet, the PFDD diagram will contain a description of consecution of actions which are executed with the billet during the given process, and the OSTN diagram will contain the detail states on each process stage.

Rectangular blocks on the diagram are called functional units or Units of Behavior (UOB). Each UOB has the name in the verb form and a unique number and denotes an event within the limits of the process (a stage, an action or decision making). UOB are connected by arrows in consecution of the process execution. There are 3 different kinds of arrows: Precedence arrow - a solid line, which is drawn from left to right or top-down; Relational Link - a dotted line, used for description of relations between UOB; Object Flow - an arrow with two arrow-heads. Such arrow denotes that the object is used in two or more subruns. For example, when the object is created in one subrun and is used in another one.

The block marked with the cross on the diagram is called a Junction. Such blocks are used for indication of decision makings during the process. Accordingly to IDEF3 standard there are two types of Junctions: for confluence (Fan-in Junction) and branching (Fan-out Junction) of arrows. Simultaneous junction and branching is not allowed. Junctions can be of different types. The junction type is denoted on the diagram.

Indication Name Fan-in Junction Fan-out Junction
Asynchronous AND Asynchronous AND All preceding subruns must be completed All subsequent subruns must be started
Synchronous AND Synchronous AND All preceding subruns must be completed simultaneously All subsequent subruns must be started simultaneously
Asynchronous OR Asynchronous OR One or several preceding subruns must be completed One or several subsequent subruns must be started
Synchronous OR Synchronous OR One or several preceding subruns must be completed simultaneously One or several subsequent subruns must be started simultaneously
Synchronous OR XOR (Exclusive OR) Only one preceding process must be completed Only one subsequent process must be started

All junctions in PFDD are numerated, each number has prefix "J", e.g. J1, J2 and so on.

Each UOB can be represented in the form of sequence of blocks with the necessary degree of detailed elaboration. For example the block “Testing of a detail” can be represented in the form of sequence of blocks, which in their turn will form PFDD diagram. Such diagram will be called a Child diagram, and the initial diagram – a Parent diagram.

The OSTN diagram represents a list of object state and descriptions of influences which correspond to UOB blocks from the corresponding PFDD diagram. Object states are represented by circumferences and their changes – by directed lines, which are signed the same way as corresponding UOB blocks.

IDEF3 Standard *

TEN RELATED HOW TO's:

Swim Lanes →

Swim lanes are visual elements used in Business Process Maps, Process Flow Diagrams and Flowcharts. ConceptDraw DIAGRAM diagramming and vector drawing software extended with Business Process Mapping Solution from the Business Processes Area of ConceptDraw Solution Park is ideal for drawing Business Process Maps and Swim Lanes Flowcharts.Swim Lanes *
Picture: Swim Lanes
Related Solution:

Database Design →

ConceptDraw DIAGRAM extended with IDEF Business Process Diagrams solution from the Business Processes area of ConceptDraw Solution Park is an ideal software for effective database design and drawing IDEF diagrams visually representing all steps of database design process.Database Design *
Picture: Database Design
Related Solution:

Business Process Elements: Swimlanes →

ConceptDraw has 142 vector stencils in the 8 libraries that helps you to start using software for designing own Business Process Diagrams. Use Swimlanes library with 20 objects from BPMN.Business Process Elements: Swimlanes *
Picture: Business Process Elements: Swimlanes
Related Solution:

Data Flow Diagram (DFD) →

In software engineering, it is important to understand how the system would cooperate with external sources, like data sources. To give this information a visual representation, data flow diagrams (DFD) were used for years. The entire system is usually divided into smaller ones, and all of them process data flows in appropriate ways. The visualizing business processes which engages the data transfer, is commonly preformed using DFDs (data flow diagrams). DFD is used to show the data flow processing and transformation. This DFD represents the electronic system of a customer purchase. It was created using Gane/Sarson notation. Data flow diagrams helps you to sort through and clarify transferring process making it available for analysis, and representation. ConceptDraw DFD solution introduces the vector library, containing the full set of icons from DFD notations.Data Flow Diagram (DFD) *
Picture: Data Flow Diagram (DFD)
Related Solution:

Entity Relationship Diagram Software Engineering →

While designing a conceptual data model, you should use appropriate software. For instance, ConceptDraw DIAGRAM is a user-friendly ER diagram tool that has a lot of samples and templates to facilitate your work. A clear entity-relationship diagram helps to define the relations between system’s components. Software engineering is the section of a computer science engaged to design, realization, and support of complex software products. An ERD is a data modeling method that is widely applied in the software engineering practice. Commonly it is used for developing a structure of a a relational database. An entity relationship diagram is helpful for structuring and organizing databases that can be modeled using a relational structure. An entity relationship diagram is designed to depicts the interrelationships within the sets of entities which are accumulated in the database. Each entity represents a particular component of a data. Thus, ER diagrams depicts the logical structure of databases. ConceptDraw ER Diagrams solution provides software engineers with the professional tool for making entity-relationship diagrams.Entity Relationship Diagram Software Engineering *
Picture: Entity Relationship Diagram Software Engineering
Related Solution:

Diagrams Mean Nothing →

You are probably familiar with diagrams. But have you ever thought that they are useless? This article will explain you why.Diagrams Mean Nothing *
Picture: Diagrams Mean Nothing
Related Solution:

Entity Relationship Diagram Examples →

An abstract representation is usually the first thing you will need while developing a database. To understand the ways that databases are structured, you should look through entity-relationship diagram examples and see the notations features and attributes. With an entity-relationship model you can describe a database of any complexity. This Entity-relationship diagram is a tool for software developers. It enables every element of database to be managed, communicated and tested before release. This ERD was created using symbols advocated by Chen's notation. Because of a linguistic origin of the Chen’s notation, the boxes representing entities could be interpreted as nouns, and the relationships between them are in verb form, shown on a diagram as a diamond.Entity Relationship Diagram Examples
Picture: Entity Relationship Diagram Examples
Related Solution:
ConceptDraw
DIAGRAM 14