Complete System Development Methodologies Tutorial

High Scoring ICT Notes for Waterfall, Spiral, Agile, Prototype & RAD Methodologies

ICT Notes Methodologies Exam Revision High Scoring Guide

📘 Topics Covered

System Development Methodologies
Common Development Stages
Waterfall Model
Spiral Model
Agile Methodology
Prototype Model
RAD Methodology
Advantages & Disadvantages
Examples of Suitable Systems
Comparison Tables
Exam Questions & Answers
High Scoring Tips

What is a System Development Methodology?

A system development methodology is a structured approach used to plan, design, develop, test and implement an information system.

Why Methodologies are Important

Better project planning
Improves software quality
Reduces risks and errors
Helps teamwork and communication
Makes development organized
Faster system development

Exam Tip: Always start answers with a clear definition before explaining stages or advantages.

Common Stages in System Development

Stage	Purpose
Analysis	Identify user requirements
Design	Plan the structure of the system
Development	Create and code the system
Testing	Find and fix errors
Implementation	Introduce the new system
Maintenance	Update and improve the system

1. Waterfall Model

The Waterfall model is a linear and sequential methodology where each stage must be completed before moving to the next stage.

Stages of Waterfall Model

Requirements Analysis
System Design
Development/Coding
Testing
Implementation
Maintenance

Characteristics of Waterfall Model

Sequential process
Fixed stages
Documentation focused
Easy to understand

Advantages of Waterfall Model

Simple and easy to manage
Clear structure
Easy documentation
Suitable for small projects
Easy progress tracking

Disadvantages of Waterfall Model

Difficult to change requirements
Errors found late
Slow development process
Not flexible

Suitable Systems

Payroll systems
School management systems
Banking systems with fixed requirements

Example

A school attendance system where all requirements are clearly known before development begins.

Sample Question:

State one advantage and one disadvantage of the Waterfall model.

Answer:

Advantage: Easy to manage because stages are clearly defined.

Disadvantage: Changes are difficult after development starts.

2. Spiral Model

The Spiral model combines iterative development with risk analysis. Development happens in repeated cycles called spirals.

Stages of Spiral Model

Planning
Risk Analysis
Engineering/Development
Evaluation

Characteristics of Spiral Model

Risk focused
Iterative process
Continuous improvement
Flexible design

Advantages of Spiral Model

Good risk management
Flexible for requirement changes
Suitable for large projects
Continuous customer feedback

Disadvantages of Spiral Model

Expensive development
Complex management
Requires expert developers

Suitable Systems

Military systems
Airline reservation systems
Large banking software
High-risk projects

Example

An online banking system requiring strong security and continuous risk analysis.

How Spiral Model Works

Small part of system developed
Risks identified and solved
Customer evaluates system
Next cycle begins

3. Agile Methodology

Agile is a flexible methodology where systems are developed in small parts called iterations or sprints.

Stages of Agile

Planning
Development
Testing
Review
Release

Characteristics of Agile

Fast development
Team collaboration
Continuous testing
Customer involvement
Flexible changes

Advantages of Agile

Quick delivery
Easy requirement changes
Frequent feedback
Better customer satisfaction
Early problem detection

Disadvantages of Agile

Difficult documentation
Requires skilled teams
Hard to estimate cost and time

Suitable Systems

Mobile apps
E-commerce websites
Modern software projects
Startup applications

Example

Developing a food delivery mobile application with frequent updates and improvements.

Agile	Waterfall
Flexible	Rigid
Continuous changes allowed	Changes difficult
Fast delivery	Slower delivery
Iterative	Sequential

Sample Question:

Why is Agile suitable for mobile app development?

Answer:
Because requirements frequently change and updates can be released quickly.

4. Prototype Model

The Prototype model creates an early sample or mock-up of the system before final development.

Stages of Prototype Model

Gather requirements
Create prototype
User evaluation
Modify prototype
Develop final system

Characteristics of Prototype Model

Early working model
User feedback focused
Repeated improvements

Advantages of Prototype Model

Better understanding of requirements
Early error detection
Increased user involvement
Improves user satisfaction

Disadvantages of Prototype Model

Time consuming
Expensive modifications
Users may think prototype is final system

Suitable Systems

User interface systems
Mobile applications
Online shopping websites
Systems with unclear requirements

Example

Developing a hospital management system where users first test sample screens before final development.

How Prototype Model Works

Build sample system
Users test it
Feedback collected
System improved repeatedly

5. RAD (Rapid Application Development)

RAD is a methodology focused on very fast system development using reusable components and rapid prototyping.

Stages of RAD

Requirements Planning
User Design
Construction
Cutover/Implementation

Characteristics of RAD

Fast development
User involvement
Reusable components
Rapid prototyping

Advantages of RAD

Faster development
Reduced development time
High user involvement
Easier modifications

Disadvantages of RAD

Requires skilled developers
Expensive tools
Not suitable for very large systems

Suitable Systems

Small and medium business systems
Online booking systems
Web applications

Example

Developing a hotel reservation system quickly using reusable software components.

Comparison of Methodologies

Methodology	Main Feature	Best For
Waterfall	Sequential process	Fixed requirement systems
Spiral	Risk analysis	Large high-risk systems
Agile	Flexible iterations	Apps & modern software
Prototype	Sample system	Unclear requirements
RAD	Fast development	Small-medium projects

Choosing the Correct Methodology

Waterfall

Requirements are fixed
Few changes expected

Spiral

Project is risky
Security is important

Agile

Frequent changes expected
Fast updates required

Prototype

Users are unsure about requirements

RAD

Fast development needed

Common Exam Questions & Answers

Question: Compare Agile and Waterfall.

Agile	Waterfall
Flexible	Sequential
Frequent testing	Testing after development
Continuous customer feedback	Limited customer involvement

Question: Which methodology is best for high-risk systems?

Answer: Spiral model because it focuses on risk analysis.

Question: Why is Prototype methodology useful?

Answer: It helps users understand and evaluate the system before final development.

🔥 Final High Scoring Exam Tips

Always write definitions first
Mention stages clearly in order
Include advantages and disadvantages
Give suitable system examples
Use comparison tables
Mention real-world applications
Use technical keywords

Important Keywords

Iteration
Prototype
Risk analysis
Sequential
Flexibility
Sprint
User feedback
Rapid development
Maintenance
Requirement analysis

Common Student Mistakes:

Forgetting disadvantages
Missing stages
No real-world examples
Mixing Agile and RAD concepts

Golden Rule: Students who explain methodologies using stages, characteristics, advantages, disadvantages, examples and suitable systems usually score the highest marks in ICT exams.