See discussions, stats, and author profiles for this publication at: [Link]

net/publication/266797414

STRUCTURED SYSTEMS ANALYSIS AND DESIGN METHOD (SSADM)

Data · October 2014

DOI: 10.13140/2.1.3902.2083

CITATION READS

1 18,239

1 author:

Sadagopan Parthasarathy
C FACTOR ACADEMY, PUNE
13 PUBLICATIONS 100 CITATIONS

SEE PROFILE

All content following this page was uploaded by Sadagopan Parthasarathy on 14 October 2014.

The user has requested enhancement of the downloaded file.

 SADSE 41

“A disciplined approach is better than mere intuitions”

CHAPTER - 4
STRUCTURED SYSTEMS ANALYSIS
AND DESIGN METHOD (SSADM)

4.1 Need for Structured Analysis and Design

Conventional system development method (SDLC) has some limitations.
These limitations are :
1. Interaction with the user is limited. The users interact with the
systems analyst at the problem identifications and feasibility study
stages. After that they are expected to use the system when it is
implemented. Hence for the user, the new system is a black box.
Further in SDLC, there is no proper mode for the user to express his
requirements clearly to the analyst at different stages.
2. The systems analyst is constantly overwhelmed with the business
and technical details of the system.
3. The analytical tools of SDLC like system flowchart, program flowchart
etc. are concerned more with physical aspect of the system rather
than the logical ones. Also, some of the SDLC tools are narrative
and vague instead of being precise and clear in their format. It
becomes difficult for the user to understand how the system parts fit
together.
4. The system specifications of SDLC are difficult to maintain or modify.
Even a small change in the users’ requirements necessitates several
changes in different system documents. The user has to plough through
several documents in order to find the information pertaining to particular
part of the system and this frustrates the user.
5. Software development is bottom-up. Hence the package can be
viewed only after it is fully complete by which time it becomes difficult
to make any correction.
6. All system documentation is prepared at the end of the project.
In short, SDLC lacks a structured approach to system development.
The structured methodology has overcome most of the disadvantages
of the conventional method. We shall discuss the structured method
here in this chapter.
42 Structured Systems Analysis and Design Method SADSE 43

4.2 What is SSADM ? The term structured is borrowed from Structured Programming.
The word structured generally imposes a structure or a disciplined
Structured systems analysis and design is a well defined approach
approach on the design of the system.
in the form of methodology. It is not new. SSADM is in fact a modified
form of SDLC. Hence we can also call SSADM as SDLC using structured SSADM Methodology
techniques.
1. System Survey
SSADM consists of :
The first step in SSADM is system survey. The subactivities in
1) System Survey 2) Structured Analysis survey are
3) Structured Design 4) Hardware Study 1. Identify the scope of the current system.
5) Implementation and 6) Maintenance 2. Identify and list the deficiencies in the current system by taking
into consideration the user requirements.
Structured 3. Establish new system goals and identify the constraints.
Feasibility
Spcific-
Docum- 4. Prepare a document consisting of
2 ations
ents 3 Test Plan
User 1 Structured - goals and objectives
→ → → Structured →
requirements Survey Analysis - customized project life cycle
Design →
Packaged - constraints regarding technical and procedural aspect
Physical
→

Design
→

Requirements - cost benefit analysis

Configuration
4 This phase is similar to feasibility study in SDLC
details
Configuring
2. Structured Analysis
Hardware
Hardware
Study The second stage in SSADM is Structured Analysis which is the
most important part. Structured Analysis is a set of techniques and
→ graphical tools. They allow the analyst to develop a new kind of
Test plan → New
→ System system specifications that are easily understandable to the user.
5 6
Constructing the
Here the analyst uses graphic symbols, Data Flow Diagrams (DFDs)
→ → Maintenance and Data Dictionaries (DDs) to represent the system.
system and
Packaged Implementaion —————————————————————————————————
design Note :
Fig 4.1 1. The DFDs are graphic representation of data movement, process
and files (Data Store) used in support of an information system.
The structured analysis uses symbols instead of narrative descriptions
and creates a graphic model of the system. 2. The Data Dictionary contains a list of terms and their definitions
for all data items and data stores of a system.
The SSADM involves data flow diagram (DFD) method of showing
—————————————————————————————————
the movement of data through a system. The DFD’s are free of
In preparing the model, the analyst concentrates on ‘What’ occurs
unnecessary details and are therefore very useful in providing an
rather than on ‘How’ it is accomplished. Thus, the focus is on ‘logical’
overview of the system.
rather than ‘physical’ aspect of the system.
The structured analysis uses other tools like
The step 2 in figure 4.1 is exploded in a detailed manner in figure
1. Data Dictionary 2. Structured English 4.2 to explain clearly what happens in the structured analysis step.
3. Decision Trees 4. Decision Tables
** [ For Tools and Techniques refer chapters 6 to 20 ]
44 Structured Systems Analysis and Design Method SADSE 45

Budget Estimate We shall discuss the sub processes shown in figure 4.2 to understand
to user
→ the structured analysis.
Physical DFD Physical
2.1 of Current requirement Subprocess 2.1 : To study current system : Here while studying
Sustem to step 4
User
→
Study 2.5 the current system, the analyst identifies
Requirments Current → Quantify 2.6
Systems Cost and Select → 1. The external entities
Benefit the best
option 2. The list of processes performed in the current system
2.2
derive Logical 3. Sequence of these processes
→ Logical DFD of New
Equivalent Current Physical New 4. Data used for the processes

→
Physical

→
DFD system
DFD 5. How the processes are performed etc.
New
2.3 Logical Ultimately, a physical model of the existing system in the form of a
2.4
→ Develop DFD Establish DFD evolves.
Logical Mo- → Man-Machine
Survey del of new and Subprocess 2.2 : To derive logical equivalent DFD
→ Interface
System DD
Selected A physical model is a pictorial representation showing how the job is
DFD
performed physically. This includes the sequence of operations, people,
New DD 2.7 computer processing, paper forms etc. But to understand the information
Package
→ Specifi- → system properly it is necessary to know where from the data emanates?
cation How does it move ? Where does it end ? etc.
Structured
Specifications
to step 3 This requires a pictorial representation of the system that shows
what processes must be performed, the flow of the data through the
system and the data stores (files) that are required. That is a logical
Fig 4.2
DFD of the working of the current system is needed. This is what
The reader will notice clearly the progression from modeling of existing exactly the subprocess 2.2 does.
system to modeling of new system in structured analysis. The progress Subprocess 2.3 : Develop logical model of new system
is graphically shown in figure 4.3
The logical DFD obtained in 2.2 is modified on the basis of the
survey conducted and according to users requirements. This new
DFD will inform the user which requirements of his will be met. The
Define the output of this subprocess is a new logical DFD of the proposed
requirements of
new system system. The output will also include data elements, files, outputs,
→ inputs etc. i.e. a new data dictionary.
→
Logical Logical
Model of Model of Subprocess 2.4 : Establish man-machine interface
Existing New
System System The output of 2.3 is the logical DFDs and DDs for the proposed
→ →
system. But to bring this conceptual idea to the real life world, we
Physical Physical
Model of need DFDs relating physical things like people, forms, computers
Model of
Existing New and their relationships. This is done by preparing physical DFDs for
System System
proposed system in this subprocess. The activities in this subprocess
include identifying
1. How will the new system work ?
2. Processes, sequence of processes, data used for the processes etc. and
Fig 4.3 3. The interaction between manual and automated process
46 Structured Systems Analysis and Design Method SADSE 47

The output of this subprocess is the new physical DFDs which will The estimated budget for the proposed system is worked out. The
serve as the input for the sub processes 2.5. and 2.6 outputs of this subprocess are
Subprocess 2.5 : Quantify Costs and Benefits : 1. Estimated budget
Here, the various options are identified in terms of costs and benefits 2. Physical requirements and
3. DFDs for the selected option.

Costs Benefits Subprocess 2.7 Package Specifications

Now that all the conceptual thinking of the analysis phase is over,
One time cost Recurring Cost Tangible Intangible the only remaining task is to collect the products of analysis and
Benefits Benefits organize them into finished structured specifications. This process is
called “Packaging”. The final result of this is the structured specifications
which consists of an interpreted set of DFDs, DDs and process
[Link] of 1. Salary of 1. Reduction [Link] descriptions. This is done through the usage of Structured English,
converting from personnel in cost of satisfaction Decision Tables and Decision Trees.
present system to 2. Supplies operation. [Link]
proposed system. 3. Equipment 2. Increased employee Step 3 : Structured Design
[Link] or maintenance. value in morale Structured Design is a data-flow based methodology. The input for
remodeling of sales and due to structured design is structured specifications which is the output of
existing facilities. net income. better structured analysis. It also receives input from the hardware study.
[Link] cost. 3. Reduced time facilities. (Step 4)
in completing What we do in the system design process is to convert the logical
the tasks. [Link] design specifications (i.e. structured specifications) into technical design
company specifications. In short, system design involves transforming a logical
image. design into a physical design. This step is much more exacting than
[Link] designing logical design specifications. Here the important activity is
to “Software Packaging”. The Software Packaging includes
management
1. Input-output design
about
2. Files and Database design
entering
into newer 3. Program design and
information 4. Control Design
technologies Activities that run parallel to this detailed design steps of software
The life span of the new system has to be decided by taking into packaging are
consideration Net Present Value and Internal Rate of Return of the 1. Equipment specifications
future cost benefits. The output of this subprocess will be the cost 2. Test specifications and
benefit analysis report which will serve as the input for subprocess 2.6. 3. User interface specifications
Subprocess 2.6 : Select the best option In fact, these parallel activities have their roots in structured analysis
The inputs for this subprocess are cost benefit analysis report and part. Here we refine and expand their specifications to make each
physical DFD of proposed system. In this subprocess, the most important one as concrete as possible. The process 3 in figure 4.1 is exploded
activity of taking the decision of selecting the best option is carried into detailed subprocesses in fig 4.4
out. This selection outlines the hardware and software requirements.
48 Structured Systems Analysis and Design Method SADSE 49

Hardware bottom shows the details. This is essential to divide the total design
Configuration process into smaller independent modules which in turn help to have
Details
Structured flexibility in the design, i.e. any changes made in one particular
Specifications → (from step 4) module will not affect the other modules. Hence this technique provides
→ Equip-
→ ment a top-down, flexible design which is easier to maintain.
Specific-
(from step 2) Logical ation To maintain a dialogue with users during the process of system
Design design is often difficult. Wise designers make it a point to involve
Specification
→ users at several stages in the design and more particularly in the
Test earlier stages of the design itself. For this, they use a technique
Use → Specific- called Structured Walk through. A Structured Walk through is an
→

Structure ation
Chart
organized step by step tracing through of a design by a group of
→ people. The group may be peer group or users. The purpose of Walk
→ through is to find where improvement can be made in the system or
Software User
Inter face
in the development process. There are two types of Structured Walk
Packaging → →
Specifi- throughs
cation
1. A Preliminary Design Walk through
2. A Detailed Design Walk through
In addition a Pseudocode Walk through is performed just before a
→ design is coded.
Input Technical Walkthroughs are conducted
Files and Program Control Design
→
Output
Design
Database Design Design Specifi- → 1. To catch design errors in advance
Design cation
2. To improve communication and
→ 3. To fine tune a design
→
→ Step 4 : Configuring Hardware Study
→ This step considers the physical requirements of the proposed system.
It is based on the new physical DFDs, DD of Step 2.

Fig. 4.4 The System Design Process Here we should specify the details of the configuration to be used in
the implementation stage. These configuration details go as input for
equipment specification process in Step 3. The cost involved and the
The main input, structured specifications (i.e. logical design specifications) present worth of the benefits to be accrued are considered here for
is used to derive structure charts. The most difficult step in SSADM hardware specifications.
is that of converting DFDs of structured specifications into software
Step 5 : Constructing the System and Implementation
packages. To do this, we need to construct what is called Structured
charts. A Structured chart is a documentation technique. It shows The implementation process begins after the management has accepted
the hierarchy of modules and their interrelationships in a program or the new system. System implementation consists of five components
a system. 1. System Acquisition
2. Programming
While a DFD considers a sequential order of processes the structured
3. Testing
chart begins with the most important process (BOSS) and then goes
4. Conversion
on to its subordinate processes. The top level of structured chart
5. Documentation
shows the most important division of work, the lowest level at the
50 Structured Systems Analysis and Design Method SADSE 51

1. System Acquisition : It involves the purchase of hardware, packaged Step 6 : Maintenance : This is the last step in the system life cycle.
software and software services. Here the systems analyst and designer However it takes the longest duration. Maintenance may be corrective,
work together to determine the best place to make these outside adaptive or perfective. In corrective maintenance errors or bugs are
purchases. Another important part of system acquisition is the actual rectified. In the adaptive maintenance the user requirements if any
purchase of goods and services. are still considered and the necessary changes are made. In perfective
2. Programming : It is the writing of instructions to be read and maintenance efforts will be constantly going on to perfect the system
executed by a computer. Programming is performed by computer in terms of response time and resource requirements.
programmer or programmer/analyst rather than by systems analyst 4.3 Advantages of SSADM
or designers. Normally a team of programmers work under the direction Some of the important advantages of SSADM are :
of lead programmer-typically a system designer. Tasks in programming 1. Good Documentation : In the structured methodology well defined
include writing the coded instructions, testing each segment of the documentation takes place. Hence it is easy for the analysts, users
code and testing the entire computer programme once it is completed. and programmers to understand and use.
3. Testing : It consists of putting together the various coded pieces 2. Better Communication : Since structured methodology is graphic
of a design, testing them and correcting the parts of the code or the it provides easy to understand presentation of the application. The
design that are not correct. At this stage some errors are introduced DFD, for example, presents a better picture than any other comparative
purposely to test whether they will be spotted by the program. tool.
4. Conversion : Once the system has been tested successfully 3. Standardization : Before the emergence of the structured methods,
then the part which remains is that of putting them into the operation. the systems analyst used to have their own methods of designing
The conversion team must manage the smooth changeover from the computerized system. But structured methodology offers very little
old system to the new system. This requires scope for individual approach.
1. Training of personnel 4. Modularisation : The process is partitioned so that we have clear
2. Modifying parts of the old system picture of the smaller modules which is essential to understand the
system thoroughly.
3. Running parallel system or dual system until everything goes as
planned. 5. Logical Design : The SSADM is more logical than physical. The
elements of the system do not depend on vendor or hardware.
5. Documentation : Documentation means putting it in the written
6. User oriented : The SSADM consults user at every stage of development
form about how a system is designed or functions. The documentation
thereby leaving no scope for rejection after the system is implemented.
includes
7. Maintainability : The need for maintenance arises due to errors,
1. Design Documentation : It describes the overall system design
modified user requirements and enhancements. The structured methodology
and includes system flowcharts, all input/output formats, file description,
takes into account this aspect, hence maintenance becomes cheaper.
control requirements and report specifications.
2. Program Documentation : It consists of programming specifications
like program logic, graphic aids, input-output formats etc. REVIEW QUESTIONS
3. Training Documentation : It includes user training manuals and 1. State the limitations of SDLC.
materials to be used in the conversion and the installation of new 2. What is SSADM ?
system.
3. List the stages of SSADM.
4. Operations Documentation : It contains instructions for normal
4. Discuss in brief :
operations as well as directions for handling problems and breakdowns.
a) Survey in SSADM
5. User reference Documentation : It carries on after training is over b) Structured Analysis
and the system is installed. It should provide quick, clear answers
c) Hardware Study
like a dictionary.
52 Structured Systems Analysis and Design Method

5. What are the outputs of Structured Analysis ?

6. Explain the aspects to be considered in Costs and Benefits Analysis
of a system.
7. “The system design part in SSADM is converting Logical Design
Specifications in to Technical Design Specifications”. Elaborate.
8. Write a short note on :
a) Structured Walk through
b) Software Packaging.
9. Represent diagrammatically
a) Structured Analysis Process
b) Structured Design Process
10. System implementation consists of System Acquisition, Programming,
Testing, Conversion and Documentation. Elaborate.
11. Write a short note on system documentation.
12. "Though maintenance is the last stage in SSADM, it is most
costly and time consuming. Hence it needs more attention". Give
your opinion.
13. State the advantages of using structured methodology in system
development.

View publication stats