Soren masters IT-requirements, UX, software acquisition and business. He is helpful, constructive and innovative. He has experience from more than 100 projects and learns new application areas fast. Updated 2021-06-15: New: Y_Foundation test script now available in Danish.
My colleagues in industry and universities praise user stories and epics, but there is no agreement on how to use them and how they cover requirements. So in cooperation with Mohammad Kuhail, I have started an experiment: We compare requirements written in two ways for the same real-life project: based on user stories/epics and based on problem-oriented requirements. Send us YOUR solution! Here is the assignment: Hotline Support (docx).
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 methodSome great user interfacesMicrosoft Access tutorialOther UX papers
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 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-architecture.