Difference between revisions of "RICM4 2017 2018 - RobAIRDL/ SRS"
Jump to navigation
Jump to search
Jordan.Jean (talk | contribs) |
|||
| Line 50: | Line 50: | ||
==3.1 Requirement X.Y.Z (in Structured Natural Language)== |
==3.1 Requirement X.Y.Z (in Structured Natural Language)== |
||
| − | '''Function''': |
+ | '''Function''': guide people |
| + | '''Description''': The main goal of this projetc is to develop a brand new feature allowing us to locate ourselves. |
||
| − | '''Description''': |
||
| − | '''Inputs''': |
+ | '''Inputs''': tablet, software, and proximity sensors |
| − | '''Source''': |
+ | '''Source''': tablet, wencam, STM32 |
| − | '''Outputs''': |
+ | '''Outputs''': tablet, software |
| − | '''Destination''': |
+ | '''Destination''': RobAIR control system |
'''Action''': |
'''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 |
||
| + | * RobAIR must be able to guide people within the building (IMAG). |
||
| ⚫ | |||
| + | * It must be able to communicate with people by showing them the path to be taken and clearly explaining what it is doing. |
||
| + | * RobAIR must be able to move around autonomously and figure its path out |
||
| + | * Avoid obstacles. |
||
| ⚫ | |||
| ⚫ | |||
| + | * WebRTC |
||
| + | * Ros |
||
| + | * Arduino |
||
| + | * Web server |
||
| + | * Custumed power supply unit |
||
| + | * Low cost |
||
| + | |||
| ⚫ | |||
| ⚫ | |||
| + | |||
| ⚫ | |||
'''Side-effects''': |
'''Side-effects''': |
||
| + | * Bad guidance |
||
| + | * Collisions |
||
=4. Product evolution= |
=4. Product evolution= |
||
Revision as of 13:34, 5 February 2018
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 | TBC | TBC | TBC | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
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 X.Y.Z (in Structured Natural Language)
Function: guide people
Description: The main goal of this projetc is to develop a brand new feature allowing us to locate ourselves.
Inputs: tablet, software, and proximity sensors
Source: tablet, wencam, STM32
Outputs: tablet, software
Destination: RobAIR control system
Action:
- RobAIR must be able to guide people within the building (IMAG).
- It must be able to communicate with people by showing them the path to be taken and clearly explaining what it is doing.
- RobAIR must be able to move around autonomously and figure its path out
- Avoid obstacles.
Non functional requirements:
- WebRTC
- Ros
- Arduino
- Web server
- Custumed power supply unit
- Low cost
Pre-condition: functional RobAIR
Post-condition: People reach their destination
Side-effects:
- Bad guidance
- Collisions