Difference between revisions of "Proj-2014-2015-Ext XBMC/SRS"
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
==1.2 Scope of the product== |
==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.3 Definitions, acronyms and abbreviations== |
==1.3 Definitions, acronyms and abbreviations== |
||
Revision as of 11:10, 11 March 2015
| 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.3 Definitions, acronyms and abbreviations
1.4 References
The main page of the project: Extensions XBMC 2015<br\>
1.5 Overview of the remainder of the document
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.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: