Made with
ConceptDraw
DIAGRAM 18

IDEF0 standard with ConceptDraw DIAGRAM

The activity of any organization is more or less branchy network of processes. The description of these processes is a hard technical task which requires definite methodology and standards.

For the first time this problem arose in the seventies of the past century during the development of complicated projects requested by the Air Forces of the USA. ICAM system (Integrated Computer-Aided Manufacturing) was developed and later on its basis there was developed the standard of structural description of IDEF0 processes. In 1993 the government of the USA accepted this standard as a federal standard.

In 2000 the new version of ISO 9000:2000 standards was accepted by International Organization of Standardization. The main idea of this standard is a representation of organization activity as a network of processes hence the management of organization is the management of this network of processes. It is for description of these networks the IDEF0 standard is used.

According to the IDEF0 standard any process can be described in the form of a block (Activity Box) which has inputs and outputs. The process consists in transformation of inputs into outputs under the influence of the management and in the presence of necessary resources. Outputs of the given process later on can be either inputs for the next process or resources, or management means.

IDEF0 diagram

Each side of the block has its meaning:

  • Top side - Control;
  • Left side - Input;
  • Right side – Output;
  • Bottom side – Mechanism.

Besides, each block on the diagram has its unique identification number. For instance, the optimization process of the initial code of the program product can be represented in the form of the following block in which already existing quick-and-dirty code is the input, technical task on modernization is the element of the process management, programmer and hardware are the modernization mechanism and at the output optimized code will result.

IDEF0 diagram

On the diagram an interaction between processes is presented by way of arrows, which connect outputs of one processes with inputs of others. Actually the diagram consists of only 2 elements: blocks-processes and arrows which connect them.

Depending on their position on the diagram arrows are classified into input and output arrows, arrows of mechanisms (resources) and management arrows. Besides, arrows can be distinguished by any other criteria. By prior agreement, for more pictorial presentation of consecution of processes, arrows can be marked out with color or with other line types (E.g. solid or dotted, thin or thick.) Various types of lines are used not only for obviousness like at presentations, for example. Also, using different arrow types it is possible to process the diagram of processes by means of computer programs and to get reports, which characterize the definite type of industrial process.

At composing the diagram of industrial processes the principal of decomposition is used, i.e. the complicated process is divided into small parts. The degree of the detailed elaboration is defined by the diagram developer. For instance, code optimizing process can be divided into constituents such as the optimization itself, results testing, bugs fixing, second testing and documenting of the new optimized code.

According to IDEF0 standard the process of diagram composing starts from presentation of the whole system as one block with a unique number A0. Besides the purpose of the diagram with the viewpoint in the form of the brief description are denoted. The definition of the diagram purpose allows choosing of processes which should be denoted and described on the given diagram, and the viewpoint defines the degree of the necessary detailed elaboration of these processes.

The diagram on which not detailed initial processes are represented is called a Parent diagram. The diagram of the detailed process from the Parent diagram is called a Child diagram. Correspondingly, the block which is worked out in detail in the Child diagram is the Parent Box, and all blocks which describe it in the Child diagram are Child Boxes.

Blocks numbers on the child diagrams begin with the number of the parent box. For example, if the parent box has number A15 then child boxes will have numbers A151, A152 and so on.

Accordingly to IDEF0 standard for description of notations and expressions used in the diagram, a glossary is used. For example, the notation of the computer Mac1 which is used as a mechanism may contain the description of computer parameters.

IDEF0 standard with ConceptDraw DIAGRAM *

Example 1. IDEF0 standard diagram example (Mac OS X and Windows)

This IDEF0 diagram shows a detailed description of an application-development process. The steps of this process are represented by blocks which are visually arranged according to their logical levels.

All source documents are vector graphic documents. They are available for reviewing, modifying, or converting to a variety of formats (PDF file, MS PowerPoint, MS Visio, and many other graphic formats).






TEN RELATED HOW TO's:
ConceptDraw DIAGRAM is a flowchart design software. There are large collections of professional flowchart symbols for process flow diagrams, standard flowchart symbols and colored basic flowchart symbols. Built-in examples and video lessons allow users to get started immediately and do drawing of virtually any type of flowchart or process flow diagramsFlow Chart Creator *
Picture: Flow Chart Creator
Related Solution:
Make diagrams, charts, workflows, flowcharts, org charts, project charts easily with ConceptDraw software.Best Program to Make Diagrams *
Picture: Best Program to Make Diagrams
Related Solution:
Use the libraries from the Block Diagrams solution to draw block diagrams for your business documents, presentations and websites in a few minutes.Block Diagram
Picture: Block Diagram
Related Solution:
There are many ways to track the system in a critical situation. To model a system behavior, uml notation is widely used. Usually, an UML diagram consists of elements such as actor and a case. This diagram represents the structure of UML notations. Unified Modeling Language (UML) is used in software engineering to depict graphically the software modeling process. UM Language uses graphic notations for developing models of object-oriented systems. These notations displays requirements, sub-systems, logical and physical elements, etc. We created this diagram using ConceptDraw DIAGRAM reinforced with Rapid UML solution. It can be helpful for students on software engineering, when learning UML.UML Notation *
Picture: UML Notation
Related Solution:
ConceptDraw DIAGRAM is a powerful diagramming and vector drawing software. Extended with Chemical and Process Engineering Solution from the Industrial Engineering Area of ConceptDraw Solution Park, it became the best Chemical Engineering software.Chemical Engineering *
Picture: Chemical Engineering
Related Solution:
Professional diagramming software for mac helps you create Cause and Effect diagram known as Fishbone diagram or Ishikawa diagram from ConceptDraw Business Solution. You will be offered to use templates, samples or draw your diagram using ConceptDraw Arrows10 TechnologyDraw Diagram on Mac *
Picture: Draw Diagram on Mac
Create your own flow charts of settlement processes using the ConceptDraw DIAGRAM diagramming and vector drawing software extended with the Cross-Functional Flowcharts solution from the Business Processes area of ConceptDraw Solution Park. Download easy flowchart software to create settlement process flowcharts show steps of monthly settlement with your business quickly and easily.Settlement Process Flowchart. Flowchart Examples *
Picture: Settlement Process Flowchart. Flowchart Examples
Related Solution:
ConceptDraw DIAGRAM is a flowchart creating software. This software includes over 20 vector stencils in libraries. These objects allow you to create well-designed flowcharts. Put an initial object from library to a page and use RapidDraw technology clicking on direction arrows to add new objects to the flowchart. This way you can make flowchart quickly.How To Create a Flow Chart in ConceptDraw *
Picture: How To Create a Flow Chart in ConceptDraw
Related Solution:
If you ever wanted to try any diagramming tools except of Visio, but were afraid to lose existing documents, there’s good news for you. One of the most striking features of ConceptDraw DIAGRAM is it’s perfect compatibility with MS Visio, which guarantees that you won’t depend on operating system anymore, because another ConceptDraw DIAGRAM feature is that it’s cross-platform tool. Don’t waste your time looking for other options, you’ve found the solution already! Business professionals often utilize the MS Visio as a common tool for making various issues on business visualization. MS Visio is a strong software with good capacity to maintain complex business solutions. But there is no MS Visio for Apple OS X. This is a large invocation, and one would be pleased to recognize that ConceptDraw DIAGRAM is the ideal alternative to MS Visio. Primarily, because this software works natively on both Windows and Apple OS X platforms. if you have migrated from Windows to Mac, or need to communicate in a cross-platform conditions, you’ll search for MS Visio replacer. ConceptDraw DIAGRAM is the exclusive professional business diagramming application that runs on both Windows and Apple OS X. The opportunity exchange files between PC and Mac, as well as between ConceptDraw DIAGRAM and Visio is the significant advantage that permits you to display and to collaborate business information in effortless and cost-effective way.ConceptDraw DIAGRAM Compatibility with MS Visio *
Picture: ConceptDraw DIAGRAM Compatibility with MS Visio
While developing software, it is very important to have a visual model, because it helps to represent the logic and the architecture of an application. Experienced engineers use UML diagrams to denote relationships between classes and their instances. UML is a general language for a set of diagrams like deployment diagrams, object diagrams or use case diagrams. This diagram represents UML class diagram used for a software system development using an object-oriented method. Class diagrams are categorized as static structure diagrams that depict the physical structure of a system. Class diagram divides a software system's structure into "classes". Classes are defined by the methods and variables of objects. UML Class diagram is used to depict relationships and source code dependencies between objects.UML Diagram *
Picture: UML Diagram
Related Solution:
ConceptDraw
DIAGRAM 18