STRUCTURE CHART
A Structure Chart is a chart, which shows
the breakdown of the configuration system to
the lowest manageable levels.
The configuration system is the specific
definition of the elements that define what a
system is composed of.
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 sub activities.
Structure charts 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
by breaking it down into parts that are small enough
to be understood .
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.
Number of readily identifiable functions and
modules within each function.
Whether each identifiable function is a
manageable entity or should be broken down
into smaller components.
Root is always main
Foo:Main
Each node displays
a method
Parameters of display
results
Input
data results
Input data results
Foo:Get Input Foo:Process Input Foo:Display Results
All methods are from the class Foo.
Each node in the chart represents a method
(in object-oriented terms, a method).
The root node represents the main method of
the program.
Each connecting line represents a method
call.
The structure chart above could correspond to the program code displayed
below:
public class Foo
{
public static void main (String[] args)
{
InputData inputData=null;
int result=0;
Foo foo = new Foo();
foo.GetInput(inputData);
result=foo.processInput(inputData);
foo.displayResults(result);}
}
}
There is not a one-to-one correspondence
between a structure chart and a program.
A number of programs could be written that
follow the design of any structure chart.
A structure chart is a high-level design
notation, and leaves some coding details
unspecified.
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, and a visual
representation of the configuration system
and the internal interfaces among its CIs .
Creating a structure, which places the root of
an upside-down tree which forms the
structure chart.
First it is checked a Structure Chart has
been developed already .
Conceptualize the main sub-tasks that must
be performed by the program to solve the
problem.
The programmer focuses on each sub-task
individually, and conceptualizes how each
can be broken down into even smaller tasks .
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 .
Structure Chart modified as programmers
learn new details about the program.
After a program is completed, the structure
chart is used to fix bugs and make changes
(maintenance).
THANK YOU
