Difference between revisions of "Projets-2015-2016-Sonotone-SRS"

From air
Jump to navigation Jump to search
Line 35: Line 35:
   
 
==1.2 Scope of the product==
 
==1.2 Scope of the product==
The Hearing aid is a technology well-knowned and well-used to correct impaired hearing, designed to amplify sound for the wearer.
+
The Hearing aid is a technology well-knowned and well-used to correct impaired hearing. Designed to amplify sound for the wearer, this type of device requires a large amount of knowledge in signal process, electronics , software development and about the functionning of a human ear. For this project, we only focused on the software aspect.
This type of device required a large amount of knowledge in signal process, electronics , software development and about the functionning of a human ear. In our case, we focused only on the software aspect.
 
   
We noticed that the main problem to acquired a hearing aid is the price. It is not due to the technology. The main cost come from the adjustement of the prosthesis made by a audioprothetist.
+
The main problem to acquire a hearing aid is the price. However, it is not related to the technology. The main part of the cost comes from the adjustements of the prosthesis by a audioprothetist.
   
The aim of the project is to permit the user to adjust by himself the hearing aid by develloping a new software with is capable of correcting impaired hearing adjustable in a simple way by the user.
+
The main goal of this project is to allow any user to adkust his hearing aid by himself. This will be donc by our software which allows to simply modify the frequences heard with an equalizer.
   
 
==1.3 Definitions, acronyms and abbreviations==
 
==1.3 Definitions, acronyms and abbreviations==

Revision as of 16:17, 15 February 2016

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.


Read first:

Document History
Version Date Authors Description Validator Validation Date
0.1.0 January 18, 2016 HATTINGUAIS Julian, LECORPS Germain, VOUTAT Manuel Creation of the document TBC TBC


1. Introduction

1.1 Purpose of the requirements document

The Software Requirements Specification (SRS) is a document describing the software system of our project: Sonotone adjustable by its user. It describes how the system is supposed to work with functional and non functional requirements.

1.2 Scope of the product

The Hearing aid is a technology well-knowned and well-used to correct impaired hearing. Designed to amplify sound for the wearer, this type of device requires a large amount of knowledge in signal process, electronics , software development and about the functionning of a human ear. For this project, we only focused on the software aspect.

The main problem to acquire a hearing aid is the price. However, it is not related to the technology. The main part of the cost comes from the adjustements of the prosthesis by a audioprothetist.

The main goal of this project is to allow any user to adkust his hearing aid by himself. This will be donc by our software which allows to simply modify the frequences heard with an equalizer.

1.3 Definitions, acronyms and abbreviations

Hearing aid / Sonotone : an electroacoustic device which is designed to amplify sound for the wearer

Hard of hearing person : A person whoch is partially deaf.

1.4 References

Wikipedia : https://en.wikipedia.org/wiki/Hearing_aid

1.5 Overview of the remainder of the document

2. General description

2.1 Product perspective

The main aim of the project is to provide people a hearing aid at a lower cost. The software we work on will permit hard of hearing person to adjust their sonotone by themselves.

2.2 Product functions

2.3 User characteristics

2.4 General constraints

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:

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:

4. Product evolution

5. Appendices

6. Index