Updated 2023-01-31: New:
The mini-course in user interface design had wrong links to the slide show. Now corrected: Mini-course.
Soren has changed mail address to: email@example.com
Several pdf-files had strange meta-data, making some pdf-viewers show strange document names. Now corrected.
The section on the User story experiment has been improved.
The report on project failures and cures is available here: Download latest report (pdf)   Download latest overview of failure data (xlsx)   And in Danish: Seneste oversigt (på dansk) (xlsx)
Søren Lauesen, professor emeritus
Phone +45 3956 1748
Mobile +45 2963 6248
IT University of Copenhagen
Rued Langgaards Vej 7
DK-2300 Copenhagen S
Phone, main: +45 7218 5000
About SorenProject CV (pdf) CV and interests Publication list The full report (pdf). The short version published in IEEE Access, 2020: Soren Lauesen: IT Project Failures, Causes and Cures (pdf).
Related data: Overview of failure data (xlsx), and in Danish: Oversigt (på dansk) (xlsx)
Y-Foundation requirements CMS requirements Use cases vs. SL-07 tasks Textbook and papers
In cooperation with Mohammad Kuhail, I compared 8 requirements specifications written by 8 professional analysts for the same real-life project: A support system for a hotline. The analysts had got an analysis report mentioning 30 functional issues the customer wanted the system to deal with. They could use user stories and whatever else they found needed. They could ask us questions, as they could do in a real project, but nobody did.
In their replies, they used user stories and epics only. We asked the analysts whether they covered all requirements and to our surprise, they all said "yes". However, on average, their specifications covered only 10 of the 30 functional issues the customer had stated (ranging between 5 and 13 issues). Further, user stories hardly mentioned any of the non-functional requirements needed too, such as usability, data migration and phasing out. Many user stories were wrong: they specified something the customer definitely didn't want. See moreMini-course in the method Some great user interfaces Microsoft Access tutorial Other UX papers Visualization papers The early national EHR strategy Graphical and customizable EHR Anonymizing an EHR Troubles with the EPIC acquisition Time study of EPIC in the clinic
One of my interests