Form driven Methodologies
HIPO is a forms-driven technique. Here standard documents are used to document the information. It consists of a hierarchy chart and an associated set of input/process/output charts. HIPO uses top-down decomposition. It describes the data input and output from processes and defines the data flow composition. The objectives are:
1.Provide a structure by which the functions of a system can be understood.
2.State the functions to be performed by the program rather than specifying the program statements to be used to perform the functions.
3.Provide a visual description of input to be used and output to be produced for each level of the diagram.
HIPO makes the transformation of input to output data visible.
HIPO uses easy to draw symbols. The procedure to construct the HIPO chart is as follows:
1.Begin at the highest level of abstraction.
2.Identify the processing steps that convert the input to the output.
3.Document each element using the HIPO diagram notation and a treelike structure.
4.Identify sub processes and their inputs and outputs. Continue decomposition until the processes cannot be decomposed further.
There are two tools used for drawing the HIPO diagrams:
->HIPO Worksheet ,GX20-1970
->HIPO template , GX20- 1971
The template contains the symbols for the HIPO diagrams. HIPO format consist of
Visual table of contents shows the structure of the diagram and the relationships of the functions in a hierarchical manner. It also has a legend to show how symbols are to be used.
Overview diagrams describe the major functions and reference the major details diagrams needed to expand the functions adequately. They provide the following
a) The input section that contains the data items used by the process steps.
b) The output section that contains the data items created by the process steps.
c) Process section that contains numbered steps that describe the functions to be performed. Arrows connect then to the output steps and input/output data items.
d) The extended description refers to non-HIPO documentation and code
Detail diagram contains an extended description section that amplifies the process steps and references the code associated with each process steps.
HIPO is a forms-driven technique. Here standard documents are used to document the information. It consists of a hierarchy chart and an associated set of input/process/output charts. HIPO uses top-down decomposition. It describes the data input and output from processes and defines the data flow composition. The objectives are:
1.Provide a structure by which the functions of a system can be understood.
2.State the functions to be performed by the program rather than specifying the program statements to be used to perform the functions.
3.Provide a visual description of input to be used and output to be produced for each level of the diagram.
HIPO makes the transformation of input to output data visible.
HIPO uses easy to draw symbols. The procedure to construct the HIPO chart is as follows:
1.Begin at the highest level of abstraction.
2.Identify the processing steps that convert the input to the output.
3.Document each element using the HIPO diagram notation and a treelike structure.
4.Identify sub processes and their inputs and outputs. Continue decomposition until the processes cannot be decomposed further.
There are two tools used for drawing the HIPO diagrams:
->HIPO Worksheet ,GX20-1970
->HIPO template , GX20- 1971
The template contains the symbols for the HIPO diagrams. HIPO format consist of
Visual table of contents shows the structure of the diagram and the relationships of the functions in a hierarchical manner. It also has a legend to show how symbols are to be used.
Overview diagrams describe the major functions and reference the major details diagrams needed to expand the functions adequately. They provide the following
a) The input section that contains the data items used by the process steps.
b) The output section that contains the data items created by the process steps.
c) Process section that contains numbered steps that describe the functions to be performed. Arrows connect then to the output steps and input/output data items.
d) The extended description refers to non-HIPO documentation and code
Detail diagram contains an extended description section that amplifies the process steps and references the code associated with each process steps.