Projet-2016-2017-UltraTeam/SRS: Difference between revisions
| Line 34: | Line 34: | ||
The application will also allow users to see on a map where are the other members of their group, and access the informations previously mentionned. These users are the Team Leaders |
The application will also allow users to see on a map where are the other members of their group, and access the informations previously mentionned. These users are the Team Leaders |
||
People should also be able to communicate their position to every users, as long as they activate their Lora Tracker. This could be used as a simple warning or as a SOS message. |
|||
==1.3 Definitions, acronyms and abbreviations== |
==1.3 Definitions, acronyms and abbreviations== |
||
Revision as of 21:25, 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 which will alow you to localise users around you, as long as they are members of your team. This application must be able to work with 3G or lora network.
Users will be able to emit their position thanks to a Lora Tracker. They will also be able to communicate thanks to Modules RN2483.
The application will allow users to transmit informations such as position, heart rate, speed, etc... depending on the equipment they have.
The application will also allow users to see on a map where are the other members of their group, and access the informations previously mentionned. These users are the Team Leaders
People should also be able to communicate their position to every users, as long as they activate their Lora Tracker. This could be used as a simple warning or as a SOS message.
1.3 Definitions, acronyms and abbreviations
User : People who interacts with the application.
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