ArticleslgStudy

engineering

Structure chart

Structure chart is a engineering topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Structure chart rather than just read about it. In short: A structure chart (SC) in software engineering and organizational theory is a chart which shows the smallest of a system to its lowest manageable levels. They are used in structured programming to arrange program modules into a tree.

Structure chart — main illustration
Structure chart — illustration

Key takeaways

  • Structure chart belongs to engineering; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Structure chart to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Structure chart from memory before moving on to harder problems.

Reference excerpt

A structure chart (SC) in software engineering and organizational theory is a chart which shows the smallest of a system to its lowest manageable levels. 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.

Overview

A structure chart is a top-down modular design tool, constructed of squares representing the different modules in the system, and lines that connect them. The lines represent the connection and or ownership between activities and subactivities as they are used in organization charts. In structured analysis structure charts, according to Wolber (2009), "are used to specify the high-level design, or architecture, of a computer program. As a design tool, they aid the programmer in dividing and conquering a large software problem, that is, recursively breaking a problem down into parts that are small enough to be understood by a human brain. The process is called top-down design, or functional decomposition. Programmers use a structure chart to build a program in a manner similar to how an architect uses a blueprint to build a house. In the design stage, the chart is drawn and used as a way for the client and the various software designers to communicate. During the actual building of the program (implementation), the chart is continually referred to as "the master-plan". A structure chart depicts

the size and complexity of the system, and number of readily identifiable functions and modules within each function and whether each identifiable function is a manageable entity or should be broken down into smaller components. A structure chart is also used to diagram associated elements that comprise a run stream or thread. It is often developed as a hierarchical diagram, but other representations are allowable. The representation must describe the breakdown of the configuration system into subsystems and the lowest manageable level. An accurate and complete structure chart is the key to the determination of the configuration items (CI), and a visual representation of the configuration system and the internal interfaces among its CIs(define CI clearly). During the configuration control process, the structure chart is used to identify CIs and their associated artifacts that a proposed change may impact.

Structure chart construction 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". 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.

See also

Computer-aided software engineering System context diagram Decomposition diagram Function model HIPO Structured Analysis and Design Technique Warnier/Orr diagram Work breakdown structure

References

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,

External links Structure charts Overview. State Court Structure Charts, a series of examples. Structure Charts (.doc).

Illustrations

Structure chart: Example of a Structured Chart.[1]
Example of a Structured Chart.[1]
Structure chart: This hierarchy chart represents data passing between two modules. When the module Pay_Bill is executed, the pseudocode checks if the bill is already paid by searching for the payment receipt (execute Search_Receipt). If the receipt is not found then it will execute the module Give_Money_To_Debt_Collector to finish the job.
This hierarchy chart represents data passing between two modules. When the module Pay_Bill is executed, the pseudocode checks if the bill is already paid by searching for the payment receipt (execute Search_Receipt). If the receipt is not found then it will execute the module Give_Money_To_Debt_Collector to finish the job.
Structure chart: A process flow diagram describing the construction of a structure chart by a so-called Subject Matter Experts (SME).[2]
A process flow diagram describing the construction of a structure chart by a so-called Subject Matter Experts (SME).[2]

Worked examples

Example 1 — a first encounter with Structure chart

Start with the simplest possible case. Write down what Structure chart claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In engineering, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Structure chart before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Structure chart ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Structure chart

In research
Structure chart appears in engineering research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Structure chart in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Structure chart is common in secondary-school and first-year university syllabi. It links to neighbouring topics Charts, Systems analysis, so understanding it makes those chapters shorter.
In everyday life
Look for Structure chart outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Structure chart in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Structure chart means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Structure chart out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Structure chart in simple terms?

A structure chart (SC) in software engineering and organizational theory is a chart which shows the smallest of a system to its lowest manageable levels. They are used in structured programming to arrange program modules into a tree.

Why does Structure chart matter?

Because it connects several engineering ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Structure chart?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Structure chart.

Tags

  • Charts
  • Systems analysis

Keep exploring