Template with Examples

IT developers and consultants often ask for an exemplary requirements specific= a­tion as a starting point in their specific project. This document is such a specifica­tion. It is a template filled out with a complex example: requirements for an Elec­tronic He= alth Record system (EHR). Only a few points had to be illustrated with examp= les from other areas. Large parts of the specification may be re­used in ot= her projects. Parts that are too special for reuse are shown in italics.

&= nbsp;

All the requirements are written in tables. The left column is the customer's demands. A sample Soren Lauesen: Guide to Requirements SL-07 - Template with Examples.
Lauesen Publishing, 2007. ISBN: 978-87-992344-0-0.

See book samples, etc. on www.itu.dk/people/slauesen

The gu= ide comments the template page by page, explains why the requirements are state= d as they are, what to avoid, and how to elicit and test the requirements.<= /o:p>

&= nbsp;

I wrote large parts of the template and the guide on request from the Danish Min&sh= y;istry of Research, Technology and Development, as part of a standard contract for software acquisition (K02). I am grateful to Sten Mogensen (from the Minist= ry) for constructive cooperation, to Tina E. Jakobsen (from the IT University) = for language editing, and to Vibeke Søderhamn (from= the IT University of Copenhagen) for a thoughtful and meticulous review of the documents.

&= nbsp;

In many cases the requirements will be an appendix to a contract between the custom= er and the supplier. The contract may have separate appendices for opera­t= ion, maintenance, response time, etc. In such cases the corresponding chapters of the requirements specification must be moved to these appendices.

&= nbsp;

Earlier versions of the template have been used with success in 18 very different projects, for instance requirements to the new CMS of the Danish Defense, to Novo's environmental reporting system, and to a COTS vendor's next version = of his product. Experiences from these 18 projects helped me improve this vers= ion.

&= nbsp;

Any co= mments - positive as well as negative - are most welcome and will help me improve future versions.

&= nbsp;

The IT University of Copen= hagen, December 31, 2007

 =

(below called the EHR s= ystem) =

Supplier

Software, operation and maintenance of an EHR system

..= ..........................................