Task 1: Minor A1 - UX/UI Brief and Prototype (Student Package)
Assessment details
- Subject: Year 10 Digital Technologies
- Assessment type: Design investigation and prototype
- Weighting: 15%
- Raw mark total: 50 marks
- Timing: Term 1, Weeks 4-9
- Final checkpoint: Term 1 Week 9
- Major project connection: This task creates the design-thinking evidence that will support the Simpsons House project.
Purpose
This task assesses your ability to identify a real user or stakeholder need, develop a design brief, create a UX/UI prototype, and evaluate your design decisions using criteria and feedback.
A strong submission does not only look polished. It explains the problem, shows evidence of user needs, and proves that your interface decisions are linked to functionality, accessibility, usability and aesthetics.
Task scenario
You are preparing the design foundation for a digital solution. Your teacher will provide or approve the broad project context. You must identify who the user or stakeholder is, what they need, what constraints apply, and what a successful interface should achieve.
Your prototype may be low-fidelity or mid-fidelity, but it must be clear enough for someone else to understand the user flow and give feedback.
Required submission components
Submit one organised evidence package that includes:
- User or stakeholder needs summary
- who the user/stakeholder is
- what problem or need you identified
- what evidence you collected
- what the evidence tells you
- Design brief
- problem statement
- intended users
- constraints
- success criteria
- initial solution direction
- UX flow and wireframes
- key screens or steps
- how the user moves through the interface
- annotations explaining important decisions
- UI prototype
- low-fidelity or mid-fidelity prototype
- consistent layout and visual hierarchy
- labels, navigation and interface elements that can be tested
- Evaluation and reflection
- feedback collected from at least one other person
- evaluation against success criteria
- changes made or improvements planned
Conditions and authentication
- Most work should be completed in class, with teacher checkpoints recorded during the process.
- Your teacher may ask you to explain your design choices in a short validation conversation.
- You may use class templates, Figma, paper sketches, teacher examples and approved resources.
- All submitted work must be your own. If you use external icons, images or interface inspiration, acknowledge the source.
Checkpoints
| Checkpoint | Evidence required | Why it matters |
|---|---|---|
| Checkpoint 1: Need identified | user/stakeholder, problem statement, evidence source | proves your project is based on a real need |
| Checkpoint 2: Brief drafted | constraints and success criteria | shows what your design will be judged against |
| Checkpoint 3: Wireframes | screen flow and annotated sketches | shows planning before polish |
| Checkpoint 4: Prototype | working or walk-through prototype | makes the design testable |
| Checkpoint 5: Evaluation | feedback, criteria check and reflection | shows iteration and learning |
Technical and design requirements
Your prototype and documentation must show:
- a clear user journey or screen sequence
- labels, buttons or navigation that make sense to the user
- layout choices that support readability and usability
- consideration of accessibility, such as contrast, text size and clear wording
- success criteria that can be checked by someone else
- evidence of iteration after feedback
Suggested evidence format
You may submit a single document or portfolio page containing:
| Section | Suggested content |
|---|---|
| 1. Problem and user | user/stakeholder, need, evidence summary |
| 2. Design brief | problem, constraints, success criteria |
| 3. UX planning | user flow, wireframes, annotations |
| 4. Prototype | screenshots or Figma/prototype link |
| 5. Evaluation | feedback, criteria table, reflection |
Academic integrity
You may use examples for inspiration, but the final brief, prototype and evaluation must represent your own thinking. Do not submit copied interface layouts without explaining and adapting them for your user need.
Command terms
- Identify: recognise and name the need, user or problem.
- Explain: make your reasoning clear using evidence.
- Design: create a planned solution that responds to criteria.
- Evaluate: judge the design against criteria and feedback.
- Justify: give reasons for a decision using evidence or constraints.
Curriculum links
- ID10-1 (WA10DIGDTID1): Ideate a problem and define client or stakeholder needs using evidence.
- ID10-2 (WA10DIGDTID2): Develop a design brief for a solution or innovation.
- ID10-3 (WA10DIGDTID3): Investigate technologies, resources and constraints.
- DI10-1 (WA10DIGDI1): Define and decompose real-world problems using data gathering techniques.
- DI10-2 (WA10DIGDI2): Design and prototype UX/UI based on client needs.
- DSN10-1 (WA10DIGDTDE1): Design alternatives considering functionality, accessibility, usability and aesthetics.
- EV10-1 (WA10DIGDTEV1): Evaluate design processes and solutions against criteria.
- PM10-1 (WA10DIGDTPM1): Manage project work using an organised process.
Marking summary
| Criterion | Marks |
|---|---|
| User needs and evidence gathering | 10 |
| Design brief, constraints and success criteria | 10 |
| UX flow and wireframes | 10 |
| UI prototype quality | 10 |
| Evaluation, documentation and communication | 10 |
| Total | 50 |
Grade guidance
| Raw mark out of 50 | Percentage | Indicative grade |
|---|---|---|
| 37.5-50 | 75.00-100.00% | A |
| 32.5-37 | 65.00-74.99% | B |
| 25-32 | 50.00-64.99% | C |
| 17.5-24.5 | 35.00-49.99% | D |
| 0.5-17 | 0.01-34.99% | E |
| 0 | 0.00% | NA |
Weighted mark conversion
This minor assessment is worth 15% of the course mark.
| Raw mark | Weighted mark |
|---|---|
| 50 | 15.0 |
| 45 | 13.5 |
| 40 | 12.0 |
| 35 | 10.5 |
| 30 | 9.0 |
| 25 | 7.5 |
| 20 | 6.0 |
| 15 | 4.5 |
| 10 | 3.0 |
| 5 | 1.5 |
| 0 | 0.0 |
Submission checklist
- I clearly identified the user/stakeholder and need.
- I included evidence from an interview, survey, observation or approved class activity.
- I wrote a design brief with constraints and success criteria.
- I included a user flow and wireframes.
- I included a prototype or clear prototype screenshots.
- I evaluated the prototype using criteria and feedback.
- I acknowledged any external assets or inspiration.
- My final package is organised and ready for marking.