RICM4 2017 2018 - Serre Connectee / SRS

Document History

	Version	Date	Authors	Description	Validator	Validation Date
	0.1.0	05.02.2017	Timothée DEPRIESTER, Guillaume BESNARD	TBC	TBC	TBC

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. This information should be available for the farmer to view locally on a screen.

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]

2. General description

2.1 Product perspective

• The aim of this projet is equip to equip multiples farms, not only one greenhouse.
• This project may become a flagship project for ST MicroElectronics

2.2 Product functions

At the end, product should return:

• The air temperature
• The air moisture
• The soil moisture

And display these data on a graphic interface (dashboard). The checking must be done remotely.

2.4 General constraints

• The energy source : There is no power near of the greenhouse, consequently we'll use a battery and a solar panel.
• 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.

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

In this iteration we aim to provide a local data viewer. Other groups are working towards an online dashboard solution. It might be interesting to group all this data on the same online virtual machine.