System Lifecycles and SSADM

A look at the software development life cycle as defined in SSADM which provides logical data modelling to identif and document the system.

By Tim TrottSoftware Engineering • February 26, 2010
System Lifecycles and SSADM

This article will look at the software development life cycle as defined in SSADM. Almost all life cycles will share the same or similar steps. Still, they may be called something slightly different and have different processes attached.

Systems Analysis is a huge topic. This tutorial only provides a brief introduction to the issues involved.

The aim of SSADM is to provide logical data modelling to identify, model and document the data requirements of the designed system. The data is split into entities and relationships. Data flow modelling documents how data moves through a system and examines processes, entities, data flow and data stores. SSADM also provides tools for entity behaviour modelling.

The SSADM life cycle is a waterfall model, i.e. one stage flows onto the next from the top to the bottom. The life cycle can also be used as an iterative loop model where the final product spawns the next phase in an ongoing system.

There are five stages to the SSADM system life cycle that follow the system from the initial idea to the completion of the system design.

SSADM System Development Life Cycle
SSADM System Development Life Cycle

Feasibility Study

The first phase of SSADM (Stage 1) is the feasibility study in which a team is formed and decides if the project is technically feasible, whether it can be financially and socially acceptable and if the client will accept the new system.

Stage 0. Feasibility Study

SSADM provides detailed instructions on the steps and stages involved.

Requirements Analysis

In this second phase, the existing system is examined in detail to determine the requirements of the new system. This phase is split into two modules.

Stage 1. Investigation of Current System

This stage involved detailed investigation and analysis involving processes and data flow. The system is modelled in various Data Flow Diagrams and Entity models.

Stage 2. Business System Options

Based on the data from the previous stage, various business and technical solutions options are analysed and evaluated, with one being selected.

Requirements Specification

3. Definition of Requirements

Using the requirements delivered in Stage 1 and working within the selected business option in Stage 2, a full logical specification is developed for what the new system must do.

Logical System Specification

Stage 4. Technical System Options

In this stage, various technical options specifying the development and implementation environments are produced, and one is selected.

Stage 5. Logical Design

This stage defines how the system processes data and describes user interactions. The specification does not say how the system will be implemented but rather describes what the system will do.

Physical Design

Stage 6 Physical Design

Physical Design consists of a single stage in which the logical and technical system specifications are used to create a physical database design and a set of program specifications.

This is only a brief introduction to the SSADM system life cycle. The subject is so vast that one could spend years studying it at university.

Related ArticlesThese articles may also be of interest to you

CommentsShare your thoughts in the comments below

My website and its content are free to use without the clutter of adverts, popups, marketing messages or anything else like that. If you enjoyed reading this article, or it helped you in some way, all I ask in return is you leave a comment below or share this page with your friends. Thank you.

There are no comments yet. Why not get the discussion started?

New comments for this post are currently closed.