Difference between revisions of "SRS - Sign2Speech"
Jump to navigation
Jump to search
(Created page with "= Introduction = == Purpose == == Document conventions == == Intended audience == == Additional information == == Contact information/SRS team members == == References == = ...") |
Reatha.Tith (talk | contribs) |
||
| Line 1: | Line 1: | ||
= Introduction = |
= Introduction = |
||
| − | == Purpose == |
+ | == Purpose of the requirements document == |
| − | == |
+ | == Scope of the product == |
| − | == |
+ | == Glossary == |
| − | == Additional information == |
||
| − | == Contact information/SRS team members == |
||
== References == |
== References == |
||
| + | == Overview of the remainder of the document == |
||
| − | = |
+ | = General Description= |
== Product perspective == |
== Product perspective == |
||
== Product functions == |
== Product functions == |
||
| − | == User |
+ | == User characteristics == |
== Operating environment == |
== Operating environment == |
||
| − | == |
+ | == General constraints == |
| − | == Design/implementation constraints == |
||
== Assumptions and dependencies == |
== Assumptions and dependencies == |
||
| + | = Specific requirements, covering functional, non-functional and interface requirements =document external interfaces, |
||
| + | * 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)== |
||
| − | = External Interface Requirements = |
||
| + | '''Function''':Live transcription |
||
| − | == User interfaces == |
||
| + | |||
| − | == Hardware interfaces == |
||
| + | '''Description''': When the receptionist speak a live transcription can be seen by both users. |
||
| − | == Software interfaces == |
||
| + | |||
| − | == Communication protocols and interfaces == |
||
| + | '''Inputs''': Voice command or button press to start the transcription. |
||
| + | |||
| + | '''Source''': Mouse or microphone. |
||
| + | |||
| + | '''Outputs''': Screen (Touchscreen?) |
||
| + | |||
| + | '''Destination''': This device is designed to used in a reception environment susceptible of welcoming deaf (or impaired) people.(University, Post office...) |
||
| + | |||
| + | '''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 |
||
| + | |||
| ⚫ | |||
| + | |||
| + | '''Pre-condition''': |
||
| + | |||
| + | '''Post-condition''': |
||
| + | |||
| + | '''Side-effects''': |
||
| − | = System Features = |
||
| − | == System feature A == |
||
| − | === Description and priority === |
||
| − | === Action/result === |
||
| ⚫ | |||
| − | == System feature B == |
||
Revision as of 13:52, 25 January 2016
Introduction
Purpose of the requirements document
Scope of the product
Glossary
References
Overview of the remainder of the document
General Description
Product perspective
Product functions
User characteristics
Operating environment
General constraints
Assumptions and dependencies
= Specific requirements, covering functional, non-functional and interface requirements =document external interfaces,
- 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:Live transcription
Description: When the receptionist speak a live transcription can be seen by both users.
Inputs: Voice command or button press to start the transcription.
Source: Mouse or microphone.
Outputs: Screen (Touchscreen?)
Destination: This device is designed to used in a reception environment susceptible of welcoming deaf (or impaired) people.(University, Post office...)
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: