Business process modelling using IDEF0 and IDEF3 diagrams

Originally developed and research funded by the US Air Force, Integration Definition, or IDEF, refers to a family of modelling languages that are used in the fields of system and software engineering. The key aim of IDEF was to devise a method for modelling data subsystems in a generic fashion; a way of sharing information and defining business processes between associated agencies and suppliers. The first language of this form, IDEF1, was initially concerned with data storage systems, and the ability to represent data regardless of how it is physically stored and used. Other IDEF languages were soon developed - 0, 1X, 2, 3 and 4 are considered developed in full (a further 10 exist no more than beyond initial definition), and focus on applying the same methodology to all aspects of business process modelling (BPM), such as business operations, functional modelling, and process flow descriptions.

Since the late 1960's, Douglas T. Ross had been developing a systems engineering and software engineering methodology called the Structured Analysis and Design Technique (SADT), with its intention being to describe a system as a hierarchy of functions. With backing from the US Air Force, this would eventually be formalised as IDEF0, a function modelling language capable of analyzing and communicating the functional perspective of system.

The methodology identifies the prime function, and displays it on the 'Top Level Context Diagram' using a standardized set of symbols. From this diagram, diagrams for lower level processes can be produced. The language is now established enough to be used by a wide variety of businesses and organisations to show dataflow and business process using precise and strictly defined diagrams and graphical notations.

Fig. 1. IDEF0 Diagram Example


According to IDEF.com, these are the communicative concepts to be followed when creating an IDEF0 diagram:

• Diagrams based on simple box and arrow graphics.
• English text labels to describe boxes and arrows and glossary and text to define the precise meanings of diagram elements.
• The gradual exposition of detail featuring a hierarchical structure, with the major functions at the top and with successive levels of sub functions revealing well-bounded detail breakout.
• A "node chart" that provides a quick index for locating details within the hierarchic structure of diagrams.
• The limitation of detail to no more than six sub functions on each successive function.

Acting as a complement to IDEF0, the IDEF3 process description method records specific knowledge of behavioural aspects of a system or process. There are two modes in which it can do so, as described by Wikipedia:

• Process Flow Descriptions, to capture the relationships between actions within the context of a specific scenario.
• Object State Transition, to capture the description of the allowable states and conditions.

Whereas IDEF0 describes an idealized model of a system or process, an IDEF3 diagram provides a description of actual process flow within an organization or business, or the changes that occur to an object within that system. This method of knowledge capture is recorded in two different perspectives - users are able to create both process schematics and object schematics using the IDEF3 schematic symbols.

Fig. 2. IDEF3 Diagram Example

ConceptDraw has created a solution that collects all symbols necessary to create professional IDEF0 and IDEF3 diagrams, as well as templates and step-by-step lessons that help create your own process diagram from the ground up. The IDEF Business Process Diagrams solution for ConceptDraw PRO contains extensive libraries of vector stencils that allow users to create professional looking diagrams of any complexity. The power of ConceptDraw PRO means that recording a business process is a quick and painless task - smart connectors allow you to map your diagram on the screen almost as quickly as it comes to mind.

IDEF methodology is suitable for almost any form of business, and for anyone who needs to record enterprise architecture in a process driven manner. The IDEF Business Process Diagram solution and ConceptDraw PRO cater for these needs, giving both beginner and experienced users the tools they need to create effective business process diagrams.

Types of Organizational Structures

It is important for any organization or business to have a clear structure, that recognises and defines employees roles and responsibilities, and ultimately provides the framework for accomplishing the goals and aims of the company. There are a number of factors which decide how formal the structure needs to be, how complex, and which template it should follow — factors such as size and location of the company, how much management is needed, and the size and divisions of the workforce.

Organization structure types

The three main types of organizational structure are as follows: hierarchical, flat, and matrix. A smaller company, or one with few levels of middle management, might have a more organic structure — there is a shared knowledge base and centralized decision making; all parts of the workforce have common interaction with each other. But in a larger company made up of various divisions and teams, who may have only brief interactions and essentially work independently from each other, it is crucial to have a structure in place that clearly defines the decision making and supervisory process.

 

 

Hierarchical organization structure

Perhaps the most common form of organizational structure is hierarchical. This structure can be represented as a pyramid, with a single entity in authority at the top, with subsequent levels of power beneath them. Each member of the pyramid reports only to their direct subordinates or superiors, limiting the amount of communication overhead, which can be seen both as an asset or a limitation. It is easy to see where a hierarchical structure would be an effective solution; companies that have offices based in disparate locations, a business that focuses on diversified markets, any organization with need for multiple levels of middle management.

 

 

Flat organization structure

A flat organizational structure differs from a hierarchical one by almost entirely dispensing with middle management; rather than a pyramid, there is a 'flat' layer between staff and executives. In real terms, this means that almost all staff are involved in the decision making process and produce reports centrally — it can be viewed as a typically democratic structure.

 

 

Matrix organization structure

A third form of organizational structure can take the form of a matrix. This structure is commonly found in businesses that have more than one line of reportage. For instance, a company might contain an engineering department with engineering managers who workers report to. However, these workers might also have to liaise with different product or project managers depending on current tasks. Some form of matrix organization is found in most large-scale modern businesses.