Lesson 2 of 12

Structured learning draft

Relationships with Normalisation

In Database Design & Modelling, the way a learner handles relationships shapes how Normalisation is used and evaluated. A relationship states association, optionality and cardinality. This beginner lesson focuses on a decision or output that another person can inspect.

Learning objectives

Explain relationships in the context of Database Design & Modelling.
Apply Normalisation to a bounded practical task.
Evaluate the result using explicit quality criteria.

Instructional figureNested structure

Relationships: from context to evidence

Relationships connects business rule and records to a valid data state in Database Design & Modelling.

Business rule and records

Define the purpose, intended user and Normalisation constraints.

frames

Relationships

Model cardinality before choosing foreign keys.

produces evidence for

Valid data state

Compare the observed result with a normal case, boundary case and stated limitation.

Takeaway: Relationships is credible only when the result can be traced back to its purpose, inputs and constraints. Relationships is the decision layer between the starting context and evidence that the result is fit for purpose.

A relationship states association, optionality and cardinality. For Normalisation, distinguish performing an operation from demonstrating that it suits the stated purpose. Model cardinality before choosing foreign keys. Record assumptions that could change the conclusion.

Apply relationships deliberately

State the Database Design & Modelling task and the decision it supports.
Prepare a small Normalisation case with a known input and difficult boundary.
Model cardinality before choosing foreign keys.
Compare the observed result with the expected behaviour and explain differences.
Save the evidence, limitation and next action in a review record.

relationships evidence record
Review point	Evidence
Purpose	The specific Normalisation outcome and intended user
Method	The relationships decision, input and version or context
Result	Observed output plus a checked boundary case
Limitation	What the result does not establish and the next safe action

Common mistakes

Using Normalisation before defining what relationships must achieve.
Checking only the easiest Database Design & Modelling example.
Reporting a result without its input, assumptions or limitation.

Practice activity

Apply the lesson

For Database Design & Modelling, complete a bounded Normalisation task demonstrating relationships. Keep the original input, numbered method, normal test, boundary test, observed results and a 100-word self-review naming one limitation and next improvement.

Check your understanding

In Database Design & Modelling, which evidence best supports a relationships result produced with Normalisation?

A polished Normalisation output without its input The input, expected behaviour, normal and boundary results, and a limitation A screenshot showing the tool opened A claim that the method always works

Lesson summary

For Database Design & Modelling, relationships means: A relationship states association, optionality and cardinality.
A credible Normalisation result includes a checked boundary, not only a successful example.
The next lesson builds on this relationships evidence record.

Sources and further reading

PostgreSQL TutorialPostgreSQL Global Development Group - accessed 2026-08-21
SQL LanguagePostgreSQL Global Development Group - accessed 2026-08-21

Personal study note

Your notes

Saved on this device

Notes for this lesson

0 / 12,000No saved note yet.