Usability in practice: formative usability evaluations - evolution and revolution
CHI '02 Extended Abstracts on Human Factors in Computing Systems
Interaction Design
Software Development Failures
Software project risks and their effect on outcomes
Communications of the ACM - Human-computer etiquette
User Interface Design: A Software Engineering Perspective
User Interface Design: A Software Engineering Perspective
A Replicated Survey of IT Software Project Failures
IEEE Software
Task descriptions versus use cases
Requirements Engineering - Special Issue on REFSQ 2011
Why software fails [software failure]
IEEE Spectrum
| Hi-index | 0.00 |
[Context and motivation] In 2009 Denmark got a compulsory IT system for Land Registration of ownership. It soon created a national disaster because selling houses and getting mortgages might take months, rather than a couple of days. In this period, house owners had to pay a much higher interest rate. [Question/problem] The press claimed it was yet another IT failure, but actually the IT system worked as intended. What was the real cause? [Principal ideas/results] The visible problem was overloaded staff in the Registry Office, but behind this were optimistic estimates of human performance, lack of usability, insufficient user interface requirements, unrealistic SOA requirements, immature risk analysis, and other factors. [Contribution] This paper shows details of the requirements, what went wrong, and what could have been done, e.g. early design of the user interface and giving the supplier more influence on the architecture.