◇ OpenCyber Academy
Technologist · Chapter 7 · English

Chapter 7 — Data quality concepts

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 7 — Data quality concepts

Lesson map

Lesson 07 published. Map, example, EX019.

flowchart TD
  N0["Learning outcomes"]
  N1["7.1 Dimensions"]
  N2["7.2 Measures"]
  N3["7.3 Quality and use"]
  N4["7.4 Quality as a habit"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX019"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["7.1 Dimensions"]
  N2["7.2 Measures"]
  N3["7.3 Quality and use"]
  N4["7.4 Quality as a habit"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX019"]

[Learning outcomes]
    |
    v
[7.1 Dimensions]
    |
    v
[7.2 Measures]
    |
    v
[7.3 Quality and use]
    |
    v
[7.4 Quality as a habit]
    |
    v
[Worked example] --> [Exercise EX019]

Learning outcomes

You will (1) apply quality dimensions to repair data; (2) choose measures for each; (3) relate quality to uses.

7.1 Dimensions

Ms. Moreau introduces quality dimensions from Wang and Strong's research: accuracy, completeness, consistency, timeliness and validity, among others. Ravi applies them to repair jobs. Completeness means jobs have priority, dates and contractor. Validity means codes and dates follow rules. Accuracy means completion dates reflect when work actually finished. Timeliness means updates arrive soon after work. Consistency means the housing system and contractor portal agree about the same job. Ravi writes a short example of a failure for each dimension using Calder Valley's repair jobs, which helps classmates and stewards understand them quickly.

7.2 Measures

For each dimension Ravi writes a measure. Completeness is the share of jobs with all required fields. Validity is the share passing code and date rules. Consistency is the share of jobs where status matches between systems. Timeliness is the share of completions updated within one day. Accuracy is checked by sampling jobs and comparing completion dates with tenant confirmations. He records each measure with its formula so results can be reproduced. The steward reviews the formulas and agrees the targets for each measure.

7.3 Quality and use

Ravi learns that quality depends on use. For paying contractors, cost accuracy matters most. For regulator reports, completion dates and priorities matter most. For tenant communication, contact details matter most. He builds a table linking uses to the dimensions they depend on, which helps Mrs. Okonjo explain to managers why some quality problems need urgent attention while others can wait. ISO 8000-8 supports stating how each quality claim was measured. Mrs. Okonjo uses the table in her next meeting with managers, who agree to prioritise completion date accuracy for the coming quarter.

7.4 Quality as a habit

Ms. Moreau explains that quality is not a project with an end date but a habit built into daily work. Technologists support this by running checks automatically, making results visible and helping people fix causes. Ravi notes in his journal that the best quality improvements he has seen so far came from small process changes at the source, such as the call centre checking for open jobs, rather than large clean-up exercises. Ms. Moreau asks the class to collect such examples throughout the course.

Worked example

Ravi applies quality dimensions to repair jobs, writes a formula for each, links uses to the dimensions they depend on and notes that small source changes improve quality most.

Synthetic case. Measures are synthetic; Wang and Strong (1996) and ISO 8000-8:2015 are real.

Errors and limits

One quality score for all uses hides what matters for each.

Exercises

Continue studying — lesson 07 (chapter 07 of 30)

← Chapter 06 · Course chapter index · Chapter 08 →

Continue to the next authored lesson.