Methodology

Structured Systems Analysis and Design (SSADM)

SSADM specifies exactly the flows and tasks of a development project and produces a detailed
documentation of the project. SSADM focuses on the Analysis and Design stages of the Systems
Development Life Cycle (SDLC). SSADM combines three methods, complementing each other
within a systems development cycle: Logical Data Modelling, Data Flow Modelling, Entity
Event Modelling.

What SSADM follows?

It follows waterfall lifecycle model starting from the feasibility study to the physical design stage
of development.

SSADM for small and medium-sized systems

The great advantage of smaller companies is, normally, that they are more flexible and less
bureaucratic than large companies. Although SSADM sees its long-term benefits in more
flexibility and time saving (reuse of certain methods), there are still doubts about whether this
could be a valuable method for medium sized companies.

At this point, though, one should consider that “it is the attributes of the development rather than
the company that indicate the appropriateness of SSADM”10. If a system is being developed, for
which standard methods and CASE tools can be used and it turns out that inhouse development
is much more expensive and more time consuming, SSADM is a good solution. Another solution
could be to produce cut-down versions of SSADM in order to make it suitable for another
project, which is probably smaller. So, the company could benefit from the fact that the staff is
already trained and experienced.

Proposed development methods

1. SDLC
SSADM is a waterfall model, embedded in the so-called Systems Development Lifecycle
(SDLC), similar to the model developed by Kendall & Kendall. But SSADM focuses mainly on
the feasibility, analysis and design stage of the SDLC. The specific stages of SSADM will be
described in more detail within. SSADM combines three methods complementing each other to a
systems development cycle: Logical Data Modelling, Data Flow Modelling, Entity Event
Modelling. SSADM specifies exactly the methods and techniques that have to be used during the
single stages of development, even though it does not specify which software or tool has to be
used.

2. LOGICAL DATA MODELLING

Within this process the data requirements of an IS are investigated, identified, modelled and
documented. The logical data structure (LDS) is formed. It gives information on the entities that
need to be put down and on the relationships between these entities. Logical Data Modelling is
mainly carried out in the first two stages of the SSADM development. So, for the feasibility
stage, a higher Data Flow Diagram (DFD) and an Entity Relation Diagram are normally
produced.

Data Flow Diagrams are used to describe the system in different levels of abstraction. They
model functionality and show how input transforms into output. Entity Relation Diagrams
represent objects and their relationships. They normally show the important entities and relations
but no attributes. DFDs and ERDs are going to be used several times within the different levels
of SSADM.

3. DATA FLOW MODELLING

While Data Flow Modelling focuses on IS requirements, Data Flow Modelling deals with
identifying, modelling and documenting how data flows around and within an IS. Again, a
comprehensive DFD is produced. This DFD shows the connection between various processes
within the IS. The transformation of the processes, however, are more likely to be represented in
a distinct description of processes. Furthermore, the DFD shows the data stores, which could be
directories, folders, servers and the way they are accessed. A description of the external entities
(persons or companies that do not belong to the systems but are relevant to it) should be
included, too. Finally, data flows between processes, data stores and external entities are also
represented.

Features

 One of the main features of SSADM is the intensive user involvement in the
requirements analysis stage.
 The users are made to sign off each stage as they are completed assuring that
requirements are met.
 The users are provided with clear, easily understandable documentation consisting of
various diagrammatic representations of the system.
 SSADM breaks up a development project into stages, modules, steps and tasks.

Techniques used in SSADM

 logical data modeling

 data flow modeling
 entity behavior modeling.

 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.
 Data Flow Modeling: This involves tracking the data flow in an information system. It
clearly analyzes the processes, data stores, external entities and data movement.
 Entity Behavior Modeling: This involves identifying and documenting the events
influencing each entity and the sequence in which these events happen.

Important characteristics of SSADM

 Dividing a project into small modules with well-defined objectives

 Useful during requirements specification and system design stage
  Diagrammatic representation and other useful modeling techniques
 Simple and easily understood by clients and developers
 Performing activities in a sequence

stages of SSADM

 Determining feasibility
 Investigating the current environment
 Determining business systems options
 Defining requirements
 Determining technical system options
 Creating the logical design
 Creating the physical design

Each of these stages applies certain techniques and a sequence of analysis. They include
conventions and procedures for recording and interpreting the information with the help of
diagrams and text.

THE DEVELOPMENT STAGES OF SSADM

Stage 0: Feasibility study

Investigation of economic and technical feasibility. The problems are defined and the project
identified. The best business option is chosen out of up to 5 propositions. In SSADM the
feasibility stage is not imperative.

Stage 1: Investigation of the current environment

Definition of broad requirements, investigation of current data and processing. The project is
being identified and costs calculated. This stage is especially important as any omissions will
have a bad effect on the whole project.

Stage 2: Business Systems Options

Formulation of business systems requirements. Evaluation of the implication and benefit of each
proposed option.
Stage 3: Requirement’s specification

Identification of functional and non-functional requirements in detail. Proposal of new methods

and techniques in order to describe processing and data structures. Produce a logical design of
the proposed systems.

Stage 4: Technical systems options

Definition and selection Maintenance of specific technical options, such as different methods of
implementation. and Review.

Stage 5: Logical design

May be simultaneously to stage 4. User dialogues, update processes, enquiry processes are
defined and selected.

Stage 6: Physical design

After producing a physical design, creating a function and data design, the SSADM cycle is
completed and the applications are ready for delivery.

Appropriateness of SSADM to organizational cultures and structures

The term organizational culture can be defined as “…a system of shared meaning held by
members that distinguishes the organization from other organisations.” This comprises unwritten
rules, shared values and customs within an organization. Each type of organizational culture
normally appears alongside an “ideal” type of organizational structure, in this case a
product/service-based design.

The parts of organizational culture, on which SSADM, if applied, has an effect, are control,
direction, risk tolerance, and communication patterns. Especially the extent of control, e.g., the
number of rules, regulations, and supervision, are affected by using SSADM. So, an organization
with a structured and hierarchical culture, for example role or person culture, will have less
problems adopting SSADM and getting its employees accustomed to it. Whereas organizations
with power or task cultures, which allow the single employee to take more responsibility, and
which in general tend to be less bureaucratic and more dynamic, will have difficulties alongside
the Structured Systems Analysis and Design Methodology.
 SSADM in context with the business situation
After discussing various aspects of SSADM, advantages as well as disadvantages have been
identified. And these are closely related to the stability of the business situation of the
organization. It can only profit from the advantages that SSADM provides, such as better quality
(due to the review of each stage) or meeting the requirements more exactly (due to emphasis on
the requirements analysis stage), when the following criteria are met:

First of all, the volume and the time that is at disposal must be large enough to undergo the
whole development process. Secondly, the short-term business situation is not supposed to
change drastically, because SSADM does not intend to change the specifications that were made
in advance after the review of the stage had been completed. This fact can lead to the problem
that the end result deliver does not meet the business requirements at the point of time when it is
delivered.

Considering the long-term situation, SSADM has shown that it increases the overall quality of
Information Systems within an organization. The fact that SSADM has become the imperative
development methodology for government departments and their suppliers of IS proves this fact.
However, it must be considered that SSADM was developed especially for these kinds of
companies and that government projects, in general, have enough time, money and human
resources to cope with the bureaucratic nature of SSADM.