Complete Systems Life Cycle Tutorial

Complete High Scoring ICT Notes for Analysis, Design, Development & Testing, Implementation, Documentation and Evaluation

ICT Notes Exam Guide Systems Life Cycle Student Revision

📘 Topics Covered

Analysis of Current System
Observation Method
Interview Method
Questionnaires
Existing Documents
Inputs, Outputs & Processing
User Requirements
Information Requirements
Hardware & Software Selection
Design of File Structures
Validation Routines
Input & Output Formats
Testing Methods
Test Data Types
Implementation Methods
Technical Documentation
User Documentation
System Evaluation
Exam Tips

1. Analysis

Definition: Analysis means studying the current system to identify problems, collect requirements and understand how the system works before developing a new system.

Characteristics, Uses, Advantages & Disadvantages of Research Methods

1. Observation

The analyst watches users while they perform their normal work.

Characteristics	Advantages	Disadvantages
Direct watching Real environment No interruption	Accurate information Shows real problems Reliable results	Time consuming Users may change behaviour

2. Interviews

Questions are asked directly from users.

Uses	Advantages	Disadvantages
Collect detailed information Clarify user problems	Detailed responses Can ask follow-up questions	Expensive Slow for many users

3. Questionnaires

Written questions distributed to many users.

Advantages	Disadvantages
Cheap Fast for many users Easy to analyse	Low response rate Less detailed answers

4. Examination of Existing Documents

Studying forms, reports, invoices and files already used in the organization.

Advantages	Disadvantages
Accurate records Shows current data flow	May contain outdated information

High Mark Tip: In exam answers always include both advantages and disadvantages.

Record and Analyse Information About the Current System

Inputs

Data entered into the system
Examples: Student ID, Name, Product Code

Processing

Operations performed on data
Examples: Calculations, Sorting, Searching

Outputs

Information produced by the system
Examples: Reports, Receipts, Payslips

Component	Example
Input	Marks
Processing	Calculate Average
Output	Grade Report

Problems with the Current System

Slow processing
Human errors
Poor security
Duplicate data
High operational cost
Paper wastage

User Requirements

Fast processing
Better security
User friendly interface
Mobile access
Easy report generation

Information Requirements

Monthly reports
Attendance summaries
Sales reports
Student progress reports

System Specification

Suitable Hardware

Computers
Printers
Barcode scanners
Routers

Suitable Software

Operating systems
Database software
Spreadsheet software
Accounting software

Sample Question:

Why is a laser printer suitable for a school management system?

Answer: Because it produces fast and high quality printing for reports and documents.

2. Design

Definition: Design means planning how the new system will work including files, inputs, outputs and validation.

Design File/Data Structures

Field Name	Field Length	Data Type	Coding
Gender	1	Character	M / F
Age	2	Integer	-
Admission No	10	Alphanumeric	-

Validation Routines

Validation	Purpose	Example
Range Check	Checks limits	0-100 Marks
Character Check	Checks characters	Name field letters only
Length Check	Checks character count	Password = 8 chars
Type Check	Checks data type	Age must be numeric
Format Check	Checks format pattern	Email format
Presence Check	Checks empty fields	Name cannot be blank
Check Digit	Checks number validity	Barcode systems

Input Formats

Data capture forms
Simple layouts
Clear labels
Easy navigation

Output Formats

Screen layouts
Report layouts
Invoices
Summary reports

Remember: Good outputs must be accurate, clear, organized and easy to understand.

3. Development & Testing

Definition: Testing ensures the system works correctly before implementation.

Need for Testing

Find errors
Improve reliability
Ensure correct outputs
Reduce future problems

Test Designs

Testing data structures
Testing file structures
Testing input formats
Testing output formats
Testing validation routines

Test Strategies

Test each module
Test each function
Test whole system

Test Plan

Test Data	Expected Outcome	Actual Outcome	Remedial Action
25	Accepted	Accepted	No action needed
-5	Rejected	Accepted	Fix range validation

Types of Test Data

Type	Meaning	Example
Normal Data	Valid data	25
Abnormal Data	Invalid data	-5
Extreme Data	Boundary value	100

Live Data

Real world data used after successful testing
Used when system is almost complete

Exam Tip: Always explain whether the data should be accepted or rejected.

4. Implementation

Definition: Implementation means introducing the new system into operation.

Method	Characteristics	Advantages	Disadvantages
Direct Changeover	Old system replaced immediately	Fast and cheap	High risk
Parallel Running	Both systems run together	Safer method	Expensive and double work
Pilot Running	Used in one department first	Find problems early	Slow process
Phased Implementation	Implemented step by step	Lower risk	Takes longer

Sample Question:

Which implementation method has the highest risk?

Answer: Direct changeover because the old system stops immediately.

5. Documentation

Definition: Documentation provides instructions and technical information about the system.

Technical Documentation

Purpose

Helps developers maintain system
Supports future modifications
Helps debugging

Components

Purpose of the system/program
Limitations of the system
Program listing
Program language
Program flowcharts/algorithms
System flowcharts
Hardware requirements
Software requirements
File structures
List of variables
Input formats
Output formats
Sample runs/test runs
Validation routines

User Documentation

Purpose

Helps users operate system
Provides instructions
Solves user problems

Components

Purpose of the system
Limitations of the system
Hardware/software requirements
How to install software
How to run software
How to save files
How to print data
How to add records
How to delete/edit records
Input formats
Output formats
Sample runs
Error messages
Error handling
Troubleshooting guide
Helpline
Frequently Asked Questions
Glossary of terms

Remember: Technical documentation is for programmers while user documentation is for end users.

6. Evaluation

Definition: Evaluation checks whether the system successfully solved the original problem.

Evaluate the Solution

Area	Meaning
Efficiency	Checks speed, cost and accuracy
Ease of Use	Checks user friendliness
Appropriateness	Checks suitability to task

Compare with Original Requirements

Requirement	Status
Fast processing	Achieved
Mobile support	Not achieved

Limitations of the System

Internet dependency
Security risks
High maintenance cost
Limited mobile support

Necessary Improvements

Add cloud storage
Improve security
Create mobile app
Increase processing speed

Users’ Responses

Positive feedback about faster work
Some users requested better mobile support
Users liked automatic report generation

Golden Rule: Evaluation answers must include strengths, weaknesses and suggested improvements.

🔥 Final High Scoring Exam Tips

Use proper headings
Write definitions clearly
Always include examples
Use tables whenever possible
Write advantages and disadvantages
Use technical terms
Practice past papers
Write logical explanations
Answer according to command words

Most Important Secret:

Students who explain with examples, tables, advantages, disadvantages and technical terms usually score the highest marks in Systems Life Cycle questions.