According to the text a structure chart is a hierarchical diagram that shows how an information system is organized. In other words a structure chart is something that shows how an information system is organized. In the early days of computers (the 1940's and 1950's) computer programs had to be small because of the restrictions of the computers they were written for. Later the computers grew bigger and had more power, so the programs could become bigger and more complex. Even more important: the users of the systems came up with more requirements. The result of this was a need for tools for analyzing and implementing systems that were better entailed for complex systems.
             In the early 1970's, Larry L. Constantine, together with Edward Yourdon, came up with the concept of structured analysis and structured design. In fact, structured design continues giving guidelines, where structured programming stops. Not only Constantine and Yourdon, but also Stevens and Myers added new ideas to the principle of structured programming. One of the main tools that are used in structured design is the structure chart, developed by Constantine. The structure chart is a variant of the HIPO-technique designed by IBM and models the modular structure of a software system. It does so by showing the modules and their interconnections, the hierarchy relationships between modules, the inter-modular data flow (parameter-passing) and the major decisions and major loops with which a module activates its own subordinate modules.
             According to the textbook, a module is a self- contained component of a system, defined by function. For large systems, several levels of STC (structure charts) will be needed to reflect the number and complexity of the modules in the system, regardless of whether multiprocessing or multitasking is in use. Furthermore, the advent of packages in languages such as Ada also creates the need for more than one level of STC, where the h...