Structure charts
Download
1 / 19

- PowerPoint PPT Presentation


  • 298 Views
  • Updated On :

STRUCTURE CHARTS. Elements and Definitions. Software System Design. translates SRS into a ===> software system architecture: system’s static structure system’s possible dynamic behaviour data structures user interface design. Structured Analysis and Design. prepare and analyse a

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about '' - derora


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Structure charts l.jpg

STRUCTURE CHARTS

Elements and Definitions


Software system design l.jpg
Software System Design

  • translates SRS into a

    ===> software system architecture:

    • system’s static structure

    • system’s possible dynamic behaviour

    • data structures

    • user interface design


Structured analysis and design l.jpg
Structured Analysis and Design

  • prepare and analyse a

    Data Flow Diagram - DFD

  • derive from the DFD a

    Structure Chart


Structure chart l.jpg
Structure Chart

  • supports the system and module design phase

  • diagramming technique with annotations

  • hierarchy of modules

  • control (invocation) is explicitly modelled

  • data flows follow control hierarchy

  • decomposition is shown in the control hierarchy

  • software / computer oriented

  • derived from the DFD and further refined


System structure control hierarchy l.jpg
System Structure - Control Hierarchy

S

I1

I2

C1

O1

I11

I12

I21

C11

O11

O12


Complete sc design l.jpg
Complete SC Design

  • Structure Chart Diagram

  • Data Dictionary (e.g. BNF)

  • Module Specifications (e.g. PDL)

    ===> consistent with DFD!


Structure charts module l.jpg
Structure Charts - Module

  • process / subroutine / task

  • unit of execution

  • accepts parameters as inputs

  • produces parameters as outputs

  • parameters: data or control

  • can be invoked and can invoke

  • label: verb

  • linked to module specification

label


Structure charts special modules l.jpg
Structure Charts - Special Modules

label

  • predefined (reused) module

  • highly useful

  • “macro” module

  • avoid

label

  • multi-entry module

  • avoid

label


Structure charts invocation call l.jpg
Structure Charts - Invocation / Call

  • call of subordinate module

  • connector element

  • NOT a data flow

  • one specific form of control flow

  • has a direction

  • no split or join

  • NO label


Structure charts invocation jump to address l.jpg
Structure Charts - Invocation / Jump to Address

  • call jumps INTO

    invoked module

  • assembler type of programming

  • modification at run-time

  • avoid


Structure charts sequence of execution l.jpg
Structure Charts - Sequence of Execution

  • sequence of subordinate modules in the diagram is not reflecting a binding sequence of invocation

  • sequence of invocation is defined in the specification of the super-ordinate module

  • module specification is

    the decisive element

X

X1

X2

X3


Structure charts conditional execution l.jpg
Structure Charts - Conditional Execution

  • call of subordinate module depends on a condition

  • no label

  • condition is defined in the module specification

  • module specification is

    the decisive element


Structure charts loops in the execution l.jpg
Structure Charts - Loops in the Execution

  • call of subordinate modules runs in a loop

  • no label or condition

  • loop (and its condition) is defined in the module specification

  • module specification is

    the decisive element


Structure charts data flow l.jpg
Structure Charts - Data Flow

  • flow of information

  • data transfer

  • bound to invocation

  • has a direction

  • no splits or joins

  • label: noun

  • specified in data-dictionary

label

label

label


Structure charts control flow l.jpg
Structure Charts - Control Flow

  • flow of control (<> invocation)

    ==> control execution path

    of targeted module

  • bound to invocation

  • has a direction

  • no splits or joins

  • label: flag, decision, condition

  • specified in data-dictionary

label

label

label


Structure charts data store l.jpg
Structure Charts - Data Store

  • storage for permanent data

  • database / file

  • passive; no activity beyond

    basic retrieval capacity

  • serviced by a module

  • label: noun

  • specified in data-dictionary

    and/or with an ER-diagram

label


Structure charts devices interfaces l.jpg
Structure Charts - Devices / Interfaces

  • provides connection to

    peripheral devices

  • origin / destination of

    external data flows (controls)

  • not part of the software

    to be developed

  • label: noun

  • specified in data-dictionary

label


Structure charts sw infrastructure l.jpg
Structure Charts - SW Infrastructure

  • provides connection to

    external systems, databases, operating system, etc.

  • origin / destination of

    external data flows (controls)

  • not part of the software

    to be developed

  • label: noun

  • specified in data-dictionary

label


End of section 3b l.jpg
End of Section 3b

coming up:

an example for

Structure Charts


ad