SlideShare une entreprise Scribd logo
1  sur  4
Télécharger pour lire hors ligne
Structure chart                                                                                                                              1



     Structure chart
     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]
                                                                                                              [1]
                                                                                Example of a Structured Chart.




     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.[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
                                                              This illustration is hierarchy chart that represent data passing between two
     that are small enough to be understood by a human        modules. When the module Pay_Bill executed, the pseudocode check if it
     brain. The process is called top-down design, or                already pay the bill by search the receipt of payment (execute
     functional decomposition. Programmers use a               Search_Receipt). If the receipt is not found then it will execute module
                                                                           Give_Money_To_Debt_Collector to finish the job.
     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.
Structure chart                                                                                                                                      2


     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, and a visual representation of the
     configuration system and the internal interfaces among its CIs. During the configuration control process, the
     structure chart is used to identify CIs and their associated artifacts that a proposed change may impact.[2]


     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".[5]

     In practice, see figure, first it is checked
                                                    A process flow diagram describing the construction of a structure chart by a so called
     if a Structure Chart has been developed                                                                [2]
                                                                            Subject Matter Experts (SME).
     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]


     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
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).
Article Sources and Contributors                                                                                                                                                                 4



    Article Sources and Contributors
    Structure 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 Contributors
    File:Structured Chart Example.jpg  Source: http://en.wikipedia.org/w/index.php?title=File:Structured_Chart_Example.jpg  License: Public Domain  Contributors: Sandia National Laboratories
    File: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 Akira
    Image:Structure chart construction.jpg  Source: http://en.wikipedia.org/w/index.php?title=File:Structure_chart_construction.jpg  License: Public Domain  Contributors: irs.gov




    License
    Creative Commons Attribution-Share Alike 3.0 Unported
    http:/ / creativecommons. org/ licenses/ by-sa/ 3. 0/

Contenu connexe

Tendances

Flow oriented modeling
Flow oriented modelingFlow oriented modeling
Flow oriented modeling
ramyaaswin
 
1.1 The nature of software.ppt
1.1 The nature of software.ppt1.1 The nature of software.ppt
1.1 The nature of software.ppt
JAYAPRIYAR7
 
System Models in Software Engineering SE7
System Models in Software Engineering SE7System Models in Software Engineering SE7
System Models in Software Engineering SE7
koolkampus
 
Uml Presentation
Uml PresentationUml Presentation
Uml Presentation
mewaseem
 

Tendances (20)

Polygons - Computer Graphics - Notes
Polygons - Computer Graphics - NotesPolygons - Computer Graphics - Notes
Polygons - Computer Graphics - Notes
 
Rad model
Rad modelRad model
Rad model
 
RMMM-Risk Management,Mitigation and Monitoring.
RMMM-Risk Management,Mitigation and Monitoring.RMMM-Risk Management,Mitigation and Monitoring.
RMMM-Risk Management,Mitigation and Monitoring.
 
Flow oriented modeling
Flow oriented modelingFlow oriented modeling
Flow oriented modeling
 
software cost factor
software cost factorsoftware cost factor
software cost factor
 
Software Cost Estimation Techniques
Software Cost Estimation TechniquesSoftware Cost Estimation Techniques
Software Cost Estimation Techniques
 
1.1 The nature of software.ppt
1.1 The nature of software.ppt1.1 The nature of software.ppt
1.1 The nature of software.ppt
 
Software design
Software designSoftware design
Software design
 
Software Engineering (Project Scheduling)
Software Engineering (Project Scheduling)Software Engineering (Project Scheduling)
Software Engineering (Project Scheduling)
 
System Models in Software Engineering SE7
System Models in Software Engineering SE7System Models in Software Engineering SE7
System Models in Software Engineering SE7
 
SE_Lec 05_System Modelling and Context Model
SE_Lec 05_System Modelling and Context ModelSE_Lec 05_System Modelling and Context Model
SE_Lec 05_System Modelling and Context Model
 
Ian Sommerville, Software Engineering, 9th EditionCh 8
Ian Sommerville,  Software Engineering, 9th EditionCh 8Ian Sommerville,  Software Engineering, 9th EditionCh 8
Ian Sommerville, Software Engineering, 9th EditionCh 8
 
PROTOTYPE MODEL
PROTOTYPE MODELPROTOTYPE MODEL
PROTOTYPE MODEL
 
Defining the Problem - Goals and requirements
Defining the Problem - Goals and requirementsDefining the Problem - Goals and requirements
Defining the Problem - Goals and requirements
 
Uml Presentation
Uml PresentationUml Presentation
Uml Presentation
 
Cocomo model
Cocomo modelCocomo model
Cocomo model
 
Reusibility vs Extensibility in OOAD
Reusibility vs Extensibility in OOADReusibility vs Extensibility in OOAD
Reusibility vs Extensibility in OOAD
 
Rayleigh model
Rayleigh modelRayleigh model
Rayleigh model
 
Lecture 12 requirements modeling - (system analysis)
Lecture 12   requirements modeling - (system analysis)Lecture 12   requirements modeling - (system analysis)
Lecture 12 requirements modeling - (system analysis)
 
Requirements analysis
Requirements analysisRequirements analysis
Requirements analysis
 

En vedette (12)

DFD, Decision Table, Decision Chart, Structure Charts
DFD, Decision Table, Decision Chart, Structure ChartsDFD, Decision Table, Decision Chart, Structure Charts
DFD, Decision Table, Decision Chart, Structure Charts
 
Structured Analysis and Structured Design
Structured Analysis and Structured DesignStructured Analysis and Structured Design
Structured Analysis and Structured Design
 
Decision tables
Decision tablesDecision tables
Decision tables
 
Structured analysis and structured design
Structured analysis  and structured designStructured analysis  and structured design
Structured analysis and structured design
 
Bisnis proses
Bisnis prosesBisnis proses
Bisnis proses
 
Desain arsitektur-pl-pert5
Desain arsitektur-pl-pert5Desain arsitektur-pl-pert5
Desain arsitektur-pl-pert5
 
Bab 11 component diagram 2010
Bab 11 component diagram 2010Bab 11 component diagram 2010
Bab 11 component diagram 2010
 
Desain arsitektur
Desain arsitekturDesain arsitektur
Desain arsitektur
 
Re-Engineering
Re-EngineeringRe-Engineering
Re-Engineering
 
L7 decision tree & table
L7 decision tree & tableL7 decision tree & table
L7 decision tree & table
 
Business process reengineering
Business process reengineeringBusiness process reengineering
Business process reengineering
 
System Analysis and Design
System Analysis and DesignSystem Analysis and Design
System Analysis and Design
 

Similaire à Structure chart

Chapter 7 Design Architecture and Methodology1.docx
Chapter 7 Design Architecture and Methodology1.docxChapter 7 Design Architecture and Methodology1.docx
Chapter 7 Design Architecture and Methodology1.docx
mccormicknadine86
 
Ch7-Software Engineering 9
Ch7-Software Engineering 9Ch7-Software Engineering 9
Ch7-Software Engineering 9
Ian Sommerville
 

Similaire à Structure chart (20)

Modeling software architecture with uml
Modeling software architecture with umlModeling software architecture with uml
Modeling software architecture with uml
 
Object oriented analysis and design unit- iv
Object oriented analysis and design unit- ivObject oriented analysis and design unit- iv
Object oriented analysis and design unit- iv
 
Object oriented sad-5 part ii
Object oriented sad-5 part iiObject oriented sad-5 part ii
Object oriented sad-5 part ii
 
Design
DesignDesign
Design
 
Object oriented sad-5 part i
Object oriented sad-5 part iObject oriented sad-5 part i
Object oriented sad-5 part i
 
CS8592 Object Oriented Analysis & Design - UNIT I
CS8592 Object Oriented Analysis & Design - UNIT ICS8592 Object Oriented Analysis & Design - UNIT I
CS8592 Object Oriented Analysis & Design - UNIT I
 
Design Engineering is a topic of software engineering of second year fourth s...
Design Engineering is a topic of software engineering of second year fourth s...Design Engineering is a topic of software engineering of second year fourth s...
Design Engineering is a topic of software engineering of second year fourth s...
 
Design Concepts in Software Engineering-1.pptx
Design Concepts in Software Engineering-1.pptxDesign Concepts in Software Engineering-1.pptx
Design Concepts in Software Engineering-1.pptx
 
Chapter 7 Design Architecture and Methodology1.docx
Chapter 7 Design Architecture and Methodology1.docxChapter 7 Design Architecture and Methodology1.docx
Chapter 7 Design Architecture and Methodology1.docx
 
software engineering Architecture and design Unit 3.pptx
software engineering Architecture and design Unit 3.pptxsoftware engineering Architecture and design Unit 3.pptx
software engineering Architecture and design Unit 3.pptx
 
SOURCE CODE MANAGEMENT SYSTEM (GITHUB)
SOURCE CODE MANAGEMENT SYSTEM (GITHUB)SOURCE CODE MANAGEMENT SYSTEM (GITHUB)
SOURCE CODE MANAGEMENT SYSTEM (GITHUB)
 
UNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptx
UNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptxUNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptx
UNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptx
 
Ch7-Software Engineering 9
Ch7-Software Engineering 9Ch7-Software Engineering 9
Ch7-Software Engineering 9
 
Reverse Engineering for Documenting Software Architectures, a Literature Review
Reverse Engineering for Documenting Software Architectures, a Literature ReviewReverse Engineering for Documenting Software Architectures, a Literature Review
Reverse Engineering for Documenting Software Architectures, a Literature Review
 
Chapter 3_Software Design sunorganisedASE_BW_finalised.ppt
Chapter 3_Software Design sunorganisedASE_BW_finalised.pptChapter 3_Software Design sunorganisedASE_BW_finalised.ppt
Chapter 3_Software Design sunorganisedASE_BW_finalised.ppt
 
Software Architecture and Design
Software Architecture and DesignSoftware Architecture and Design
Software Architecture and Design
 
Distributed Graphical User Interfaces to Class Diagram: Reverse Engineering A...
Distributed Graphical User Interfaces to Class Diagram: Reverse Engineering A...Distributed Graphical User Interfaces to Class Diagram: Reverse Engineering A...
Distributed Graphical User Interfaces to Class Diagram: Reverse Engineering A...
 
software Design.ppt
software Design.pptsoftware Design.ppt
software Design.ppt
 
Visualizing Software Architecture Effectively in Service Description
Visualizing Software Architecture Effectively in Service DescriptionVisualizing Software Architecture Effectively in Service Description
Visualizing Software Architecture Effectively in Service Description
 
Unit-3.doc
Unit-3.docUnit-3.doc
Unit-3.doc
 

Plus de Roy Antony Arnold G

Plus de Roy Antony Arnold G (20)

6 sigma
6 sigma6 sigma
6 sigma
 
Run chart
Run chartRun chart
Run chart
 
Reliability growth models for quality management
Reliability growth models for quality managementReliability growth models for quality management
Reliability growth models for quality management
 
6 sigma
6 sigma6 sigma
6 sigma
 
Quality management models
Quality management modelsQuality management models
Quality management models
 
Pareto diagram
Pareto diagramPareto diagram
Pareto diagram
 
Ishikawa diagram
Ishikawa diagramIshikawa diagram
Ishikawa diagram
 
Histogram
HistogramHistogram
Histogram
 
Customer satisfaction
Customer satisfactionCustomer satisfaction
Customer satisfaction
 
Control chart
Control chartControl chart
Control chart
 
Complexity metrics and models
Complexity metrics and modelsComplexity metrics and models
Complexity metrics and models
 
Check lists
Check listsCheck lists
Check lists
 
Capability maturity model
Capability maturity modelCapability maturity model
Capability maturity model
 
Seven new tools
Seven new toolsSeven new tools
Seven new tools
 
Scatter diagram
Scatter diagramScatter diagram
Scatter diagram
 
Qms
QmsQms
Qms
 
Relations diagram
Relations diagramRelations diagram
Relations diagram
 
Rayleigh model
Rayleigh modelRayleigh model
Rayleigh model
 
Defect removal effectiveness
Defect removal effectivenessDefect removal effectiveness
Defect removal effectiveness
 
Customer satisfaction
Customer satisfactionCustomer satisfaction
Customer satisfaction
 

Structure chart

  • 1. Structure chart 1 Structure chart 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] [1] Example of a Structured Chart. 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.[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 This illustration is hierarchy chart that represent data passing between two that are small enough to be understood by a human modules. When the module Pay_Bill executed, the pseudocode check if it brain. The process is called top-down design, or already pay the bill by search the receipt of payment (execute functional decomposition. Programmers use a Search_Receipt). If the receipt is not found then it will execute module Give_Money_To_Debt_Collector to finish the job. 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.
  • 2. Structure chart 2 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, and a visual representation of the configuration system and the internal interfaces among its CIs. During the configuration control process, the structure chart is used to identify CIs and their associated artifacts that a proposed change may impact.[2] 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".[5] In practice, see figure, first it is checked A process flow diagram describing the construction of a structure chart by a so called if a Structure Chart has been developed [2] Subject Matter Experts (SME). 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] 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
  • 3. 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).
  • 4. Article Sources and Contributors 4 Article Sources and Contributors Structure 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 Contributors File:Structured Chart Example.jpg  Source: http://en.wikipedia.org/w/index.php?title=File:Structured_Chart_Example.jpg  License: Public Domain  Contributors: Sandia National Laboratories File: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 Akira Image:Structure chart construction.jpg  Source: http://en.wikipedia.org/w/index.php?title=File:Structure_chart_construction.jpg  License: Public Domain  Contributors: irs.gov License Creative Commons Attribution-Share Alike 3.0 Unported http:/ / creativecommons. org/ licenses/ by-sa/ 3. 0/