Topic module

Website Analysis

Identify end users and functional requirements for a web-design and development problem.

Long-form learning
Concept to Risk to Memory to Check-up

How to study Higher Computing Science

Move from requirements to structured designs, trace code and data precisely, and support every test or evaluation judgement with observable evidence.

Core concepts

Concept 1

End-user analysis considers who will access the website, their goals and relevant device or interaction needs.

Exam cue: Name the intended user and the task they need to complete.

Concept 2

Functional requirements state what navigation, content, media, forms and interactions the website must provide.

Exam cue: Write a requirement as observable website behaviour.

Concept 3

Requirements should be testable and traceable into structure, wireframes, HTML, CSS and JavaScript.

Exam cue: Keep visual preferences separate from required functionality unless the scenario makes them essential.

Risk pitfalls and guardrails

Naming the client organisation rather than the actual end user.

Guardrail: Check route, scope, data type, boundary, loop condition, identifier and expected output before committing to the response.

Calling attractive appearance a complete functional requirement.

Guardrail: Check route, scope, data type, boundary, loop condition, identifier and expected output before committing to the response.

Choosing implementation tags before defining the required behaviour.

Guardrail: Check route, scope, data type, boundary, loop condition, identifier and expected output before committing to the response.

Memory anchors

Website end user

The person or audience that navigates, reads, enters data or interacts with the site.

Website functional requirement

A testable behaviour such as navigating, displaying media, validating data or responding to an event.

Content requirement

The text, graphics, audio or video information the site must present.

Interaction requirement

The response required when a user submits, selects, clicks or points.

Device context

User devices can affect layout, input and media requirements.

Traceability

Every requirement should connect to a design, implementation feature and test.

Checkpoint rule

Do the check-up only after you can summarize each concept in one sentence and identify one dangerous pitfall from memory.

Knowledge Check (after reading)

Short check-up to confirm understanding of this module.

Check-up Questions

1-2 question checkpoint

A community theatre requests a website. Which statement is an end-user requirement?

Which question best identifies a site's purpose?

Answer all questions to submit.

Next step personalized recommendations

What is Pass Harbor?

Completely free exam prep for 247 UK exams.

  • Practice questions
  • Flashcards
  • Study guides
  • Mock exams
  • No registration
  • No paywall
  • Start instantly
No more expensive exam prep. Quality study tools should be accessible to everyone.