Difference between revisions of "SRS ECOM 2015 GRP5"
Jump to navigation
Jump to search
Robin.Eudes (talk | contribs) |
Robin.Eudes (talk | contribs) |
||
| Line 30: | Line 30: | ||
=1. Introduction= |
=1. Introduction= |
||
| + | ==1.1 Objectif du document d'exigence== |
||
| − | ==1.1 Purpose of the requirements document== |
||
| − | This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe. |
||
| − | In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves. |
||
| − | ==1.2 |
+ | ==1.2 Cadre du produit== |
| − | ==1.3 Definitions, acronyms and abbreviations== |
||
| ⚫ | |||
| − | *The main page of the project: [[Proj-2013-2014-StartAIR-2]] |
||
| + | ==1.3 Définitions, acronymes et abréviations== |
||
| − | ==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)== |
||
| ⚫ | |||
| + | ==1.5 Présentation du restant du document== |
||
| ⚫ | |||
| + | =2. Description générale = |
||
| ⚫ | |||
| + | ==2.1 Perspective du produit== |
||
| ⚫ | |||
| + | ==2.2 Fonctions du produit== |
||
| ⚫ | |||
| + | ==2.3 Caractéristiques de l'utilisateur== |
||
| − | '''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 |
||
| + | ==2.4 Contraintes générales== |
||
| − | '''Non functional requirements''': |
||
| + | |||
| ⚫ | |||
| + | ==2.5 Hypothèses et dépendances== |
||
| + | =3. Exigences spécifiques, exigences d'interface, exigences fonctionnelles, exigences non fonctionnelles= |
||
| ⚫ | |||
| + | ==3.1 Exigences== |
||
| − | '''Side-effects''': |
||
| + | '''Fonction''' : |
||
| ⚫ | |||
| − | =4. Product evolution= |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| − | ==5.1. SRS structure== |
||
| − | The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard. |
||
| − | ''' |
+ | '''Destination''' : |
| + | |||
| − | * 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] |
||
| + | |||
| + | '''Exigences fonctionnelles''' : |
||
| + | |||
| + | '''Exigences non fonctionnelles''' : |
||
| + | |||
| + | |||
| ⚫ | |||
| + | |||
| + | |||
| + | '''Qualité''' : |
||
| + | |||
| ⚫ | |||
| + | |||
| + | |||
| ⚫ | |||
| + | |||
| + | |||
| + | =4. Evolution du produit = |
||
| + | |||
| ⚫ | |||
=6. Index= |
=6. Index= |
||
Revision as of 18:35, 19 October 2015
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
- IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | Robin Eudes, Malek Mammar, Zhang Zhengmeng | Présentation des exigences ECOM-Restauration perosonalisée | TBC | TBC | TBC |
1. Introduction
1.1 Objectif du document d'exigence
1.2 Cadre du produit
1.3 Définitions, acronymes et abréviations
1.4 Références
1.5 Présentation du restant du document
2. Description générale
2.1 Perspective du produit
2.2 Fonctions du produit
2.3 Caractéristiques de l'utilisateur
2.4 Contraintes générales
2.5 Hypothèses et dépendances
3. Exigences spécifiques, exigences d'interface, exigences fonctionnelles, exigences non fonctionnelles
3.1 Exigences
Fonction :
Description :
Inputs :
Outputs :
Destination :
Action :
Exigences fonctionnelles :
Exigences non fonctionnelles :
Risques :
Qualité :
Pré-condition :
Post-condition :