Difference between revisions of "Projets-2016-2017-StartAir-SRS"

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...")
 
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
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-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
 
* http://en.wikipedia.org/wiki/Software_requirements_specification
 
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]
 
   
 
{|class="wikitable alternance"
 
{|class="wikitable alternance"
Line 20: Line 13:
 
!scope="row" |
 
!scope="row" |
 
| 0.1.0
 
| 0.1.0
| TBC
+
| 06.02.2017
  +
| Simon CHAMBONNET, Boris ODIEVRE
| TBC
 
 
| TBC
 
| TBC
 
| TBC
 
| TBC
Line 31: Line 24:
 
=1. Introduction=
 
=1. Introduction=
 
==1.1 Purpose of the requirements document==
 
==1.1 Purpose of the requirements document==
  +
;Project name : “StartAir”
  +
;Supervisor : Nicolas Palix
  +
;School : Polytech Grenoble
  +
;Product designer/manufacturer Team : Simon CHAMBONNET and Boris ODIEVRE
  +
;Customer: Polytech Grenoble
  +
 
==1.2 Scope of the product==
 
==1.2 Scope of the product==
 
==1.3 Definitions, acronyms and abbreviations==
 
==1.3 Definitions, acronyms and abbreviations==

Latest revision as of 16:49, 6 February 2017

Document History
Version Date Authors Description Validator Validation Date
0.1.0 06.02.2017 Simon CHAMBONNET, Boris ODIEVRE TBC TBC TBC


1. Introduction

1.1 Purpose of the requirements document

Project name
“StartAir”
Supervisor
Nicolas Palix
School
Polytech Grenoble
Product designer/manufacturer Team
Simon CHAMBONNET and Boris ODIEVRE
Customer
Polytech Grenoble

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