Difference between revisions of "Projet Tachymètre"

From air
Jump to navigation Jump to search
(Created page with "The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard. '''Read first:''' * http://www.cs.st-an...")
 
Line 11: Line 11:
 
|-
 
|-
 
|
 
|
!scope="col"| Version
+
!scope="col"| Version : 0.0.1
!scope="col"| Date
+
!scope="col"| Début : 18/01/2016
!scope="col"| Authors
+
!scope="col"| Auteurs : MACE Quentin, NOUGUIER Thibaut, RAMEL Régis
!scope="col"| Description
+
!scope="col"| Description :
!scope="col"| Validator
+
!scope="col"| Tuteur : Olivier Gattaz
!scope="col"| Validation Date
+
!scope="col"| Rendu : 06/04/2016
 
|-
 
|-
 
!scope="row" |
 
!scope="row" |

Revision as of 13:07, 18 January 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 : 0.0.1 Début : 18/01/2016 Auteurs : MACE Quentin, NOUGUIER Thibaut, RAMEL Régis Description : Tuteur : Olivier Gattaz Rendu : 06/04/2016
0.1.0 TBC TBC TBC TBC TBC


1. Introduction

1.1 Purpose of the requirements document

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