IPO map and HIPO diagram of the relationship?
This project outlines the design requirements of the system elements (each layer of modules, sub-programs, utilities, etc.) relationship. The HIPO diagram is a good representation, which can describe both the overall software module hierarchy and the details of each module's input / output data, processing functions, and module invocation.
because just learned hipo and ipo figure mixed up. hipo ipo hipo figure =ipo figure + hierarchy chart. H diagram shows which modules and their control hierarchies are in the software system; The IPO diagram illustrates the inter-module information transfer and the internal processing of the module;
The process of drawing knowledge tree HIPO diagram: Firstly, the system is decomposed into two subsystems, namely user subsystem and content subsystem. Then the subsystem is divided into modules of the user subsystem is divided into login and registration module, the content subsystem is divided into display and message module. Before this is the hierarchical division of the system, the following is a description of each module input / output data, processing functions, etc. details. Is my description of the HIPO diagram of the Knowledge Tree system:
The level of the HIPO diagram is based on the system-> Subsystem-> Module-> Sub-Program.
Fifth time job