You are on page 1of 3

Structured Systems Analysis and Design Method, a set of standards developed in the early 1980s

for systems analysis and application design widely used for government computing projects in
the United Kingdom. SSADM uses a combination of text and diagrams throughout the whole life
cycle of a systemdesign, from the initial design idea to the actual physical design of the
application
• The SSADM methodology is a well-defined (structured) methodology and is quite
difficult to use. When used skillfully it can produce well-documented, accurate
information systems. It recognizes the following stages in the systems development
lifecycle.
• However, it concentrates on the analysis and design phase of the Waterfall Model of the
Systems Development lifecycle, as shown in the following diagram:

SSADM follows the waterfall life cycle model starting from the feasibility study to the physical
design stage of development. 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. The first
and foremost model developed in SSADM is the data model. It is a part of requirements
gathering and consists of well defined stages, steps and products. The techniques used in
SSADM are logical data modeling, data flow modeling and 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.
Some of the important characteristics of SSADM are:

 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
Why use SSADM?
• Within government departments (in the UK) SSADM has to be used. External contractors
producing software for the government also have to use SSADM.
• Other companies, i.e., non-government contractors and companies, use SSADM because
they expect that the use of a disciplined 'engineering' approach will eventually improve
the quality of the systems they produce.
• Many companies have been willing to incur the considerable expense of implementing
SSADM (e.g., staff training) with this expectation in mind.

Its main benefits are:


• Improvement of quality, detailed documentation of the development stages, and
reusability for similar projects that follow. But these points are not likely to be taken
into consideration in practice. This is due to the danger of over-analyzing, which can be
very time and -cost consuming.
• Delays caused by SSADM can vary in range from months to years. Especially for small or
medium-sized companies, huge delays can lead to serious financial and resource
problems. So, it is highly advisable to investigate alternative methods, such as the Rapid
Application Development (RAD) or to use an off-the-shelf product, which is much less
expensive and less time-consuming and has already been tested by various other
companies.
• Timelines: Theoretically, SSADM allows one to plan, manage and control a project well.
These points are essential to deliver the product on time.
Usability: Within SSADM special emphasis is put on the analysis of user needs. Simultaneously,
the systems model is developed and a comprehensive demand analysis is carried out. Both are
tried to see if they are well suited to each other
• Respond to changes in the business environment: As in SSADM documentation of the
project′s progress is taken very seriously, issues like business objectives and business
needs are considered while the project is being developed. This offers the possibility to
tailor the planning of the project to the actual requirements of the business.
• Effective use of skills: SSADM does not require very special skills and can easily be
taught to the staff. Normally, common modeling and diagramming tools are used.
Commercial CASE tools are also offered in order to be able to set up SSADM easily.

• Better quality: SSADM reduces the error rate of IS by defining a certain quality level in
the beginning and constantly checking the system.
• Improvement of productivity: By encouraging on-time delivery, meeting business
requirements, ensuring better quality, using human resources effectively as well as
trying to avoid bureaucracy, SSADM improves the overall productivity of the specific
project and the company.
• Cuts costs: SSADM separates the logical and the physical systems design. So the system
does not have to be implemented again with new hard -or software.

Disadvantages of SSADM
• SSADM puts special emphasis on the analysis of the system and its documentation. This
causes the danger of over-analyzing, which can be very time and cost consuming
• Due to various types of description methods, checks of consistence cannot be carried
out. Especially with large systems, the outline diagram can become very unclear,
because all relevant data flows have to be included
The Rapid Application Development (or RAD) model is based on prototyping and iterative
model with no (or less) specific planning. In general, RAD approach to software development
means putting lesser emphasis on planning tasks and more emphasis on development and
coming up with a prototype. In disparity to the waterfall model, which emphasizes meticulous
specification and planning, the RAD approach means building on continuously evolving
requirements, as more and more learnings are drawn as the development progresses.

Description: RAD puts clear focus on prototyping, which acts as an alternative to design
specifications. This means that RAD works well wherever there's a greater focus on user
interface rather than non-GUI programs. The RAD model includes agile method and spiral
model.

Why RAD?
• Small and medium-sized companies, especially, will have to bear in mind that "time is
money" because they do not have such large reserves or incomes from other parts of the
company. SSADM, as we have seen, is very time consuming, they will have to look for
alternative methods to SSADM.
• There is mainly one method that focuses especially on fast, flexible and low resources
development of IS. called Rapid Applications Development (RAD). IT uses prototyping
to involve users, so this definitely meets their requirements, and can help to develop IS
faster.
• RAD is mostly used in combination with the Dynamic Systems Development
Methodology (DSDM). Its major principles are as follows:
DSDM
• "Active user involvement is imperative.

* DSDM teams must be empowered to make decisions.


* The delivery of products is the most important factor.
* Fitness for business is the essential criterion for acceptance of deliverables.
* Iterative and incremental development is necessary to achieve an accurate business
solution.
* All changes during development are reversible.
* Requirements are base lined at a high level.
* Testing is integrated throughout the life-cycle.
* A collaborative and co-operative approach between all stakeholders is essential.”

You might also like