HIPO diagram

EVA principle when converting alternating current into direct current in a power supply unit

EVA principle in a business process (at a high hierarchical level)

The HIPO diagram ( hierarchy plus input-process-output ) is a graphic representation of functions that are carried out in a system . The diagram is based on the so-called EVA principle (input - processing - output).

HIPO was developed around 1970 as a design aid and documentation technology for software from IBM. Under the name "IT process engineering", it has been expanded into a comprehensive method of describing operational business processes (including a connection to semantic data modeling ).

In a non-technical, but rather business-oriented form, the HIPO diagram ("EVA diagram") describes operational functions for generating data in the form of "required data" (E), processing processes (V) and "generated" within the framework of business process modeling Data ”(A) on various hierarchical levels of refinement (“ overview diagram ”or“ detail diagram ”).

The HIPO diagram is divided into a function diagram and a level diagram with an input process . The representation is made for each function with the help of overview diagrams, several detailed diagrams are used to represent the input and output interrelations.

Advantages:

With HIPO, specifications of the specialist departments can be formulated free of IT-specifics
Even very complex processes can be structured with HIPO.
HIPO is suitable for batch processes batch but almost better for sequences in video games, and technical programs (such as device drivers) can be structured with HIPO.
Structuring with HIPO allows programs to be structured down to the functional level and the complexity of a program to be predicted directly from the diagram.

Disadvantages of the HIPO diagram:

The display quickly becomes confusing, especially when it is gradually refined.
Data returns cannot be represented in the HIPO diagram, HIPO represents program flows, not data flows

Web links

HIPO lecture, there are more examples

Individual evidence

^ IBM Corporation (1974). HIPO-A Design Aid and Documentation Technique , Publication Number GC20-1851, IBM Corporation, White Plains, NY, 1974.
↑ Jürgen Beetz, Hansgert Lambers: An application development methodology for AD / CYCLE. The methodology of the IT process engineering . Addison-Wesley, Bonn 1991, ISBN 3-89319-205-0 .

[1] IBM Corporation (1974). HIPO-A Design Aid and Documentation Technique , Publication Number GC20-1851, IBM Corporation, White Plains, NY, 1974.

[2] Jürgen Beetz, Hansgert Lambers: An application development methodology for AD / CYCLE. The methodology of the IT process engineering . Addison-Wesley, Bonn 1991, ISBN 3-89319-205-0 .