Structure chart

4
Structure chart 1 Structure chart Example of a Structured Chart. [1] A Structure Chart (SC) in software engineering and organizational theory is a chart, which shows the breakdown of the configuration system to the lowest manageable levels. [2] This chart is used in structured programming to arrange the program modules in a tree structure. Each module is represented by a box, which contains the module's name. The tree structure visualizes the relationships between the modules. [3] Overview This illustration is hierarchy chart that represent data passing between two modules. When the module Pay_Bill executed, the pseudocode check if it already pay the bill by search the receipt of payment (execute Search_Receipt). If the receipt is not found then it will execute module Give_Money_To_Debt_Collector to finish the job. 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. [4] 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". [5] . A structure chart depicts [2] 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.

description

Software Quality ManagementAnna University SyllabusB.E. IV CSEAbout Structure Chart

Transcript of Structure chart

Page 1: Structure chart

Structure chart 1

Structure chart

Example of a Structured Chart.[1]

A Structure Chart (SC) in softwareengineering and organizational theory isa chart, which shows the breakdown ofthe configuration system to the lowestmanageable levels.[2]

This chart is used in structuredprogramming to arrange the programmodules in a tree structure. Eachmodule is represented by a box, whichcontains the module's name. The treestructure visualizes the relationshipsbetween the modules.[3]

Overview

This illustration is hierarchy chart that represent data passing between twomodules. When the module Pay_Bill executed, the pseudocode check if it

already pay the bill by search the receipt of payment (executeSearch_Receipt). If the receipt is not found then it will execute module

Give_Money_To_Debt_Collector to finish the job.

A structure chart is a top-down modular designtool, constructed of squares representing thedifferent modules in the system, and lines thatconnect them. The lines represent the connectionand or ownership between activities andsubactivities as they are used in organizationcharts.[4]

In structured analysis structure charts, according toWolber (2009), "are used to specify the high-leveldesign, or architecture, of a computer program. Asa design tool, they aid the programmer in dividingand conquering a large software problem, that is,recursively breaking a problem down into partsthat are small enough to be understood by a humanbrain. The process is called top-down design, orfunctional decomposition. Programmers use astructure chart to build a program in a mannersimilar to how an architect uses a blueprint to builda house. In the design stage, the chart is drawn and used as a way for the client and the various software designers tocommunicate. During the actual building of the program (implementation), the chart is continually referred to as themaster-plan".[5] .

A structure chart depicts[2]

• 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.

Page 2: Structure chart

Structure chart 2

A structure chart is also used to diagram associated elements that comprise a run stream or thread. It is oftendeveloped as a hierarchical diagram, but other representations are allowable. The representation must describe thebreakdown of the configuration system into subsystems and the lowest manageable level. An accurate and completestructure chart is the key to the determination of the configuration items, and a visual representation of theconfiguration system and the internal interfaces among its CIs. During the configuration control process, thestructure chart is used to identify CIs and their associated artifacts that a proposed change may impact.[2]

Structure chart construction

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

According to Wolber (2009), "astructure chart can be developedstarting with the creating of a structure,which places the root of anupside-down tree which forms thestructure chart. The next step is toconceptualize the main sub-tasks thatmust be performed by the program tosolve the problem. Next, theprogrammer focuses on each sub-taskindividually, and conceptualizes howeach can be broken down into evensmaller tasks. Eventually, the programis broken down to a point where theleaves of the tree represent simplemethods that can be coded with just afew program statements".[5]

In practice, see figure, first it is checkedif a Structure Chart has been developedalready. If so an expert needs to reviewit to ensure it represents the currentstructure and if not, updates the chart where needed.[2]

References[1] Sandia National Laboratories (1992). Sandia Software Guidelines Volume 5 Tools, Techniques,and Methodologies (http:/ / www. prod.

sandia. gov/ cgi-bin/ techlib/ access-control. pl/ 1985/ 852348. pdf) SANDIA REPORTS 85–2348qUC–32[2] IRS (2008) "Configuration Management"] In: IRS Resources Part 2. Information Technology Chapter 27. Configuration Management.

Accessed at IRS.GOV (http:/ / www. 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] H. Fujita & V. Gruhn (2004). New Trends in Software Methodologies, Tools and Techniques. Page 6.[5] David Wolber (2009) " Structure Charts (http:/ / www. usfca. edu/ ~wolberd/ cs112/ SupplementalNotes/ structureChart. doc): Supplementary

Notes Structure Charts and Bottom-up Implementation: Java Version. Accessed Nov 8, 2009

Page 3: Structure chart

Structure chart 3

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 (http:/ / www. hit. ac. il/ staff/ leonidM/ information-systems/ ch63. html) Overview.• Strategies for converting the DFD into Structure Chart (http:/ / elearning. tvm. tcs. co. in/ SDO/ SDO/ 3_2. htm)• UN structure chart (http:/ / www. un. org/ aboutun/ chart_en. pdf), an example.• State Court Structure Charts (http:/ / www. ncsconline. org/ D_Research/ Ct_Struct/ Index. html), a series of

examples.• Structure Charts (http:/ / www. usfca. edu/ ~wolberd/ cs112/ SupplementalNotes/ structureChart. doc) (.doc).

Page 4: Structure chart

Article Sources and Contributors 4

Article Sources and ContributorsStructure chart  Source: http://en.wikipedia.org/w/index.php?oldid=390748059  Contributors: EagleFan, Ivan Akira, Mdd, Wdfarmer, Weimeranerman, 16 anonymous edits

Image Sources, Licenses and ContributorsFile:Structured Chart Example.jpg  Source: http://en.wikipedia.org/w/index.php?title=File:Structured_Chart_Example.jpg  License: Public Domain  Contributors: Sandia National LaboratoriesFile:Sample of Hierarchy chart.png  Source: http://en.wikipedia.org/w/index.php?title=File:Sample_of_Hierarchy_chart.png  License: Creative Commons Attribution-Sharealike 3.0 Contributors: User:Ivan AkiraImage:Structure chart construction.jpg  Source: http://en.wikipedia.org/w/index.php?title=File:Structure_chart_construction.jpg  License: Public Domain  Contributors: irs.gov

LicenseCreative Commons Attribution-Share Alike 3.0 Unportedhttp:/ / creativecommons. org/ licenses/ by-sa/ 3. 0/