Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21eb1df1e13cf89

Jump to content

HIPO model

From Wikipedia, the free encyclopedia
(Redirected from HIPO)
IBM stencil for HIPO.

HIPO model (hierarchical input process output model) is a systems analysis design aid and documentation technique from the 1970s,[1] used for representing the modules of a system as a hierarchy and for documenting each module.[2][3]

History

[edit]

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.[4]

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.[3]

See also

[edit]

References

[edit]
  1. IBM Corporation (1974).HIPO—A Design Aid and Documentation Technique, Publication Number GC20-1851, IBM Corporation, White Plains, NY, 1974.
  2. Katzan, Harry Jr. (1976). Systems Design and Documentation: An introduction to the HIPO Method. Van Nostrand Reinhold. ISBN 0-442-24267-0.
  3. 1 2 Sandia National Laboratories (1992). Sandia Software Guidelines Volume 5 Tools, Techniques, and Methodologies Archived 2009-08-25 at the Wayback Machine SANDIA REPORTS 85–2348qUC–32
  4. Mary Ann Goodwin and Charles C. Robertson (1986). EXPERT SYSTEM VERIFICATION CONCERNS IN AN OPERATIONS ENVIRONMENT. NASA paper N88-17234.