HIPO model

Hipo the diagram ( Hierarchy plus Input -Process - Output) is a graphical representation of functions performed in a single 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 designation " DV Process Engineering" was expanded into a comprehensive method of the description of operational business processes ( including connection to semantic data modeling ).

In a non- technical, but business-oriented form, the HIPO diagram ( "EVA - diagram " ), within the context of business process modeling business functions to generate data in the form " Data Required " (E), manufacturing processes (V) and " Generated data "(A ) at various hierarchical levels of refinement ( " summary graph "or" Detail diagram ").

To display the HIPO diagram in a functional diagram and a layer diagram, input process is divided. The presentation will be made ​​for each function by using the summary charts, more detailed diagrams are used to represent input and output links.

Advantages:

  • With HIPO to requirements of the departments free of computer specifications can be formulated
  • With HIPO structure can be very complex processes.
  • HIPO is suitable for batch processes batch but almost even better for workflows in video games, and technical programs ( such as device drivers) can be structured with HIPO.
  • The structuring with HIPO allows to structure programs to functional level and to predict the complexity of a program directly from the diagram.

Disadvantages of the HIPO diagram:

  • The presentation is mainly on stepwise refinement, quickly become confusing.
  • Data recoveries are in the HIPO diagram can not be displayed, HIPO program is not data flows represent flows
IPO Model Conceptual schema Function tree
392822
de