Abstract
[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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Beynon-Davies, P.: Human error and information systems failure: the case of the London ambulance service computer-aided despatch system project. Interacting with Computers 11(6), 699–720 (1999)
Charette, R.N.: Why software fails. IEEE Spectrum (September 2005) (Lists 31 failed US projects from 1992 to 2005)
Emam, K.E., Koru, A.G.: A replicated survey of IT software project failures. IEEE Software (September/October 2008)
Ewusi-Mensah, K.: Software development failures. The MIT press (2003)
Glass, R.L.: Software runaways. Prentice Hall (1998)
Jones, C.: Patterns of large software systems: failure and success. IEEE Computer (March 1995)
Keil, M., Rai, A., Mann, J.E.C., Zhang, P.: Why software projects escalate: The importance of project management constructs. IEEE Transactions on Engineering Management 50(3) (August 2003)
Lauesen, S.: Guide to Requirements SL-07 - Template with Examples (2007), www.itu.dk/people/slauesen/SorenReqs.html#SL-07 ISBN: 978-87-992344-0-0
Lauesen, S., Kuhail, M.: Task descriptions versus use cases. Requirements Engineering Journal (2011), doi:10.1007/s00766-011-0140-1
Lauesen, S.: User Interface Design - A Software Engineering Perspective. Addison-Wesley (2005)
Leveson, N.G., Turner, C.S.: An investigation of the Therac-25 accidents. IEEE Computer (July 1993)
Molich, M.: Usable Web Design. Nyt Teknisk Forlag, Denmark (2007)
Preece, J., Rogers, Y., Sharp, H.: Interaction Design – Beyond Human–Computer Interaction. John Wiley & Sons, New York (2002)
Redish, J., Molich, R., Bias, R.G., Dumas, J., Bailey, R., Spool, J.M.: Usability in Practice: Formative Usability Evaluations — Evolution and Revolution. In: CHI 2002, Minneapolis, USA, April 20-25 (2002)
Rigsrevisonen: Beretning til Statsrevisorerne om det digitale tinglysningsprojekt (in Danish) (August 2010), http://www.rigsrevisionen.dk/media(1610,1030)/14-2009.pdf
Southon, G., Sauer, C., Dampney, K.: Lessons from a Failed Information Systems Initiative: Issues for complex organisations. In: APAMI/HIC 1997, Sydney (August 1997)
Wallace, L., Keil, M.: Software project risks and their effect on outcomes. Communications of the ACM (April 2004)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2012 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Lauesen, S. (2012). Why the Electronic Land Registry Failed. In: Regnell, B., Damian, D. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2012. Lecture Notes in Computer Science, vol 7195. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-28714-5_1
Download citation
DOI: https://doi.org/10.1007/978-3-642-28714-5_1
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-28713-8
Online ISBN: 978-3-642-28714-5
eBook Packages: Computer ScienceComputer Science (R0)