If you own a bike (e.g. a mountain bike), it needs to be maintained regularly to keep it running smoothly. Remembering what tasks need to be completed and when can be tricky, meaning that tasks get forgotten.
There is a need for a simple system that allows tasks to be be noted down and then for the user to be reminded of them.
The typical end-user would be a bike owner who wants to do their own bike maintenance. They will be knowledgeable about bikes. However, they won’t necessarily be technically skilled. This means that the system will need to cater for people with a range of IT skills - the system must be intuitive to use.
A system that allows someone to track maintenance jobs for their bikes.
A functional system is one that works as intended. All of the expected features work, data displayed is accurate and no unexpected behaviour is shown.
It is important that this system is fully functional otherwise the users will end up missing key bike maintenance tasks. If this happens, the user will lose faith with the system and will stop using it.
I will need to ensure that each part of the system works as expected. This can be down by thoroughly testing the system with a range of different input data, and a range of scenarios. For example, I can add a range of tasks with different data: some one-off tasks, some repeating tasks; then check that they are shown correctly, check they can be marked as done, check that repeating tasks re-occur, etc.
A system is usable if it is intuitive to use.
It is important that this system is usable so that blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah.
As I design this system I will keep in mind Neilssen’s Usability Heuristics. I will ensure that blah blah blah blah blah blah blah blah blah blah blah blah blah blah.
When I am testing the system and/or getting end-user feedback, I will blah blah blah blah blah blah blah blah blah blah blah blah.
Complete for other implications
Replace this text with a clear explanation of what the principle means.
Replace this text with an explanation of why the principle is relevant to this particular project.
Replace this text with an explanation of what you will need to consider moving forward and how the project will be impacted by this principle.
Replace this text with a clear explanation of what the principle means.
Replace this text with an explanation of why the principle is relevant to this particular project.
Replace this text with an explanation of what you will need to consider moving forward and how the project will be impacted by this principle.
Replace this text with a clear explanation of what the principle means.
Replace this text with an explanation of why the principle is relevant to this particular project.
Replace this text with an explanation of what you will need to consider moving forward and how the project will be impacted by this principle.