App Development: Unit Exam B
Analysis and maintenance, wireframes, functional and non-functional requirements, consistency and feedback, test cases, usability and evaluation.
Instructions
- Time allowed
- 25 minutes
- Total marks
- 25
- Calculator
- No calculator is permitted.
- Answer all the questions.
- The number of marks for each question is shown in brackets. Use it as a guide to how much to write.
- The clock at the top counts down from the real time allowed. When it reaches zero the paper is locked and marked, as it would be collected in the exam hall.
- Read every question to the end before answering. Where a question says tick two boxes, tick exactly two: ticking more than asked scores nothing. Type one word and number answers carefully, because they are marked exactly.
Questions
Answer every question, then finish the paper to have it marked. Marking as you go teaches you far less.
Tick one box.
- LD Analysis
Analysis finds out what the users need.
Tick one box.
- LA Bugs are fixed and updates are released after the app is in use
Maintenance keeps the app working and up to date.
- LTo plan the layout and agree it with the client or users
- LChanging a sketch is much quicker and cheaper than changing finished code
Wireframes plan where everything goes on each screen, so the layout can be agreed with the client before any building starts. Moving a box on a sketch takes seconds, while changing a finished screen in code can take hours.
| Functional requirement | Non-functional requirement | |
|---|---|---|
| The user can reset their password | ||
| Every screen loads in under 2 seconds | ||
| The app can scan a QR code | ||
| The app works on phones with small screens |
Tick one box in each row.
- LThe user can reset their password: Functional requirement
- LEvery screen loads in under 2 seconds: Non-functional requirement
- LThe app can scan a QR code: Functional requirement
- LThe app works on phones with small screens: Non-functional requirement
Functional requirements are things the app does. Non-functional requirements describe how well it does them.
Tick one box.
- LB The save button is green on one screen and red on the next
The same action should look the same everywhere.
Tick one box.
- LC Building the app in repeated cycles of design, build and test, improving it each time
Each cycle produces a better version.
| Accepted | Rejected | |
|---|---|---|
| A password of exactly 8 characters | ||
| The username left blank | ||
| An age of 150 | ||
| An age of 13 |
Tick one box in each row.
- LA password of exactly 8 characters: Accepted
- LThe username left blank: Rejected
- LAn age of 150: Rejected
- LAn age of 13: Accepted
8 characters meets the minimum and 13 is in the range. A blank username and an age of 150 break the rules.
- LLarge buttons with pictures or icons
- LSimple words and few choices, with bright colours, sounds or clear feedback
Large buttons with pictures, because young children cannot read well and need big targets to tap. Few, simple choices on each screen, with sounds or animations as feedback so they know their tap worked.
Tick two boxes.
- LA A loading spinner while a page downloads
- LD A message saying your order has been placed
- LNo marks if more than 2 boxes are ticked
Feedback tells the user what is happening or what has happened.
- LReal users are given tasks to do with the app
- LThey are watched to see where they struggle, and the design is improved
Real users are given tasks, such as booking a lesson, and watched while they try. Where they hesitate, get lost or make mistakes shows which parts of the design need improving.
| Analysis | Design | Testing | Evaluation | |
|---|---|---|---|---|
| What does the user need the app to do? | ||||
| What will each screen look like? | ||||
| Does each feature work with every type of test data? | ||||
| How well does the finished app meet the requirements? |
Tick one box in each row.
- LWhat does the user need the app to do?: Analysis
- LWhat will each screen look like?: Design
- LDoes each feature work with every type of test data?: Testing
- LHow well does the finished app meet the requirements?: Evaluation
Needs are analysis, screens are design, checking features is testing, and judging the result is evaluation.
Tick one box.
- LB Colour blind users may not see the difference
Add a symbol or text as well as the colour.
This is an original Key Stage 3 assessment. Most questions are closed, so the marking is exact, and the written answers are marked against a mark scheme in the same style as a GCSE paper, so the format is familiar long before it counts.