📊 System Development Life Cycle (SDLC)

The system development process proceeds through six sequential stages. The flowchart
below visualises the progression and the mnemonics that help remember the order.

The diagram on the right lists each stage and connects them with arrows, illustrating the
linear flow of the SDLC. The mnemonics “ADDIDE” and “Ali's Designer Developed Ideas,
Documented Everything” reinforce the order.
Stages
1. Analysis – Gather information about the current system and pinpoint problems.
2. Design – Create a blueprint for a new system that resolves the identified
issues.
3. Development & Testing – Build the system and verify that it works as intended.
4. Implementation – Replace the old system with the newly built one.
5. Documentation – Produce technical and user manuals.
6. Evaluation – Confirm that the system meets the original design requirements.

🕵️ Data Collection Methods

Four primary techniques are used to collect information about the existing system.
Method Description Advantages Disadvantages
Observation Analyst Reliable data; holistic view; People may
watches inexpensive; sees all alter behavior;
processes inputs/outputs. may not
directly. represent a
typical day.
Interviews One‑on‑one Detailed info; ability to probe; Time‑consuming
(or small body‑language cues. costly; no
group) anonymity.
conversations
with key users.
Questionnaires Written Fast for large groups; cheap; Limited by
surveys respondents stay anonymous. question
distributed to design; low
many people. response
quality
possible.
Collecting Review Reveals data volume, types, and Very
Documents existing forms, required I/O devices. time‑consuming;
reports, relatively
manuals, log expensive.
files.

Visual examples

🔎 Analyzing the Present System

After gathering data, the analyst examines it to:
Identify Inputs, Outputs, and Processes.
Detect Problems (inefficiencies, errors, missing functionality).
Draft a Requirements Specification (user + information requirements).
Determine required Hardware and Software (e.g., number of PCs, network
type, special devices).
📋 Requirements Specification
Requirement type Audience Typical content
User Requirements Business managers Written in plain language;
(customers) describes what the system
must do from a user’s
viewpoint.
Information System designers Specifies what data is
Requirements needed and when (data
items, timing, reports).

🛠️ Design Phase
The design stage converts requirements into concrete system specifications.

1️⃣ Designing Data & File Structures

A file = collection of records (rows) and fields (columns).
One field acts as the primary key (unique identifier).
Design considerations for each field: name, length, datatype, expected record
count.
Choose appropriate storage media (disk, SSD, cloud).

2️⃣ Designing Input Formats

Data Capture Methods
Method Description
Manual Data Capture Paper forms are filled out first.
Manual Data Input Information from paper forms is typed
into the system.
Automatic Data Capture Data is captured and entered
simultaneously (e.g., barcode scanner).
The diagram shows the three capture pathways feeding into the computer system.
Paper‑Based Form Design
Clear heading indicating purpose.
Explicit spaces for answers (text boxes, character boxes, tick boxes).
Consistent layout for dates, phone numbers, etc.
Proper headings, labeled fields, and tick boxes improve data quality.
On‑Screen Form Design
Include all necessary fields with appropriate controls (textboxes, radio buttons,
checkboxes, drop‑downs).
Size controls to match expected input length.
Provide clear instructions and real‑time validation.

These controls form the building blocks of an intuitive on‑screen form.

3️⃣ Designing Data Processing (Algorithms)
Define processing steps (algorithms) that transform input data into required
outputs.
Ensure modular design so each step can be tested independently.

4️⃣ Designing System Outputs

Two major output categories:
Output type Characteristics
On‑screen reports Dynamic layouts; use colours, fonts,
charts; fit screen size.
 Printed reports Fixed layout; corporate header/footer;
page numbers; minimal empty space.

Shows a clear, colour‑coded on‑screen record with actionable buttons.

Demonstrates a well‑formatted printed report with all required fields.
Good Report Practices
On‑screen: appropriate field size, concise instructions, effective use of screen
real‑estate, consistent colours/fonts.
Printed: clear report title, corporate header/logo, footer with page
numbers/date, organized layout, no large gaps.

5️⃣ Designing Validation Routines

Validation checks ensure entered data makes sense before it is stored.

📐 Data Validation & Verification

Validation – Ensures data meets predefined criteria (e.g., date not in the future).
Verification – Confirms that entered data exactly matches the original source.

Validation Techniques
Check type Purpose Example
Presence Field not left blank. Username must be
entered.
Range Value lies within limits. Exam mark between $0
and $100.
Length Correct number of Password exactly $6$
characters. characters.
Type Correct datatype (numeric, No letters in a numeric
text, date). field.
Format Proper pattern (e.g., Date of birth format.
dd/mm/yyyy).
Lookup Value belongs to an Subject must be one of
allowed list. {Math, Science,…}.
 Check digit Final digit validates whole ISBN or barcode check
number (error‑detecting). digit.

The highlighted final digit is the check digit used to detect entry errors.
Check‑digit calculation example
1. Sum of odd‑position digits: 7 + 0 + 5 + 3 + 0 + 1 = 16
2. Multiply by $3: $16 \times 3 = 48
3. Sum of even‑position digits: 9 + 8 + 9 + 7 + 4 + 4 = 41
4. Add results: 48 + 41 = 89
5. Divide by $10: $89/10 = 8 remainder $9$
6. Check digit = 10 − 9 = 1
Verification Techniques
Technique How it works
Visual verification Analyst compares original paper/printout
with computer entry.
Double‑entry Two independent operators enter the
same data; the system flags mismatches.
🧪 Development & Testing
Testing guarantees that each component and the whole system function correctly before
deployment.

Test Plan Essentials

Test list – Every function to be examined.
Test data – Normal, extreme, and abnormal values.
Live data – Real‑world data with known outcomes for final validation.
Expected vs. actual results – Determine pass/fail.

Types of Test Data

Category Definition Example (exam marks)
Normal Typical valid input. $63, $89
Extreme Boundary values of the $0, $100
valid range.
Abnormal Invalid input that should be −1 , $101, $200
rejected.

Modular Testing Approach

Each module is built, tested, and corrected before being combined into the final program,
which is then tested again.
Key Testing Questions
Does the system start and shut down correctly?
Can data be entered, saved, and retrieved?
Are reports generated accurately?
Are appropriate error messages shown for invalid actions?

📚 Quick Reference Tables

Advantages / Disadvantages Summary
Method Advantages Disadvantages
Observation Direct, inexpensive, holistic May alter behavior; limited
view to observed periods
Interviews Rich detail, non‑verbal cues Time‑intensive, costly, no
anonymity
 Questionnaires Fast, cheap, anonymous Restricted by question
design, low response
quality
Document collection Reveals data Very time‑consuming,
volume/types, hardware costly
needs

Validation Checks Cheat‑Sheet

Check When to use
Presence Mandatory fields
Range Numeric limits (e.g., age $0–$120)
Length Fixed‑size codes (e.g., ID $10$ chars)
Type Numeric vs. alphabetic fields
Format Dates, phone numbers
Lookup Pre‑defined lists (departments, subjects)
Check digit Barcodes, ISBNs

❓ Sample Past‑Paper Questions & Answers

1. Which stage involves writing user manuals? – Documentation.
2. Which stage checks if the system meets the user’s needs? – Evaluation.
3. Interviewing staff about current problems belongs to which stage? –
Analysis.
4. Replacing an old system with a new one is which stage? – Implementation.

These notes capture the essential concepts, procedures, and visual aids needed to master
System Analysis & Design and the associated testing practices.