Difference between revisions of "RICM4 2016 2017 - Ruche Connectee / SRS"

From air
Jump to navigation Jump to search
Line 25: Line 25:
 
=1. Introduction=
 
=1. Introduction=
 
==1.1 Purpose of the requirements document==
 
==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==
 
==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==
 
==1.3 Definitions, acronyms and abbreviations==
  +
LoRa: Long Range radio RF technology, can be use to 20km far.
 
==1.4 References==
 
==1.4 References==
  +
[[RICM4_2016_2017_-_Ruche_Connectee|Project Wiki [FR]]]
 
==1.5 Overview of the remainder of the document==
 
==1.5 Overview of the remainder of the document==
 
=2. General description=
 
=2. General description=

Revision as of 17:37, 6 February 2017

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]

1.5 Overview of the remainder of the document

2. General description

2.1 Product perspective

2.2 Product functions

2.3 User characteristics

2.4 General constraints

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