Project failures and damages
- Large IT projects may be damaged in many ways, for instance large cost or schedule overruns, unsatisfied users, or disappointing business results. Sometimes the damages are so severe that the project is closed (complete failure). I have investigated several projects and identified detailed causes of damage, e.g. that project owners trusted tech hype or accepted a solution description without understanding it. I also provide suggestions on how to prevent the causes. Service-oriented architecture (SOA) is often a cause of damage. So I have included a detailed investigation of two ways to integrate systems: The ideal SOA and the shared database. Further there are detailed reports on two of the systems: The Electronic Land Registry and the health record system (EPIC). See more
Data visualization and electronic health records
Problem-oriented requirements - SL-07
Traditional IEEE 830 requirements describe what the system shall do. Problem-oriented requirements (SL-07 requirements) describe what the users want to achieve and which problems to remedy. The requirements leave it to the supplier to describe how his solution supports the users and handles the problems. The customer can assess how well this solution supports the users and use this in the supplier selection.
- Requirements template SL-07
English version 5.5 (docx, 21-11-2017)
Danish version 5.5 (docx, 21-11-2017)
- Guide to requirements SL-07
English version 5 (pdf, 21-11-2017) Danish version 5 (pdf, 21-11-2017)
The template is a problem-oriented requirements specification for a complex system, an electronic health record system. It can be used as inspiration and template for other systems. It covers functional requirements, security, usability, integration, etc. The guide booklet explains what to write and not to write, contract issues, test issues, etc. The booklet is available on-line above. You can also buy the English as well as the Danish booklet on www.amazon.com, www.amazon.de and www.amazon.co.uk.
See Danish summary
- Requirements for the Y-Foundation
Twice a year, the Y-foundation assesses around 300 applications and give grants to some of them. The process is quite complex and involves applicant, secretary, assessment board, accountant, auditor, web-editor, payments and a new web-site. They needed a system to support them. From January 2013 to March 2013, Lauesen made the analysis and wrote the requirements based on SL-07. He managed the acquisition until completion in Sept 2014. The requirements, the supplier's proposal, and other project documents are available (anonymized): See more
The experiences are published in Lauesen, Soren: Problem-Oriented Requirements in Practice - a Case Study. In: E. Kamsties et al. (Eds.): REFSQ 2018, LNCS 10753, pp. 3–19, 2018, Springer, https://doi.org/10.1007/978-3-319-77243-1_1.
- Use case experiment - hotline system (updated 11-01-2012)
In 2009 we conducted an experiment where several professionals and researchers specified requirements for a hotline support system. We got eight replies based on traditional use cases and seven based on SL-07's task descriptions. It turned out that use cases couldn't cover the customer's needs in areas where improvement was important but difficult. Tasks didn't have these problems and were better in other ways too. See more
- Book: Software requirements - styles and techniques (Book 2002, 600 pages)
This book explains how to write requirements that ensure that the customer gets what he needs - while giving the supplier space for building on what he has already. See more
- CMS requirements - template with examples (2007, 80 pages)
This document is a Master's thesis written by Miriam Tang and Jan Keller Pedersen. It is based on SL-07 (above) and shows exemplary requirements for acquisition of a CMS (Contents Management System). See more
- Requirements papers See more
- Book: User interface design - a software engineering perspective (Updated 02-03-2009, book 2005, 604 pages)
This book bridges the gap between software engineering and human-computer interaction. It introduces the Virtual Windows method where the data presentation screens are designed first, the dialog next. The book shows the full design process for three systems, including the initial requirements work.
- Design guide for PDA and Smartphone (2006, 64 pages, in Danish)
This guide is a Master's thesis written by Julie Krogh. It shows how to support complex tasks on PDA and Smartphone. The user interfaces are efficient to use, yet elegant. The Virtual Windows method was a key part of the solution.
Download (pdf)See more (in Danish)
- User interface for maternity benefits (2008, 92 pages, in Danish)
This user interface was designed by Britt Morelli Hansen as a Master's thesis. Due to legislation, maternity leave is amazingly complex. The user interface deals with all the complexities, is efficient to use, yet elegant. The Virtual Windows method was a key part of the solution.See more (in Danish)
- User interface papers See more
- Microsoft-Access Tutorial (July 2011, 154 pages)
This free book covers Access databases with advanced user interfaces and Visual Basic.
A health record
Guide to SL-07
User interface design
Design guide for PDA and Smartphone