SRS - SmartProjector

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

SmartProjector est conçu dans le cadre de SmartClassRoom. Il peut perte utilisé en dehors de cette intégration mais est plus performant en ce contexte. Le projet permet de se passer de fils pour projeter son écran sur une surface (peut être autre qu'un vidéo-projecteur). Dans le cadre de SmartClassRoom, nous avons imaginé que les élèves puissent se connecter pour faire une présentation, ou poser des questions, pour montrer leur écrans, tout ceci sous la supervision d'un admin : le professeur.

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

Notre produit va permettre de se passer de fils mais aussi d'avoir une véritable interaction avec les élèves tout au long d'un court.

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.

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: