|
ABSTRACT
It is widely recognized that system usability requires active involvement of end-users in all phases of software development, and there is currently a broad consensus among researchers and practitioners in the field as to what constitutes a good user-centered design process. Despite this, many systems development projects still fail when it comes to addressing usability issues and appropriately involving users in the design process. We find that a project's boundary conditions are becoming increasingly important for the potential impact of user-centered design activities, and hence the success of the end result of the project. We propose and define "context of design" as a concept to embrace the socio-technical system in which user-centered design takes place. The context of design includes, but is not limited to, the internal structure of the developer and the client organizations, contractual and tender issues, software engineering tools, and stakeholder agendas and relations. We illustrate the reasoning with various cases in which user-centered design has been constrained by factors in the context of design. We recommend that user-centered-design projects give priority to an early identification of factors in the context of design that pose risks to end-product usability. By analyzing the context of design for each project, we may be able to better tailor user-centered design activities to reach the goal of building a more usable end-result.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
ISO 9241-11:1998 Ergonomic requirements for office work with visual display terminals (VDTs). Part 11 Guidance on usability.
|
| |
2
|
ISO 13407:1999 Human-centred design processes for interactive systems.
|
| |
3
|
|
| |
4
|
Bevan, N., Claridge, N., Athousaki, M., Maguire, M., et al., PRUE European Project Final Report: Guide to specifying and evaluating usability as part of a contract. 2002, http://www.usability.serco.com/prue/index.htm.
|
| |
5
|
Bevan, N. and Bogomolni, I., Incorporating user quality requirements in the software development process. Proceedings 4th International Software Quality Week Europe, Brussels, 2000: p. 1192--1204.
|
| |
6
|
ISO 18529:2000 Ergonomics of Human-System Interaction---Human-Centered Lifecycle Process Descriptions.
|
| |
7
|
|
 |
8
|
|
 |
9
|
|
 |
10
|
|
 |
11
|
Stephanie Wilson , Mathilde Bekker , Peter Johnson , Hilary Johnson, Helping and hindering user involvement — a tale of everyday design, Proceedings of the SIGCHI conference on Human factors in computing systems, p.178-185, March 22-27, 1997, Atlanta, Georgia, United States
[doi> 10.1145/258549.258699]
|
 |
12
|
Jan Gulliksen , Inger Boivie , Jenny Persson , Anders Hektor , Lena Herulf, Making a difference: a survey of the usability profession in Sweden, Proceedings of the third Nordic conference on Human-computer interaction, p.207-215, October 23-27, 2004, Tampere, Finland
[doi> 10.1145/1028014.1028046]
|
| |
13
|
Law, E. L. C., Evaluating the Downstream Utility of User Tests and Examining the Developer Effect: A Case Study. International Journal of Human-Computer Interaction. 21(2): p. 147--172.
|
 |
14
|
|
| |
15
|
Markensten, E., Mind the gap: a procurement approach to integrating user-centred design in contract development: KTH, Numerical Analysis and Computer Science.
|
 |
16
|
|
| |
17
|
|
 |
18
|
|
| |
19
|
Beck, E., P for Political: Participation is Not Enough. Scandinavian Journal of Information Systems, 2002. 14(1): p. 77--92.
|
 |
20
|
|
| |
21
|
Hope, V. and Overgaard, B., Involving health workers in the development of hospital ICT: An analysis of UCD practice (In Norwegian). 2004, Trondheim: NSEP - NTNU.
|
| |
22
|
Nygaard, K., Program Development as a Social Activity. Information Processing, 1986. 86: p. 189--198.
|
| |
23
|
Earthy, J., Usability Maturity Model: Human Centredness Scale. EC Telematics Applications Project IE. 2016.
|
| |
24
|
Reitan, R., Integrating UCD in RUP: a Case Study (in Norwegian). M.Sc thesis, NTNU, Trondheim, Norway, 2005.
|
| |
25
|
|
| |
26
|
Öhman Persson, J., The Obvious & The Essential: Interpreting Software Development & Organizational Change.
|
| |
27
|
Boivie, I., Åborg, C., Persson, J., and Löfberg, M., Why usability gets lost or usability in in-house software development. Interacting with Computers, 2003. 15(4): p. 623--639.
|
| |
28
|
Gulliksen, J., Göransson, B., Boivie, I., Blomkvist, S., et al., Key principles for user-centred systems design. Behaviour & Information Technology, 2003. 22(6): p. 397--409.
|
| |
29
|
|
| |
30
|
|
| |
31
|
|
| |
32
|
Göransson, B., Lif, M., and Gulliksen, J., Usability Design---Extending Rational Unified Process with a New Discipline. Proceedings of Design, Specification and Verification of Interactive Systems DSV-IS 2003, 2003: p. 4--6.
|
| |
33
|
Lauesen, S. and Vium, J. P., Experiences from a tender process. International Workshop on Requirements Engineering, REFSQ, 2004. 4: p. 2004.
|
| |
34
|
Skjetne, J. H., Prototypes and tender documentation, in User Involvement in e-Government Development Projects. Results from INTERACT 2005 workshop, A. Følstad, J. Krogstie, R. Oppermann, and D. Svanæs, Editors. 2005, SINTEF: Oslo.
|
| |
35
|
|
 |
36
|
|
| |
37
|
|
|