Difference between revisions of "Projets-2015-2016-Sonotone-SRS"

From air
Jump to navigation Jump to search
Line 32: Line 32:
 
==1.1 Purpose of the requirements document==
 
==1.1 Purpose of the requirements document==
 
The Software Requirements Specification (SRS) is a document describing the software system of our project: Sonotone adjustable by its user.
 
The Software Requirements Specification (SRS) is a document describing the software system of our project: Sonotone adjustable by its user.
It describes how the system is supposed to to work with functional and non functional requirements.
+
It describes how the system is supposed to work with functional and non functional requirements.
   
 
==1.2 Scope of the product==
 
==1.2 Scope of the product==

Revision as of 15:54, 15 February 2016

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


Read first:

Document History
Version Date Authors Description Validator Validation Date
0.1.0 January 18, 2016 HATTINGUAIS Julian, LECORPS Germain, VOUTAT Manuel Creation of the document TBC TBC


1. Introduction

1.1 Purpose of the requirements document

The Software Requirements Specification (SRS) is a document describing the software system of our project: Sonotone adjustable by its user. It describes how the system is supposed to work with functional and non functional requirements.

1.2 Scope of the product

1.3 Definitions, acronyms and abbreviations

1.4 References

1.5 Overview of the remainder of the document

2. General description

2.1 Product perspective

2.2 Product functions

2.3 User characteristics

2.4 General constraints

2.5 Assumptions and dependencies

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:

4. Product evolution

5. Appendices

6. Index