SRS - GrenobloisFuté: Difference between revisions
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{|class="wikitable alternance" |
|||
|+ Document History |
|||
|- |
|||
| |
|||
!scope="col"| Version |
|||
!scope="col"| Date |
|||
!scope="col"| Authors |
|||
!scope="col"| Description |
|||
!scope="col"| Validator |
|||
!scope="col"| Validation Date |
|||
|- |
|||
!scope="row" | |
|||
| 0.1.0 |
|||
| January 18, 2016 |
|||
| Delaporte Adrien, Lucidarme Benjamin, Mouret Adrien |
|||
| Creation of the document |
|||
| TBC |
|||
| TBC |
|||
|} |
|||
=1. Introduction= |
=1. Introduction= |
||
==1.1 Purpose of the requirements document== |
==1.1 Purpose of the requirements document== |
||
| Line 31: | Line 9: | ||
==1.3 Definitions, acronyms and abbreviations== |
==1.3 Definitions, acronyms and abbreviations== |
||
* Mobile application : it's a standalone program designed to run on a mobile device like a smartphone or a tablet. |
|||
* Plugin :it's a tool consisting of a set of computer files, and lets you install new features on the sidelines of a program which it is attached. |
|||
==1.4 References== |
==1.4 References== |
||
| Line 43: | Line 23: | ||
==1.5 Overview of the remainder of the document== |
==1.5 Overview of the remainder of the document== |
||
Description of the project |
|||
=2. General description= |
=2. General description= |
||
==2.1 Product perspective== |
==2.1 Product perspective== |
||
The project goal is to provide an application that provides traffic and led work to Grenoble to be able to adapt its path. |
|||
==2.2 Product functions == |
==2.2 Product functions == |
||
* Display real-time traffic on the map of the application |
|||
* Display real-time work on the map of the application |
|||
==2.3 User characteristics== |
==2.3 User characteristics== |
||
Plugin users are motorists who travel in the Grenoble area. |
|||
==2.4 General constraints== |
==2.4 General constraints== |
||
The plugin is available only on android smartphone. |
|||
==2.5 Assumptions and dependencies== |
|||
| Line 70: | Line 49: | ||
==3.1 Requirement X.Y.Z (in Structured Natural Language)== |
==3.1 Requirement X.Y.Z (in Structured Natural Language)== |
||
'''Function''': |
'''Function''': Display on the map the traffic and work. |
||
'''Description''': When traffic is heavy, users see it on the application and can avoid those areas. |
|||
'''Description''': |
|||
'''Inputs''': |
'''Inputs''': Button press to activate the plugin. |
||
'''Source''': |
'''Source''': Open Data from the metromobilite. |
||
'''Outputs''': |
'''Outputs''': Touchscreen |
||
'''Destination''': |
'''Destination''': This device is designed to be used by all people who have a car. |
||
'''Action''': The plugin retrieves the free data and displays it on the map as panels or coloring. |
|||
'''Action''': |
|||
| ⚫ | |||
* Easy to use interface |
|||
| ⚫ | |||
* Free plugin and application |
|||
'''Pre-condition''': |
|||
'''Post-condition''': |
|||
'''Side-effects''': |
|||
=4. Product evolution= |
=4. Product evolution= |
||
* For the work : we could view the details of the work (which are present in the xml file) by clicking on the icon. |
|||
* For the traffic: we could add an option in the GPS which can change routes depending on traffic. |
|||
* Add a zoom setting for the traffic display |
|||
=5. Appendices= |
|||
* Spread to other cities |
|||
* Make an off-line mode |
|||
=6. Index= |
|||
Latest revision as of 19:55, 5 April 2016
1. Introduction
1.1 Purpose of the requirements document
The Software Requirements Specification (SRS) is a document describing the software system of our project: GrenobloisFuté. It describes how the system is supposed to work with functional and non functional requirements.
1.2 Scope of the product
Our application is intended for all motorists Grenoble. The goal is to display the traffic and work presented in the Grenoble area to be able to adjust his path.
1.3 Definitions, acronyms and abbreviations
- Mobile application : it's a standalone program designed to run on a mobile device like a smartphone or a tablet.
- Plugin :it's a tool consisting of a set of computer files, and lets you install new features on the sidelines of a program which it is attached.
1.4 References
Fiche
http://air.imag.fr/index.php/GrenobleFut%C3%A9
Home Page
http://air.imag.fr/index.php/GrenobloisFut%C3%A9
1.5 Overview of the remainder of the document
Description of the project
2. General description
2.1 Product perspective
The project goal is to provide an application that provides traffic and led work to Grenoble to be able to adapt its path.
2.2 Product functions
- Display real-time traffic on the map of the application
- Display real-time work on the map of the application
2.3 User characteristics
Plugin users are motorists who travel in the Grenoble area.
2.4 General constraints
The plugin is available only on android smartphone.
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: Display on the map the traffic and work.
Description: When traffic is heavy, users see it on the application and can avoid those areas.
Inputs: Button press to activate the plugin.
Source: Open Data from the metromobilite.
Outputs: Touchscreen
Destination: This device is designed to be used by all people who have a car.
Action: The plugin retrieves the free data and displays it on the map as panels or coloring.
Non functional requirements:
- Easy to use interface
- Free plugin and application
4. Product evolution
- For the work : we could view the details of the work (which are present in the xml file) by clicking on the icon.
- For the traffic: we could add an option in the GPS which can change routes depending on traffic.
- Add a zoom setting for the traffic display
- Spread to other cities
- Make an off-line mode