Web work is easier when you know which layer is responsible for what. This page shows how the four skills in this cluster connect and the order to study them.
The cluster belongs to SPM Computer Science. Begin with separating structure, presentation and behaviour, since it gives you a way to think about every fault.
What does this cluster cover?
The first skill is separating structure, presentation and behaviour. The second is planning an original assessed project. The third is testing interaction and data validation, and the fourth is documenting your work without having anyone complete it for you.
The second and fourth skills keep assessed work your own, and the first and third make your project reliable.
How does knowing the layer help find a fault?
Take a worked example: a student builds a sign-up page, and the Submit button does nothing when clicked. The student first changes the colour and size of the button, which are presentation settings, and nothing improves.
The student then asks what the button should do. That is behaviour, so the next check is whether any action is attached to the click. The missing link is found in a minute.
The fault was never about how the button looked. Naming the layer before changing anything saves time and builds a habit of reasoning, and your notes will show clear reasoning.
Who should start where?
A learner who copies working code without understanding it starts with layers. A learner who has an idea but no plan goes to planning an original assessed project.
A learner with a working draft should try testing interaction and data validation and then documenting work without completing a student’s assessed submission. See also web development without assessed project substitution, and use the cluster practice set.
When does one-to-one help?
A teacher can explain how to reason about your own design and testing, and set small original exercises for practice. See online one-to-one Computer Science tuition for how to start.