From air
Revision as of 20:42, 18 January 2016 by Antoine.Revel (talk | contribs)
Jump to: navigation, search
Document History
Version Date Authors Description Validator Validation Date
0.1.0 January 18, 2016 Quentin DUNAND - Elsa NAVARRO - Antoine REVEL Creation of the document TBC TBC

1. Introduction

1.1 Purpose of the requirements document

This Software Requirements Specification (SRS) identifies the requirements for project "Borne Interactive". 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.

1.2 Scope of the product

Toutes structures voulant proposer un système pour les personnes malentendantes.

1.3 Definitions, acronyms and abbreviations

1.4 References

1.5 Overview of the remainder of the document

2. General description

The aim of this project is to design a new interactive system for help impaired hearing people, by writing what the receptionnist is saying.

2.1 Product perspective

When deaf(or Impaired hearing) people come at a recpetion stand, to, for example, request informations, they can have difficulties communicating with the receptionist. Our product make a live transcription of the receptionist speech and write it down on a screen to help the people understand the receptionist in a possible noisy environnment where it's hard to communicate. Since voice recognition make mistakes and don't recognise technical terms, our product also offer a mean of correction for the receptionist.

2.2 Product functions

Live transcription of the receptionist voice. Possibility to correct the transcription (for mistakes or technical terms)

2.3 User characteristics

Two types of users, the receptionist and the deaf (or impaired) person. The receptionist can correct the live transcription. The impaire person read the live transcription in a easy way.

2.4 General constraints

Only made by using Web technologies suach as HTML/PHP/JavaScript to make it run on almost every devices. Should use the Google Speech Recognition API.

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: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...)


  • 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:




4. Product evolution

5. Appendices

6. Index