RICM4 2017 2018 - Serre Connectee / SRS

=1.  Introduction=

1.1 Purpose of the requirements document
The Software Requirements Specification (SRS) is a communication tool between stakeholders and software designers. It gives a description of the software’s purpose and functionality. In other words, the SRS is a document that captures complete description about how the system is expected to perform.

1.2 Scope of the product
The project consist of upgrading a classic greenhouse to retrieve live information about its climate. These information will be available on an online dashboard.

1.3 Definitions, acronyms and abbreviations

 * Greenhouse: an area, usually chiefly of glass, in which the temperature is maintained within a desired range, used for cultivating tender plants or growing plants out of season.
 * LoRa: Long Range and low energy radio RF technology developed by Semtech. It's an open-source technology.

1.4 References

 * Subject [FR]

1.5 Overview of the remainder of the document
=2.  General description=

2.1 Product perspective
The aim of this projet is equip all the farm, not only one greenhouse.

2.2 Product functions
At the end, product should return: And display these data on a graphic interface (dashboard). The checking must be do remotely.
 * The air temperature
 * The air moisture
 * The soil moisture

2.4 General constraints

 * The energy source : There is no power near of the greenhouse, consequently we'll use a battery.
 * Duty Cycle : We can use only 1% of the time in order to comply with the law.
 * Sensors needs to be moveable : Vehicles should be able to move along the greenhouse.

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=

=5. Appendices= =6. Index=