| 1/10 | 16 | ||||||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 13 | |||||||||||||||||||||||||
| 12 | 3 | 14 | |||||||||||||||||||||||
| 4 | 11 | ||||||||||||||||||||||||
| 5 | 15 | ||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 9 |
1. The extent to which a user is pleased or dissatisfied with a system.
2. The quality of being clear, straightforward, and uncomplicated in system design, making it easier to understand, maintain, and modify.
3. The limitations and restrictions on a system's design and implementation, such as time, budget, technology, or resources.
4. The degree to which a system can be used by people with disabilities or impairments.
5. The overall experience and satisfaction a user has while using a system.
6. The structure and organization of a system's components and their relationships, defining its properties, behavior, and interactions.
7. The uniformity and predictability in the design and behavior of a system's elements.
8. The speed and ease with which a user can learn to use a system.
9. The accuracy and completeness with which a user can achieve their goals using a system.
10. The extent to which a system is easy to use and fits the needs of the users.
11. The state of having intricate and interconnected parts or elements in system design, making it harder to understand, maintain, and modify.
12. The 'Keep It Simple, Stupid' approach in system design emphasizes simplicity and avoiding unnecessary complexity.
13. The specifications of what a system must do or qualities it must have, usually gathered from stakeholders and users.
14. The process of defining the architecture, components, and interfaces of a system to satisfy specified requirements and constraints.
15. The design and implementation of features that reduce the occurrence of user errors.
16. The visual elements and controls through which a user interacts with a system.