The Structured Systems Analysis and Design Method (SSADM) is a highly structured, “waterfall” methodology developed in the 1980s for the UK government to standardise IT project management. Its timeline can be viewed through two lenses: its historical evolution as a standard and its internal execution phases.
Historical Evolution Timeline
SSADM evolved through several versions to become an “open” standard used widely in public and private sectors.
- 1980: The Central Computer and Telecommunications Agency (CCTA) evaluates various analysis and design methods.
- 1981: Consultants from Learmonth & Burchett Management Systems (LBMS) are selected to develop SSADM v1.
- 1983: SSADM is made mandatory for all new information system developments within the UK government.
- 1984–1986: Version 2 (1984) and Version 3 (1986) are released, with the latter being adopted by the National Computing Centre (NCC).
- 1990: Version 4 is launched, introducing more refined modules and stages.
- 1995: SSADM V4+ is announced, followed by the release of V4.2.
- 2000: The CCTA rebrands SSADM as “Business System Development,” repackaging it into 15 core modules with additional specialized modules.
Methodological Execution Timeline (Stages 0–6)
SSADM follows a strict linear sequence where each stage must be completed and “signed off” before the next begins.
- Stage 0: Feasibility Study – Analyzes technical, financial, and organizational feasibility to determine if the project is cost-effective.
- Stage 1: Investigation of Current Environment – Models the existing system using Data Flow Diagrams (DFDs) to understand current data and processes.
- Stage 2: Business System Options – Presents up to six different ways to build the new system, allowing users to choose the best strategic direction.
- Stage 3: Requirements Specification – A complex stage that builds a full logical specification of what the system must do, including Entity Life Histories (ELHs).
- Stage 4: Technical System Options – Evaluates hardware and software architectures to determine the best technical implementation.
- Stage 5: Logical Design – Defines user dialogues, update processes, and enquiry processes in an implementation-independent manner.
- Stage 6: Physical Design – The final stage where logical specifications are converted into real hardware and software database structures and program specifications.








