RICM4 2016 2017 - Ruche Connectee / SRS

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

Document History

	Version	Date	Authors	Description	Validator	Validation Date
	0.1	06/02/17	MOREAU - LESAGE	Starting	TBC	TBC

1. Introduction

1.1 Purpose of the requirements document

This SRS (Software Requirements Specification) is a description of the project, containing all users and technologies characteristics.

1.2 Scope of the product

The project consists of building a connection between a hive and a beekeeper, to monitor the hive with some captors. We are twinned with an IESE group which is working on the captors and they'll give us the collected data.

1.3 Definitions, acronyms and abbreviations

LoRa: Long Range radio RF technology, can be use to 20km far.

1.4 References

Project Wiki [FR]

2. General description

2.1 Product perspective

The aim of the project is basically to transmit data from serial link to a distance monitoring computer. This project can evolve in the future to connect hives from all around the metropolis to a central server. We can be link to the BioLab in Grenoble to build a new future for the Grenoble's bees.

2.2 Product functions

The product will have an overview of informations collected from the hive at anytime, and it'll be flexible in order to add others captors (or others hives). At the moment, the aim is to collect the weight and the inside's temperature of the hive.

2.3 User characteristics

There aren't specifics user characteristics at the moment.

2.4 General constraints

• Radio occupation : We can emit only 1% of the time (36 second each hour in total)
• Transmissions errors : In case of interferences, we need to manage the reemission of data
• Stability : We can't open the hive in winter, to avoid killing bees

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: