Difference between revisions of "RICM4 2017 2018 - IGreenHouse / SRS"
Jump to navigation
Jump to search
| Line 37: | Line 37: | ||
==1.4 References== |
==1.4 References== |
||
| − | * '''Follow-up sheet:''' [[ Projets |
+ | * '''Follow-up sheet:''' [[ Projets-2017-2018-I-Greenhouse : Serre connectée aquaponie]] |
* '''Subject:''' [[ I-Greenhouse]] : [[Serre connectée aquaponie ]] |
* '''Subject:''' [[ I-Greenhouse]] : [[Serre connectée aquaponie ]] |
||
Revision as of 12:40, 5 February 2018
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | 05/02/2018 | SURIER GAROFALO Aurélien, FERREIRA Joffrey, OZENDA Thomas | TBC | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
This Software Requirements Specification (SRS) identifies the requirements for the project I-Greenhouse : Serre connectée aquaponie. This document is a guideline about the functionalities offered and the problems that the system solves.
1.2 Scope of the product
The goal of this project is to connect an aquaponic greenhouse by using LoRa tecnology. Broadly speaking, it involves places different sensors in the greenhouse and take some measures to inform the farmer about the state of his crops.
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
- Follow-up sheet: Projets-2017-2018-I-Greenhouse : Serre connectée aquaponie
- Subject: I-Greenhouse : Serre connectée aquaponie
1.5 Overview of the remainder of the document
General description of the project followed by all its requirements and the product evolution.
2. General description
2.1 Product perspective
2.2 Product functions
2.3 User characteristics
2.4 General constraints
CHARO
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: