Proj-2014-2015-Ext XBMC/SRS

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

This Software Requirements Specification (SRS) identifies the requirements for the xbmc/Kodi extension development project. This document is a guideline about the functionalities offered and the problems that the system solves.

1.2 Scope of the product

• The purpose of this project is to allow a user, playing files with xbmc, to have an experience of mobility while watching a film or listening to music, thanks to numerous computers with xbmc on it and sharing of files over the network.

• The code used in this project is extensible and open-source.

1.4 References

• Page of the project : Extensions XBMC Sujet 2015
• Last year project : Extensions XBMC Sujet 2014

1.5 Overview of the remainder of the document

The rest of the SRS examines the specifications of the Extensions XBMC 2015 project in details. Section two of the SRS presents the general features of the FollowME extension. Section three outlines the detailed, specific and functional requirements, system and other related requirements of the project. Supporting information about appendices is provided in Section three.

2. General description

2.1 Product perspective

Play video or music on various screen/kodi application according to the location of the main user.

2.3 User characteristics

The user does not need to be familiar with coding or computer science. The only requierement is to be able to share files on a network and to install Addon on xbmc.

2.5 Assumptions and dependencies

• The android device used as remote controller have a wi-fi access to the network in order to control the xbmc instances
• The xbmc instances are runned on computers on the same network with shared library contaning files that will be resumed.

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: