Engineering, Computing and Technology Library | Design, Models and Useful Systems

EDUKATESINGAPORE · SUBJECT READING ROOM

Start with the problem a system must solve. This reading room connects scientific understanding, mathematical models, computing, data and design. It helps you move from a need to a testable requirement, examine a proposed solution and decide what evidence would count as success.

Before you begin: Be ready to name a user, a task and a constraint. A familiar everyday problem is enough for the first exercise.

Choose the part of the system

Study the complete case

Library Catalogue Requirements and Acceptance Tests: A Worked Guide

Turn reader needs into catalogue requirements using six fictional records, exact acceptance cases, traceability and changed-condition exercises.

Turn a wish into a requirement

“Make it better” leaves the task undefined. A useful requirement identifies an observable result, the conditions under which it matters and an acceptance method. Separate a requirement from a favourite implementation: a reader needs to find a book, but a particular search box is only one possible way to help.

StageIllustrative library example
NeedA reader wants to locate a title in a small catalogue.
RequirementFor a stated set of titles and spelling variants, the catalogue should return the intended record.
Design optionNormalise spacing and keep an explicit table of approved title variants.
VerificationRun the stated cases and examine incorrect or missing results.
User evaluationObserve whether readers can complete the task in realistic conditions.

Passing the predefined cases supports a bounded result. It does not establish that every future query will work or that readers understand the interface. Technical correctness and practical usefulness require related but different checks.

Models, boundaries and failure

Every model leaves something out. Write down its assumptions and expected operating conditions. A classroom model can help explain a mechanism while remaining unsuitable for a real structure or a consequential decision.

When a result fails, ask where the mismatch begins: the need, the measurement, the model, the data, the implementation or the conditions of use. Change one relevant factor where possible and retain what the failed attempt taught you. Use Learning Manuals to follow materials and mechanisms through concrete examples.

Try a design inquiry

  1. Choose a small information task, such as finding a book or organising a reading list. Name the user and the difficulty.
  2. Write two requirements and compare two possible designs against them.
  3. List ordinary cases, an edge case and a failure case. Explain how each would be checked.

Transfer check: change a condition, such as the number of records or the reader’s access needs. Revisit the requirements before claiming the original design still fits. A successful demonstration is a starting point for evidence, not a guarantee of performance at a new scale.

Continue into delivery

Read Project Management for planning and controlled delivery, Teamwork for coordination, and Research Methods and Source Evaluation for choosing evidence that can answer a design question. Keep the scientific mechanism, the software implementation and the project decision distinguishable as you move between them.

Continue through the library

Return to World Knowledge Research Library to choose another subject, or use the eduKateSingapore Hub for school learning, science, vocabulary and study support.

Collection note: This reading room brings together currently published introductions and selected reading routes. The linked articles provide the detailed explanations; the collection is developing and is not an exhaustive survey of the subject.

Explore the connected learning guides

Choose the question that brought you here. Open one useful guide, try a small task, and stop when you have what you need.

Take one question further

The same learning habit can travel across subjects, while each subject keeps its own methods. These routes help you notice a difficulty, understand one part of it, and return to something you can do.

A word is familiar, but using it is difficult.

Move from recognising a word to retrieving it in a new context. Understand vocabulary plateaus.

Try it without the guide: Choose one word you already know. Close the guide and use it in a new sentence. Explain why it fits; try another context tomorrow.

A piece of writing has ideas, but the reader loses the thread.

Make the order of events and the links between sentences clear. Explore composition writing.

Try it without the guide: Choose one short paragraph. Read the relevant explanation, close it, and revise the paragraph. Ask someone to tell you what happened and why.

The Mathematics seems familiar, but marks still disappear.

Find the first point where the working stops being reliable. Find Secondary 4 A-Math mark leakage.

Try it without the guide: For a Secondary 4 A-Math question you have attempted, locate the first uncertain line. Repair that step, then try a comparable question without the worked answer.

A Science fact is remembered, but the explanation is incomplete.

Connect the evidence to a scientific idea and the resulting change. Follow the Primary Science learning route.

Try it without the guide: Choose a familiar Primary Science example. Explain the evidence, the idea and the result without notes. Then change one condition and explain your prediction.

Two accounts of the world seem to disagree.

Check the question, source, date and evidence before combining claims. Explore the World Knowledge research library.

Try it without the guide: Take one claim. Find the source best placed to support it, note its date, and state what remains uncertain. Return to your original question.

There is plenty of help, but independence is hard to see.

Check what the learner can understand and do after support is removed. Understand how education works.

Try it without the guide: Choose one small task the child has practised. Agree on a calm, brief attempt without prompts. Use what happens to choose one next step, then stop.

For the structure behind these connections, read the eduKateSingapore runtime manifest and the eduKate ecosystem boot contract. The reader map describes public navigation; those manifests preserve the wider ownership and return rules.