Difference between revisions of "Projets-2016-2017-UPnP Cameras integration into OpenHAB/SRS"

From air
Jump to navigation Jump to search
Line 27: Line 27:
   
 
==1.2 Scope of the product==
 
==1.2 Scope of the product==
  +
  +
Automatic camera detection with UPnP protocol.
  +
  +
Camera management through the OpenHAB interface.
  +
  +
Remote camera control and display live videos from cameras.
  +
  +
Integration into the open source Eclipse SmartHome project.
  +
  +
Tracking feature for cameras.
  +
 
==1.3 Definitions, acronyms and abbreviations==
 
==1.3 Definitions, acronyms and abbreviations==
 
==1.4 References==
 
==1.4 References==

Revision as of 23:05, 4 February 2017

Document History
Version Date Authors Description Validator Validation Date
0.1.0 TBC TBC TBC TBC TBC


1. Introduction

1.1 Purpose of the requirements document

The Software Requirements specification lays out functional and non-functional requirements of cameras integration into OpenHAB. It defines what the user will be able to do or not to do with the final result of the project.

1.2 Scope of the product

Automatic camera detection with UPnP protocol.

Camera management through the OpenHAB interface.

Remote camera control and display live videos from cameras.

Integration into the open source Eclipse SmartHome project.

Tracking feature for cameras.

1.3 Definitions, acronyms and abbreviations

1.4 References

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