Projet-2016-2017-UltraTeam/SRS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
!scope="row" | |
!scope="row" | |
||
| 0.1.0 |
| 0.1.0 |
||
| |
| 02/02/17 |
||
| Gallier R. Ferrera A. |
|||
| TBC |
|||
| TBC |
| TBC |
||
| TBC |
| TBC |
||
| Line 24: | Line 24: | ||
=1. Introduction= |
=1. Introduction= |
||
==1.1 Purpose of the requirements document== |
==1.1 Purpose of the requirements document== |
||
The aim of this documents is to provide a definition of the of the different expected feature of our project. |
|||
==1.2 Scope of the product== |
==1.2 Scope of the product== |
||
The scope of the product is to provide a phone application wich will alow you to localise people around you. |
|||
These application must be able to work with 3G or lora network. |
|||
==1.3 Definitions, acronyms and abbreviations== |
==1.3 Definitions, acronyms and abbreviations== |
||
==1.4 References== |
==1.4 References== |
||
| Line 69: | Line 73: | ||
=4. Product evolution= |
=4. Product evolution= |
||
Add group |
|||
=5. Appendices= |
=5. Appendices= |
||
=6. Index= |
=6. Index= |
||
Revision as of 08:54, 2 February 2017
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | 02/02/17 | Gallier R. Ferrera A. | TBC | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
The aim of this documents is to provide a definition of the of the different expected feature of our project.
1.2 Scope of the product
The scope of the product is to provide a phone application wich will alow you to localise people around you. These application must be able to work with 3G or lora network.
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
Add group