SRS

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

Document History

	Version	Date	Authors	Description	Validator	Validation Date
	0.1.0	2013/01/21	Mame Daba Diouf	TBC	TBC	TBC

1. Introduction

1.1 Purpose of the requirements document

This document includes the descriptions of the software services and constraints that should be respected during its development.

It is intended to client engineers and managers, software developers, software users and contractors so that it allows them to understand and validate what the software will do.

1.2 Scope of the product

The name of the product is BMS.

BMS:

• Will control temperature, ventilation, lighting in a building, report residents’ preferences
• Will NOT include security monitor.

1.3 Definitions, acronyms and abbreviations

• BMS = Building Mangaement System
• HVAC = Heating Ventilation Air Conditionning

1.5 Overview of the remainder of the document

The rest of the document contains, along these lines :

- The overall descriptions

- The specific requirements and

- Supporting information

3.Specific requirements, covering functional, non-functional and interface requirements

• document external interfaces,
• describe system functionality and performance
• specify logical database requirements,
• design constraints,
• emergent system properties and quality characteristics.

3.1 Requirement X.Y.Z (in Structured Natural Language)

Function:

Description:

Inputs:

Source:

Outputs:

Destination:

Action:

• Natural language sentences (with MUST, MAY, SHALL)
• Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
• Mathematical Notations
• Tabular notations for several (condition --> action) tuples

Non functional requirements:

Pre-condition:

Post-condition:

Side-effects: