TK Study

Software Engineering › Key terms › Y12 Secure Software Architecture › Authorisation

Authorisation

Term Key terms bank Y12 Secure Software Architecture

Definition

Deciding what an authenticated user is allowed to access or do (roles and permissions).

Example: A student can view marks but only a teacher can edit them.

Found in: syllabus, sample exam and familiarisation guidelines, school notes.

Short version to memorise (key terms bank)

Deciding what you may do.

Where it is used in the test

Syllabus area: Y12 Secure Software Architecture.

Question types it can appear in

Where it has appeared in the paper

Secure Software Architecture (Part A, B). Part letters follow each paper’s own layout.

Related past questions

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Deciding what an authenticated user is allowed to access or do (roles and permissions).” Then apply it: A student can view marks but only a teacher can edit them.

In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.

Command words used with it

From the linked past questions
  • Explain: Relate cause and effect; make the relationship between things evident; provide why and/or how. (Sample exam Q19 (4 marks): Authentication and authorisation)

Technique for the question types

Worked answers from the marking guidelines

Sample exam Q19 (4 marks): Authentication and authorisation (4 marks): criteria and sample answer

Criteria

4: Explains how authentication AND authorisation could be applied. 3: Explains how authentication OR authorisation could be applied, OR outlines how both could be applied. 2: Outlines some features of authentication and/or authorisation. 1: Some relevant information.

Sample answer

Authentication ensures that only staff and students with valid usernames and passwords, which should be encrypted in storage (eg using hashing), can access the app. Authorisation controls access to specific features of the app based on user roles or groups. Teachers may have permissions to upload, assign and track homework, while students can only download tasks and upload completed work. By organising users into specific roles or groups, the app restricts access to appropriate functionality, ensuring that each user can only perform actions relevant to their role or group.

Open the question page

Common mistakes

General advice
  • Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
  • Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.

Same group in the syllabus: Confidentiality · Integrity · Availability · Authentication · Accountability · Privacy · Regulatory compliance

← AuthenticationIn Y12 Secure Software ArchitectureAvailability →