HIPO for hierarchical input process output is a "popular 1970s systems analysis design aid and documentation technique" for representing the modules of a system as a hierarchy and for documenting each module.
It was used to develop requirements, construct the design, and support implementation of an expert system to demonstrate automated rendezvous. Verification was then conducted systematically because of the method of design and implementation.
The overall design of the system is documented using HIPO charts or structure charts. The structure chart is similar in appearance to an organizational chart, but has been modified to show additional detail. Structure charts can be used to display several types of information, but are used most commonly to diagram either data structures or code structures.
- IBM Corporation (1974).HIPO—A Design Aid and Documentation Technique, Publication Number GC20-1851, IBM Corporation, White Plains, NY, 1974.
- Katzan, Harry, Jr. (1976). Systems Design and Documentation: An introduction to the HIPO Method. Van Nostrand Reinhold. ISBN 0-442-24267-0.
- Sandia National Laboratories (1992). Sandia Software Guidelines Volume 5 Tools, Techniques,and Methodologies SANDIA REPORTS 85–2348qUC–32
- Mary Ann Goodwin and Charles C. Robertson (1986). EXPERT SYSTEM VERIFICATION CONCERNS IN AN OPERATIONS ENVIRONMENT. NASA paper N88-17234.
- HIPO (hierarchy plus input-process-output) in: The Information System Consultant's Handbook: Systems Analysis and Design by William S. Davis, David C. Yen, 1998.
|This systems-related article is a stub. You can help Wikipedia by expanding it.|