Project CV (pdf)
CV and interests
Large IT projects may be damaged in many ways, for instance large cost or schedule overruns,
unsatisfied users, or disappointing business results. I have investigated several large projects
and identified 37 damage causes and 22 cures.
The electronic land registry
Electronic health record - EPIC
Traditional requirements describe what the system shall do. Problem-oriented requirements (SL-07 requirements) describe what the system is to be used for. They cover all kinds of requirememts, are five times shorter, five times faster to write, and five times faster to reply to.
Use cases vs. SL-07 tasks
Textbook and papers
Requirements are often appendices to long contracts. IT-people don't read the contract and lawyers don't read the requirements. It need not be so. SL-07 requirements have an 8 page contract with 4 appendices. Together they cover what traditional 50 page contracts with 16 appendices do.
There is a big gap between UX specialists and software developers. UX specialists are good at identifying user needs and testing whether usability of the user interface is adequate. However, they are rarely able to design intuitive and efficient user interfaces. Nor are programmers. There are no systematic design methods. At best it is trial-and-error. Lauesen invented a design method (Virtual Windows) that gives a minimum of user screens, good data overview, efficiency for professional users, and fast development. The health record screen at the right was developed with this method.
Mini-course in the method
Some great user interfaces
Microsoft Access tutorial
Professionals need overview of complex data, so good data visualization is crucial. Uvis is a tool that allows IT-interested users to develop interactive, complex data visualizations. The health record screen at the right was made this way. Visualization papers
Lauesen has been involved in many aspects of EHR. Here are some links:
The early national EHR strategy
Graphical and customizable EHR
Anonymizing an EHR
Troubles when deploying EPIC
Time study of EPIC in the clinic
Lauesen has worked in software engineering since 1962. He wrote his first tutorial in 1969, developed operating systems, studied why SW research wasn't used in industry, how perfectionism killed usefulness, and fought hype about OO, SOA and IT-achitecture.
Want help to write problem-oriented requirements? Simply send a message to: firstname.lastname@example.org
One of my interests
I am at the left
Guide to SL-07
Uvis health record
User interface design