Proj-2016-2017-ColisMatter/SRS: Difference between revisions
No edit summary |
|||
| Line 52: | Line 52: | ||
* emergent system properties and quality characteristics. |
* emergent system properties and quality characteristics. |
||
==3.1 Requirement |
==3.1 Requirement 1 : Application 1 : RFID Reader== |
||
'''Function''': |
'''Function''': RFID Sensor communication |
||
'''Description''': |
'''Description''': Build a top level layer and application on the NurApi |
||
'''Inputs''': |
'''Inputs''': Communication with a RFID sensor |
||
'''Source''': |
'''Source''': NurApi |
||
'''Outputs''': |
'''Outputs''': RFID Tag |
||
'''Destination''': |
'''Destination''': User or another Application |
||
'''Action''': |
'''Action''': |
||
* ''MUST'' : Communicate with RFid Sensor through the NurApi in order to register the package into the database. |
|||
* 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''': |
'''Non functional requirements''': |
||
'''Pre-condition''': |
'''Pre-condition''': Database operational |
||
'''Post-condition''': |
'''Post-condition''': |
||
'''Side-effects''': |
|||
'''Side-effects''': |
'''Side-effects''': |
||
Revision as of 12:25, 6 February 2017
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
Read first:
- http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
- http://en.wikipedia.org/wiki/Software_requirements_specification
- IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | 06/02/2017 | Hugo Amodru-Favin, Antoine Delise | SRS V1 | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
SRS document aims to define the different characteristics and functions of this project. It has to present functional and non-functional requirements.
This should eventually describe the full content of the subject : applications allowing users to follow packages using RFID.
1.2 Scope of the product
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 1 : Application 1 : RFID Reader
Function: RFID Sensor communication
Description: Build a top level layer and application on the NurApi
Inputs: Communication with a RFID sensor
Source: NurApi
Outputs: RFID Tag
Destination: User or another Application
Action:
- MUST : Communicate with RFid Sensor through the NurApi in order to register the package into the database.
Non functional requirements:
Pre-condition: Database operational
Post-condition:
Side-effects:
Side-effects: