Difference between revisions of "SRS - Sign2Speech"
Jump to navigation
Jump to search
Reatha.Tith (talk | contribs) |
Reatha.Tith (talk | contribs) |
||
| Line 22: | Line 22: | ||
* emergent system properties and quality characteristics. |
* emergent system properties and quality characteristics. |
||
| − | == Requirement |
+ | == Requirement == |
| − | '''Function''': |
+ | '''Function''': |
| − | '''Description''': |
+ | '''Description''': |
| + | '''Inputs''': |
||
| − | '''Inputs''': Voice command or button press to start the transcription. |
||
| − | '''Source''': |
+ | '''Source''': |
| − | '''Outputs''': |
+ | '''Outputs''': |
| + | '''Destination''': |
||
| − | '''Destination''': This device is designed to used in a reception environment susceptible of welcoming deaf (or impaired) people.(University, Post office...) |
||
'''Action''': |
'''Action''': |
||
Revision as of 13:56, 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,
- describe system functionality and performance
- specify logical database requirements,
- design constraints,
- emergent system properties and quality characteristics.
Requirement
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: