Skip to the page
Year 10 · ICT · Spring 2 · The systems life cycle; presentations

Analysis and design

What this lesson covers

7.1 Analysis

Cambridge IGCSE ICT 0417 · Topic 7: The systems life cycle · Paper 1

7.2 Design

Cambridge IGCSE ICT 0417 · Topic 7: The systems life cycle · Paper 1

You will learn to

  • Describe observation, interviews, questionnaires and examining documents.
  • Choose an analysis method for a scenario and justify the choice.
  • Design a data structure with field names, field lengths and data types.
  • Design an input form that is clear and easy to fill in.

Success criteria

  • I can give an advantage and a disadvantage of each analysis method.
  • I can choose the best method for a vet's practice and say why.
  • I can design the vet's record structure and its data capture form.
The syllabus points for these sections
  • Describe observation, interviews, questionnaires and examining documents.
  • Give advantages and disadvantages of each research method.
  • Identify inputs, outputs, processing and problems of the current system.
  • Identify user requirements and information requirements.
  • Write a system specification for hardware and software.
  • Design file and data structures: field name, field length, data type, coding of data.
  • Describe range, character, length, type, format, presence and check digit validation.
  • Calculate an ISBN-13 check digit.
  • Design input formats (data capture forms) and output formats (screen and report layouts).

Key words

Say each word, then read what it means. Every one is in the glossary too.

Systems life cycle
The stages used to create a new system: analysis, design, development and testing, implementation, documentation, evaluation.
Systems analyst
The person who studies the current system and plans the new one.
Questionnaire
A set of written questions given to many people to collect their views.
System specification
A list of the hardware and software the new system needs.
Field
One item of data in a record, such as Surname.
Coding of data
Storing short codes such as M or F instead of whole words.
Validation
An automatic computer check that data is sensible and allowed.
Check digit
An extra digit calculated from the other digits, used to detect input errors.
Data capture form
A paper or on-screen form used to collect data.
Test plan
A table listing each test, its data, the expected and actual outcomes and any remedial action.
Live data
Real data from the organisation, used to test the system with known results.
Evaluation
Judging the finished system against the original requirements after it has been used.

The explanation

Read it here, or open the study page below to go one step at a time with things to try.

7.1 Analysis

What a system is and why there is a life cycle

A system is a way of doing a job: the people, the data, the steps and the equipment.

The systems life cycle is the order of stages used to build a new system. Each stage feeds the next.

The stages are: analysis, design, development and testing, implementation, documentation, evaluation.

A systems analyst is the person who studies the old system and plans the new one.

e.g.Example
A school library uses paper cards to record loans. Books go missing and nobody knows who has them. The head asks a systems analyst to build a computer system for loans.
?Why?

Working in stages means problems are found early, when they are cheap to fix. A mistake found after the system is live costs far more.

Research method 1 and 2: observation and interviews

Observation means watching people use the current system.

Interviews mean asking people questions face to face, one at a time.

Both methods help the analyst understand the current system before designing a new one.

MethodAdvantagesDisadvantages
ObservationThe analyst sees what really happens, not what people say happens. Reliable first-hand data. Fairly cheap: only the analyst's time.People may work differently because they know they are watched (the Hawthorne effect). It can take a long time. Some tasks are not seen if they happen rarely.
InterviewsQuestions can be changed during the interview to follow up answers. The analyst can see body language. People can explain problems in detail.Very time-consuming, so only a few people can be interviewed. Expensive (analyst and staff away from work). People may give answers they think the analyst wants. Not anonymous.
e.g.Example
Library example: Observation: the analyst sits at the desk for a morning and watches loans being written on cards. Interview: the analyst asks the head librarian what goes wrong most often.

Research method 3 and 4: questionnaires and examining documents

A questionnaire is a set of written questions given to many people, on paper or online.

Examining documents means reading the papers and files the current system uses: forms, invoices, reports.

Analysts usually use more than one method, so the weaknesses of one are covered by another.

MethodAdvantagesDisadvantages
QuestionnairesReach many people quickly and cheaply. Can be anonymous, so answers are more honest. People answer when it suits them. Answers are easy to analyse, especially tick boxes.Many people do not return them. Questions cannot be explained or changed. People may misunderstand a question. Tick boxes limit the answers people can give.
Examining documentsShows exactly what data the system holds and the format it uses. Helps decide inputs and outputs. Does not interrupt staff.Very time-consuming to read everything. Documents may be out of date or hard to understand. Costly, because of the analyst's time.
e.g.Example
Library example: Questionnaire: 600 students answer 8 tick-box questions online about how they borrow books. Examining documents: the analyst reads the loan cards and the overdue-letter template.
!Watch out

In exam answers, give an advantage and a disadvantage that fit the scenario. 'It is quick' alone rarely earns a mark. Say quick compared with what, for example 'quicker than interviewing 600 students one by one'.

What the analysis must find out

The analyst records the inputs (data going in), processing (what is done to the data) and outputs (results coming out) of the current system.

The analyst also lists the problems with the current system.

From this come the user requirements (what the users need the system to do) and the information requirements (what information the system must produce).

Finally the analyst writes a system specification: the hardware and software the new system needs.

ItemLibrary example
InputsStudent ID, book ISBN, date of loan
ProcessingWork out the return date, check if a book is overdue
OutputsLoan receipt, list of overdue books, reminder emails
ProblemsCards get lost, overdue books are not chased
User requirementA librarian can record a loan in under 30 seconds
Information requirementA weekly report of overdue books by tutor group
Hardware specificationPC, barcode reader, receipt printer
Software specificationDatabase software, operating system, email software
?Why?

The hardware and software choices depend on the requirements. For example, scanning book barcodes needs a barcode reader, and storing thousands of records needs enough storage.

7.2 Design

Designing the file structure

A file here means a table of records. A record is all the data about one thing. A field is one item of data in a record.

For each field the designer chooses a field name, a data type and a field length (the maximum number of characters).

Coding of data means storing short codes instead of long words, for example M or F, Y or N.

Field nameData typeField lengthExample
StudentIDText6S10432
SurnameText30García
DateOfBirthDate/Time1014/03/2011
GenderText (coded)1F
FinesOwedNumeric (currency)61.50
OverdueBoolean1Y
?Why?

Codes save storage space, are quicker to type and are easier to validate. There are only a few allowed values, so mistakes are easy to spot.

!Watch out

Phone numbers and IDs with leading zeros are stored as text, not numbers. A numeric field would drop the leading zero (0034 would become 34).

Validation: what it is and why we need it

Validation is an automatic check, done by the computer, that data entered is sensible and allowed.

It stops impossible or unreasonable data getting into the system.

Validation cannot tell if data is correct. It can only tell if it is reasonable. An age of 15 passes a range check even if the student is really 14.

CheckWhat it checksExample
Range checkThe value is between a lower and an upper limitExam mark from 0 to 100
Length checkThe number of characters is exact, or within limitsA Spanish mobile number has exactly 9 digits
Type checkThe data is the right data typeAge must be a whole number, not 'fifteen'
Character checkOnly allowed characters are usedA surname may contain letters, spaces, hyphens and apostrophes, but no digits
Format checkThe data follows a set patternStudentID is a letter then 5 digits: S10432. A date is dd/mm/yyyy
Presence checkThe field is not left emptySurname must be filled in
Check digitAn extra digit worked out from the other digits matchesThe last digit of an ISBN or a supermarket barcode
e.g.Example
Try the toy: type 19 in the Age box, which has a range check of 11 to 18. Then type 'abc' there for a type check. Leave the Surname box empty to trigger the presence check.
!Watch out

Do not mix up validation and verification. Verification checks data was copied correctly (double entry, visual check). Validation checks data is sensible.

There is something to try for this step in the IGCSE library.

The check digit, worked through

A check digit is an extra digit added to the end of a code. It is calculated from the other digits.

When the code is typed or scanned, the computer recalculates the check digit. If it does not match, there is an error.

It catches mistyped digits and transposition errors (two digits swapped, such as 45 typed as 54).

ISBN-13 (the number on books) uses weights of 1 and 3 and modulo 10. Modulo 10 means the remainder after dividing by 10.

e.g.Example
Find the check digit for the first 12 digits of an ISBN: 978030640615 Step 1: multiply digits by 1, 3, 1, 3 … in turn: 9×1=9, 7×3=21, 8×1=8, 0×3=0, 3×1=3, 0×3=0, 6×1=6, 4×3=12, 0×1=0, 6×3=18, 1×1=1, 5×3=15 Step 2: add them: 9+21+8+0+3+0+6+12+0+18+1+15 = 93 Step 3: remainder after dividing by 10: 93 MOD 10 = 3 Step 4: subtract from 10: 10 − 3 = 7 (If the remainder is 0, the check digit is 0.) Full ISBN: 978-0-306-40615-7 Spot an error: someone types 9780306406517 (1 and 5 swapped). The weighted total becomes 92 instead of 100 (counting the check digit 7 × 1). 92 is not a multiple of 10, so the computer rejects it.
?Why?

Multiplying by different weights means swapped digits give a different total. A plain sum would not catch a swap, because 1+5 and 5+1 are the same.

Input formats: data capture forms

A data capture form collects data from a person. It can be on paper or on screen.

A good form has a clear title, instructions, logical field order and enough space for each answer.

On-screen forms can use drop-down menus, radio buttons (choose one) and tick boxes (choose any). These limit what can be entered, so there are fewer errors.

Paper forms may use boxes with one character per box, so writing is easier to read or scan by OCR.

e.g.Example
Library sign-up screen: Title: 'New library member' StudentID [S_____] (format shown as a hint) Surname [__________] Year group: drop-down 7, 8, 9, 10, 11, 12, 13 Gender: radio buttons F / M Buttons: Save Clear Help
!Watch out

Exam answers about forms need specific features: 'use a drop-down for year group' earns a mark, 'make it look nice' does not.

Output formats: screen layouts and report layouts

Output formats decide how results are shown: on a screen or in a printed report.

A screen layout shows where each item appears, the fonts, the colours and any buttons.

A report layout shows the title, column headings, the order of fields, page numbers and totals.

The designer plans these early, so users can agree them before any building starts.

e.g.Example
Weekly overdue report layout: Title: Overdue books, week ending 13/11/2026 Columns: Tutor group | Surname | Book title | Days overdue Sorted by tutor group, then surname Footer: page 1 of 3, total overdue books: 47
?Why?

Showing users the layouts before building means changes are cheap. Changing a finished report later costs time and money.

Study it

Open the study page and go one step at a time.

Check yourself

One question at a time. The reason shows after each answer.

Saved on this device.