Difference between revisions of "Proj-2012-2013-CaveVinNFC"
| Line 1: | Line 1: | ||
| + | =1. Introduction= |
||
| + | ==1.1 Purpose of the requirements document== |
||
| + | The purpose of the documents is to explain how we will manage our project, the different steps of the conception. And endly, the realisation. |
||
| + | ==1.2 Scope of the product== |
||
| + | The product aims people who have a wine cellar and want to control the humidity and the temperature. We will also provide an application which permits the user to know at every time the telemetry and the contain of his cellar. |
||
| + | ==1.3 Definitions, acronyms and abbreviations== |
||
| + | NFC : http://en.wikipedia.org/wiki/Near_field_communication <br\> |
||
| + | Mifare : http://en.wikipedia.org/wiki/MIFARE<br\> |
||
| + | RFID : http://en.wikipedia.org/wiki/RFID |
||
| + | ==1.4 References== |
||
| + | ==1.5 Overview of the remainder of the document== |
||
| + | =2. General description= |
||
| + | ==2.1 Product perspective== |
||
| + | A smartphone application and a linked web application which allows the owner to consult the state of his cellar |
||
| + | ==2.2 Product functions== |
||
| + | The functions of our project is mainly to : |
||
| + | ::- Consult the humidity and temperature of his cellar<br\> |
||
| + | ::- Consult the number of bottles in his cellar thanks to the database stored on a server from a website or an application<br\> |
||
| + | ::- Be able to add/remove a bottle or a box of bottles<br\> |
||
| + | ::- An alarm is send to the proprietary of the cellar in case of troubles (using email, sms, notification...) : intrusion, deviations of temperature or humidity |
||
| + | ==2.3 User characteristics== |
||
| + | Like wine<br\> |
||
| + | Have a wine cellar device<br\> |
||
| + | Have a NFC equipment (reader, writer, tags)<br\> |
||
| + | ==2.4 General constraints== |
||
| + | An Internet access is required<br\> |
||
| + | A smartphone as NFC equipment is recommended |
||
| + | ==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= |
||
| + | The evolution that we can do is to control the cave remote manually in case of problem of the cellar cave. |
||
| + | =5. Appendices= |
||
| + | =6. Index= |
||
Revision as of 16:46, 2 February 2013
1. Introduction
1.1 Purpose of the requirements document
The purpose of the documents is to explain how we will manage our project, the different steps of the conception. And endly, the realisation.
1.2 Scope of the product
The product aims people who have a wine cellar and want to control the humidity and the temperature. We will also provide an application which permits the user to know at every time the telemetry and the contain of his cellar.
1.3 Definitions, acronyms and abbreviations
NFC : http://en.wikipedia.org/wiki/Near_field_communication <br\> Mifare : http://en.wikipedia.org/wiki/MIFARE<br\> RFID : http://en.wikipedia.org/wiki/RFID
1.4 References
1.5 Overview of the remainder of the document
2. General description
2.1 Product perspective
A smartphone application and a linked web application which allows the owner to consult the state of his cellar
2.2 Product functions
The functions of our project is mainly to :
- - Consult the humidity and temperature of his cellar<br\>
- - Consult the number of bottles in his cellar thanks to the database stored on a server from a website or an application<br\>
- - Be able to add/remove a bottle or a box of bottles<br\>
- - An alarm is send to the proprietary of the cellar in case of troubles (using email, sms, notification...) : intrusion, deviations of temperature or humidity
2.3 User characteristics
Like wine<br\> Have a wine cellar device<br\> Have a NFC equipment (reader, writer, tags)<br\>
2.4 General constraints
An Internet access is required<br\> A smartphone as NFC equipment is recommended
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
The evolution that we can do is to control the cave remote manually in case of problem of the cellar cave.