Know and understand file/data structures including field length, field name, data type, coding of data for example M for male, F for female

Published by Patrick Mutisya · 14 days ago

Cambridge IGCSE ICT 0417 – The Systems Life Cycle & Data Structures

7. The Systems Life Cycle

The systems life cycle (SLC) provides a structured approach to developing, implementing and maintaining information systems. It ensures that each stage is completed before moving to the next, reducing risk and improving quality.

Stages of the Systems Life Cycle

  1. Planning – Identify the problem or opportunity and define the scope.
  2. Analysis – Gather detailed requirements from users and document them.
  3. Design – Create logical and physical designs for data, processes and user interfaces.
  4. Development – Build or configure the system according to the design specifications.
  5. Implementation – Install, test and roll‑out the system to users.
  6. Maintenance – Provide ongoing support, updates and improvements.

Suggested diagram: A circular flowchart showing the six stages of the systems life cycle.

Objective: File/Data Structures

A file or database is organised into records, each consisting of fields. Understanding the components of a field is essential for designing efficient data storage.

Key Components of a Field

  • Field Name – A descriptive identifier (e.g., FirstName).
  • Field Length – The maximum number of characters or bytes the field can hold.
  • Data Type – The kind of data stored (e.g., Text, Integer, Decimal, Date, Boolean).
  • Coding of Data – A method of representing values with a single character or code (e.g., M for Male, F for Female).

Example: Student Record Structure

Field NameField LengthData TypeCoding / Example \cdot alue
StudentID8Alphanumeric20230001
FirstName20TextEmily
LastName25TextBrown
Gender1CharacterM / F
DateOfBirth10Date (DD/MM/YYYY)15/04/2005
EnrolYear4Integer2023
IsFullTime1BooleanY / N

Calculating Record Size

To estimate the storage required for a single record, sum the field lengths (in bytes). For character data, 1 character = 1 byte (assuming ASCII). For Unicode, use 2 bytes per character.

Example calculation (ASCII):

\$\text{Record Size} = 8 + 20 + 25 + 1 + 10 + 4 + 1 = 69\ \text{bytes}\$

Common Coding Schemes

  • Gender: M = Male, F = Female, O = Other.
  • Status: Y = Yes, N = No.
  • Payment Method: C = Cash, D = Debit, R = Credit.
  • Priority: H = High, M = Medium, L = Low.

Best Practices for Designing Field Structures

  1. Use clear, concise field names – avoid spaces; use CamelCase or underscores.
  2. Set field lengths just long enough for expected data to save space.
  3. Choose the most appropriate data type – numeric for calculations, text for free‑form input.
  4. Apply coding only when it reduces storage or simplifies processing; document the code meanings.
  5. Validate data entry against field definitions to maintain data integrity.

Understanding these concepts helps you design efficient databases and contributes to the Design and Development phases of the systems life cycle.