Business Analysis Templates & Aides

Recent Templates | Categories | Search | Subscribe (RSS)

Requirements SL-07 - Template with Examples

Requirements SL-07 - Template with Examples
Statistics: 44018 Views // 4 Comments // Article Rating
Posted by: Adrian M on Saturday, January 21, 2012

Business Analysts, IT developers and consultants often ask for an exemplary requirements specification as a starting point in their specific project. This document is such a specification. It is a template filled out with a complex example: requirements for an Electronic Health Record system (EHR). Only a few points had to be illustrated with examples from other areas. Large parts of the specification may be reused in other projects. Parts that are too special for reuse are shown in italics.

All the requirements are written in tables. The left column is the customer's demands. A sample solution or the proposed solution is in the neighbor column.

You can simply copy the template, delete the first page, and adjust the rest to your project. The parts in italics should always be replaced with something else - without italics.

The guide to the template is published as a separate booklet:

Soren Lauesen: Guide to Requirements SL-07 - Template with Examples.
Lauesen Publishing, 2007. ISBN: 978-87-992344-0-0.
Available on,, or through book stores. 

The guide comments the template page by page, explains why the requirements are stated as they are, what to avoid, and how to elicit and test the requirements.

Author: Soren Lauesen, The IT University of Copenhagen, December 31, 2007

DOWNLOAD: You must be logged-on in order to download templates.


Bill posted on Wednesday, January 7, 2009 2:20 PM
While this is an excellent template it does fall down on the first rule of user orientated documents - no unexplained jargon. In the first section there is mention of a COTS system. Now all of us in IT know what this is or can use Google - but what about the poor business user or executive that only has 5 minutes to read the document....
Ash posted on Sunday, March 1, 2009 12:51 AM
Madhukar posted on Tuesday, May 17, 2011 11:35 AM

pegasusdba posted on Friday, October 14, 2011 2:35 AM
My practice is to always immediately follow a term with an acronym, or, said another way, precede the first use of an acronym with the full name. So, it should be Electronic Health Record (EHR) ...
So bhollins comment about COTS is valid, just as pointing out the E/R diagram has nothiing to do with the ER room :-)
The topics are presented logically, though I'm looking for more summarization that can be used for traceability. That is, it seems like we could miss tracking a few requirements if it's too literal. This is why many of us use a spreadsheet to list each requirement, and perhaps moving it into HP Quality Center for requirements management once we've obtained business signoff.
Nevertheless, Thanks for sharing.
Only registered users may post comments.



Copyright 2006-2024 by Modern Analyst Media LLC