user centred design | can be accomplished if developers follow certain guidelines including: | |
can ensure that unnecessary features and functions are not added to the software | |
can improve the quality of software | |
can improve the system's efficiency of use | |
can make the system more attractive so users may be more willing to buy and use it | |
can reduce costs associated with changing the system later | |
can reduce costs by only developing features that are needed | |
can reduce the cost to produce, operate and maintain software | |
can reduce the time needed to learn the system | |
can reduce training and support costs | |
has definition An approach to software engineering using techniques that focus on users and their needs | |
helps developers prioritize their work so that the most important features reach the users sooner | |
is a subtopic of 7.1 - User Centred Design | |
is abbreviated as UCD | |
is a kind of design | |
requires developers to understand users | |
design | determines how components will be implemented in a system | |
has goals - Increasing profit by reducing cost and increasing revenue
- Ensuring that we actually conform with the requirements, thus solving the customers' problems
- Accelerating development, which helps reduce short-term costs, and may also ensure the software reaches the market soon enough to effectively compete
- Increasing qualities such as usability, efficiency, reliability, maintainability, and reusability which can help reduce costs and also increase revenues
| |
has part detailed design | |
has part modelling | |
has part programming | |
has part software architecture^2 | |
has part systems engineering | |
has part user interface design | |
see also design^2 | |