Structured Systems

Analysis and Design

Methodology
 What is Structured Systems Analysis And Design Method
 It is a set of standards for systems analysis and
(SSADM)?
application design that uses a formal methodical
approach to the analysis and design of information
systems.

 Open methodology based on the waterfall model.

What is Structured
Systems Analysis
 Developed by Learmonth Burchett Management
And Design Systems (LBMS) and the Central Computer
Method (SSADM)? Telecommunications Agency (CCTA) in 1980-1981 as a
standard for developing British database projects.

 It has been used by many commercial businesses,

consultants, educational establishments and CASE tool
developers.
 Structured Systems Analysis And Design Method
 follows the waterfall life cycle model starting from the
feasibility study to the physical design stage of
development.

Structured
Systems Analysis  intensive user involvement in the requirements analysis
stage.
And Design  The users are made to sign off each stage as they are

Method completed assuring that requirements are met.

 The users are provided with clear, easily understandable

documentation consisting of various diagrammatic
representations of the system.
  It is graphic which specifies the presentation of
application.

 It divides the processes so that it gives a clear picture of

Attributes of system flow.

Structured
Analysis  It is logical rather than physical i.e., the elements of
system do not depend on vendor or hardware.

 It is an approach that works from high-level overviews

to lower-level details.
 Structured Systems Analysis And Design Method

SSADM breaks up a development project into stages,

modules, steps and tasks.
Structured
Systems Analysis The first and foremost model developed in SSADM is the
And Design data model. It is a part of requirements gathering and
Method consists of well defined stages, steps and products.
 1. Logical Data Modeling- This involves the process of
identifying, modeling and documenting data as a part of
system requirements gathering. The data are classified
further into entities and relationships.

2. Data Flow Modeling- This involves tracking the data

Techniques used flow in an information system. It clearly analyzes the
in SSADM processes, data stores, external entities and data
movement.

3. Entity Behavior Modeling- This involves identifying and

documenting the events influencing each entity and the
sequence in which these events happen.
 Various tools used for system development during
Structured Analysis-

 Data Flow Diagrams

Structured  Data Dictionary
Analysis  Decision Trees

Tools  Decision Tables

 Structured English
 Pseudocode
Structured
Analysis
Tools
 It is a technique developed by Larry Constantine to express
the requirements of system in a graphical form.

 It shows the flow of data between various functions of system

and specifies how the current system is implemented.

Data Flow  It is an initial stage of design phase that functionally divides

Diagrams the requirement specifications down to the lowest level of

(DFD) or
detail.

Bubble Chart  Its graphical nature makes it a good communication tool

between user and analyst or analyst and system designer.

 It gives an overview of what data a system processes, what

transformations are performed, what data are stored, what
results are produced and where they flow.
 Symbol Name Symbol Meaning

Source or
Square
Destination of Data
Basic Elements Arrow Data flow
of Data Flow Process
Diagrams Circle transforming data
flow

Open Rectangle Data Store

 Physical Logical

It is implementation
It is implementation
independent. It focuses only
dependent. It shows which
on the flow of data between
functions are performed.
processes.
Types of Data
Flow Diagram It provides low level details of
hardware, software, files, and
It explains events of systems
and data required by each
people. event.

It depicts how the current It shows how business

system operates and how a operates; not how the system
system will be implemented. can be implemented.
  A context diagram helps in understanding the entire
system by one DFD which gives the overview of a
system.
Context
Diagram  It starts with mentioning major processes with little
details and then goes onto giving more details of the
processes with the top-down approach.
  is a structured repository of data elements in the
system. It stores the descriptions of all DFD data
elements that is, details and definitions of data flows,
data stores, data stored in data stores, and the
Data processes.

Dictionary
 A data dictionary improves the communication between
the analyst and the user. It plays an important role in
building a database.
  A method for defining complex relationships by
describing decisions and avoiding the problems in
communication.

 It is a diagram that shows alternative actions and

conditions within horizontal tree framework. Thus, it
depicts which conditions to consider first, second, and so

Decision on.

Trees  Depict the relationship of each condition and their

permissible actions. A square node indicates an action and
a circle indicates a condition.

 The major limitation of a decision tree is that it lacks

information in its format to describe what other
combinations of conditions you can take for testing.
 Decision tables are a method of describing the complex
logical relationship in a precise manner which is easily
understandable.

Decision  It is useful in situations where the resulting actions

depend on the occurrence of one or several combinations
Tables of independent conditions.

 It is a matrix containing row or columns for defining a

problem and the actions.
  Condition Stub − It is in the upper left quadrant which
lists all the condition to be checked.

 Action Stub − It is in the lower left quadrant which

outlines all the action to be carried out to meet such
condition.

Components of
 Condition Entry − It is in upper right quadrant which
a Decision Table provides answers to questions asked in condition stub
quadrant.

 Action Entry − It is in lower right quadrant which

indicates the appropriate action resulting from the
answers to the conditions in the condition entry
quadrant.
 The entries in decision table are given by Decision Rules
which define the relationships between combinations of
conditions and courses of action.

These rules are:

Components of  Y shows the existence of a condition.
a Decision Table  N represents the condition, which is not satisfied.
 A blank - against action states it is to be ignored.
 X (or a check mark will do) against action states it is to
be carried out.
  Structure English is derived from structured
programming language which gives more
understandable and precise description of process.
Structured
English  It is based on procedural logic that uses construction
and imperative sentences designed to perform
operation for action.
 A pseudocode does not conform to any programming
language and expresses logic in plain English.

 It may specify the physical programming logic without

Pseudocode actual coding during and after the physical design.

 It is used in conjunction with structured programming.

 It replaces the flowcharts of a program.

  Dividing a project into small modules with well defined
objectives

 Useful during requirements specification and system

design stage

Important
 Diagrammatic representation and other useful
Characteristic modeling techniques

s of SSADM  Simple and easily understood by clients and

developers

 Performing activities in a sequence

 1. Determining feasibility

2. Investigating the current environment

3. Determining business systems options

Stages of 4. Defining requirements

SSADM 5. Determining technical system options

6. Creating the logical design

7. Creating the physical design