Jump to content

Structure chart

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 194.168.185.50 (talk) at 12:32, 12 September 2013 (Overview). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Example of a Structured Chart.[1]

A Structure Chart (SC) in software engineering and organizational theory, is a chart which shows the breakdown of a system to its lowest manageable levels.[2] They are used in structured programming to arrange program modules into a tree. Each module is represented by a box, which contains the module's name. The tree structure visualizes the relationships between modules.[3]


Structure of a very good school. Structure made by ICT department derby.

Structure chart construction

A process flow diagram describing the construction of a structure chart by a so called Subject Matter Experts (SME).[2]

According to Wolber (2009), "a structure chart can be developed starting with the creating of a structure, which places the root of an upside-down tree which forms the structure chart. The next step is to conceptualize the main sub-tasks that must be performed by the program to solve the problem. Next, the programmer focuses on each sub-task individually, and conceptualizes how each can be broken down into even smaller tasks. Eventually, the program is broken down to a point where the leaves of the tree represent simple methods that can be coded with just a few program statements".[4]

In practice, see figure, first it is checked if a Structure Chart has been developed already. If so an expert needs to review it to ensure it represents the current structure and if not, updates the chart where needed.[2]

See also

References

  1. ^ Sandia National Laboratories (1992). Sandia Software Guidelines Volume 5 Tools, Techniques,and Methodologies SANDIA REPORTS 85–2348qUC–32
  2. ^ a b c IRS (2008) "Configuration Management"] In: IRS Resources Part 2. Information Technology Chapter 27. Configuration Management. Accessed at IRS.GOV 14 Nov 2008. No longer online Nov 8, 2009.
  3. ^ James Martin, Carma L. McClure (1988). Structured Techniques: The Basis for Case. Prentice Hall. p.56.
  4. ^ Cite error: The named reference Wol was invoked but never defined (see the help page).

Further reading

  • Sarah Brooks (1981). "Structure Charts and Basic Programming". in: MATYC Journal, v15 n2 p. 107-112 Spring 1981.
  • Tom DeMarco (1979). Structured Analysis and System Specification. Prentice Hall.
  • Edward Yourdon (1999). Modern Structured Analysis, Yourdon Press Computing Series, 1999,