Structure Systems Analysis & Design

Prof P Karthikeyan Assistant Professor Senior Professor.

What is SSA & SD ?

Composite of two separate but related p p techniques. First is Structured System Analysis, which is concerned with the modeling of p ob e e ated eatu es o problem-related features of a system, syste , making use of a set of descriptive forms a ca a so o a c ec u a that can also be used for architectural design The second is Structured Design which in turn is oriented towards the solutionrelated aspects

Structured Systems Analysis and Structured Design The Structured Systems Analysis - SSA techniques are centered on the use of the Data-Flow Diagram, or DFD, while the Structure Design SD process makes use of the Structure Chart. I. I Representation forms for SSA/SD 1. Representations for structured systems analysis 2. Representations used for structured design p g II. The SSA/SD Process 1. Structure system analysis 2. Transaction Analysis 3. Transform Analysis 4. Completing the design Process

I. Representation forms for SSA/SD Representations for structured systems analysis

The Structured Systems Analysis techniques are centered on the use of the Data Flow Diagram, or DFD. DFDs provide a problem-oriented and functional viewpoint that does not involve making any

assumptions about hierarchy. The techniques of Structured Systems Analysis guide the designer in building a model of the problem by using DFDs, elaborating this where necessary by

The functional viewpoint provided through the use of DFDs can be augmented by means of more detailed descriptions in the form of process specifications or P-Specs(mini specs). A P Spec is a textual description of the primitive P-Spec process that is represented by a bubble in a DFD, and so can be regarded as a subsidiary functional viewpoint. A typical P-Spec will summarize the process in terms of its title a description of the input/output data flow title, relating to the process, and the procedural tasks that it performs couched in terms of the basic concepts of

Representations for structured systems analysis

P Spec P-Spec number corresponds to bubble id-number

P-Spec title

3.2.1 Cash Withdrawal /* customer selected withdraw cash option */ 1. Prompt customer to select from receipt option. 2. If receipt required selected 2.1.set provide receipt flag 3. 4.

Numbered steps (for easier reference)

Data dictionary: used to record the information content of data flows flows. This typically included descriptions of all of the data forms that are mentioned in the DFDs, P-Specs and any other forms of description that might be used. The initial description provided by the data dictionary should b hi hl abstract, and should not f h ld be highly b t t d h ld t focus upon physical format. More recent developments in design practice

encourage the analyst to develop a set of ERDs as a means of modeling the relationships between the data

Conventions For clarity the use of the following operators is helpful: = means is or is equivalent to. + means AND [] means either/OR, so that one of the enclosed options will be selected {} means the components inside the braces are iterated ( ) means that the component is optional p p Examples Customer-id = bank code + sort code + account number Account summary = account number + (withdrawal amount) + {transaction log entries} + [withdraw | withdraw receipt | accnt summary ]

Representations used for structured design

In I comparison with th variety of f i ith the i t f forms th t can that be used for the task of analyzing the structure of a problem, the Structured Design activities mostly make use of only one significant form of diagrammatical y g g notation. As might be expected, the view point adopted is a constructional one, and it is provided by the , p y Structure Chart.

It is chiefly concerned with describing the functions of the subprograms that make up a program, together with the run-time invocation hierarchy that links them them. It is therefore the task of the Structured Design part of the method to bridge the gap between the very different viewpoint and forms that are used for structured systems analysis and for

structured design, and the next section provides an outline of the way in which this is

Two-pass Assembler

First Pass symb ol Add symbol to table Size instructio n

Second Pass

Print listing symbo l

Generat e opcode

Get symbol value

Print line buffer

Simple example of Structure Chart

SSA/SD Process
Basic 5 steps: p 1. Construct an initial DFD to provide a top-level description of the problem (the context diagram). 2. Elaborate this into a layered hierarchy of DFDs, supported by a data dictionary. 3. 3 Use transaction analysis to divide the DFD into tractable units 4. Perform a Transform Analysis on the DFD created for each transaction, in order to produce a Structure Chart for the transaction. 5. 5 Merge the resulting structure charts to create the basic implementation plans, and refine them to include any necessary error-handling, initialization , and other exceptions. d th ti

Transformation Diagram for Structured Systems Analysis and Structured Design y g

Requirement Document 1. Construct initial DFD Data Flow Diagram Transformation of viewpoint (Creation of model)

2. Refine
DFD and expand d Data Flow Diagrams

Refinement of viewpoint

3. Transaction Analysis Data Flow Diagrams 4. 4 Transform Analysis Structure Chart

Refinement of viewpoint

Optionally add central transform

Transformation of viewpoint (add decisions about invocation)

5. Merge and Refine

Refinement of viewpoint

Structure Chart

Requirements document 1. Construct initial DFD Transformation of viewpoint(creation of model) Data flow diagram 2. Refine DFD and Expand Elaboration of view point
Optionally add central transform

Data flow diagram 3. Transaction Analysis Elaboration of view point Data flow diagrams 4. Transform Analysis Transformation of view point( add decisions about i d i i b t invocation) ti ) Structure charts 5. Merge and refine 5 M d fi Structure Chart

Step 1 and 2 : Structured System Analysis Level 0 = context diagram. Level 1 = top level DFD. Level 2 = explosion of level 1 DFD bubbles bubbles. Level 3 = use this level as appropriate.

Step 3: The transaction analysis step and has five basic components: The event in the systems environment that causes the transaction to occur; ; The stimulus that is applied to the system to inform it about the event; The activity that is performed by the system as a result of the stimulus; Th response that this generates in t The th t thi t i terms of output f t t from the system; The effect that this has upon the environment;

Step 4: Identify the central transform in the DFD: You do not have to redraw the DFDs but if you add a boss bubble redraw showing where the boss fits. y p Which will allow you to develop a hierarchical structure chart. Develop structure charts for all of your level 1-2 DFDs. DFD

Step 5: Merge the Structure Charts The objective of this step is to produce a single structure chart

Co s uc g SSA SD o SafeHome security Constructing SS & S for Sa e o e secu y system

Co e Context Diagram : S g e Bubble ag a Single ubb e

Step 3: Transform Analysis

Step 4: Identify the central transform in the DFD:

Step 4: Identify the central transform in the DFD:

Step 4: Identify the central transform in the DFD:

Step 4: Identify the central transform in the DFD:

Step 4: Identify the central transform in the DFD:

Step 5: Merge the Structure Charts M th St t Ch t