SRS - SmartProjector: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= Introduction = |
= Introduction = |
||
== Purpose == |
== Purpose of the requirements document == |
||
This Software Requirements Specification (SRS) identifies the requirements for project SmartProjector. In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves. |
This Software Requirements Specification (SRS) identifies the requirements for project SmartProjector. In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves. |
||
== |
== Scope of the product == |
||
== Intended audience == |
|||
Sign2Speech could be used at reception desks or during video conferences to allow dumb people to speak with people who don't know the French sign language. |
|||
== Additional information == |
|||
The program will be able to transcribe gestures into written words, printed on the screen. |
|||
== Contact information/SRS team members == |
|||
== Glossary == |
|||
== References == |
== References == |
||
== Overview of the remainder of the document == |
|||
In the remainder of the document, the general description of the software will be exposed. The requirements (functional and non-functional) will be specified in another part. |
|||
| ⚫ | |||
The document will end with the product evolution, the appendices and the index. |
|||
| ⚫ | |||
== Product perspective == |
== Product perspective == |
||
The main aim of our project is to help speechless people to communicate with other people. In this case, we develop a software able to recognize and analyze the sign language to retranscribing it in writting. |
|||
== Product functions == |
== Product functions == |
||
| ⚫ | |||
Our product is able to understand a sign from the hand and to analyze and show the corresponding word on a screen. |
|||
| ⚫ | |||
Mainly, you will need one user that master sign language and another that doesn't know how to understand it. |
|||
The first one will stand in the front of the camera and will speak with sign langage and the other one will watch the monitor to see the translation. |
|||
== 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, |
|||
* 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 |
|||
| ⚫ | |||
'''Pre-condition''': |
|||
'''Post-condition''': |
|||
'''Side-effects''': |
|||
= Product Evolution = |
|||
= External Interface Requirements = |
|||
== User interfaces == |
|||
== Hardware interfaces == |
|||
== Software interfaces == |
|||
== Communication protocols and interfaces == |
|||
= System Features = |
|||
== System feature A == |
|||
=== Description and priority === |
|||
=== Action/result === |
|||
| ⚫ | |||
== System feature B == |
|||
= Appendices = |
|||
= Other Nonfunctional Requirements = |
|||
== Performance requirements == |
|||
== Safety requirements == |
|||
== Security requirements == |
|||
== Software quality attributes == |
|||
== Project documentation == |
|||
== User documentation == |
|||
= Index = |
|||
= Other Requirements = |
|||
== Appendix A: Terminology/Glossary/Definitions list == |
|||
== Appendix B: To be determined == |
|||
Revision as of 10:11, 15 February 2016
Introduction
Purpose of the requirements document
This Software Requirements Specification (SRS) identifies the requirements for project SmartProjector. In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.
Scope of the product
Sign2Speech could be used at reception desks or during video conferences to allow dumb people to speak with people who don't know the French sign language. The program will be able to transcribe gestures into written words, printed on the screen.
Glossary
References
Overview of the remainder of the document
In the remainder of the document, the general description of the software will be exposed. The requirements (functional and non-functional) will be specified in another part. The document will end with the product evolution, the appendices and the index.
General Description
Product perspective
The main aim of our project is to help speechless people to communicate with other people. In this case, we develop a software able to recognize and analyze the sign language to retranscribing it in writting.
Product functions
Our product is able to understand a sign from the hand and to analyze and show the corresponding word on a screen.
User characteristics
Mainly, you will need one user that master sign language and another that doesn't know how to understand it. The first one will stand in the front of the camera and will speak with sign langage and the other one will watch the monitor to see the translation.
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: