Proj-2012-2013-Audioprothèse DIY 1/SRS
1. Introduction
1.1 Purpose of the requirements document
The purpose of the document is to explain how we will manage our project, the different steps of the conception. Endly, the realisation.
1.2 Scope of the product
The application is designed to allow people with hearing difficulties to listen to audio documents on their computers without using their usual hearind aids, which don't always provide the best solutions according to the sounds they have to process.
1.3 Definitions, acronyms and abbreviations
A hearing aid is an electroacoustic device which typically fits in or behind the wearer's ear, and is designed to amplify and modulate sound for the wearer.
1.4 References
http://en.wikipedia.org/wiki/Hearing_aid
1.5 Overview of the remainder of the document
2. General description
2.1 Product perspective
In a first time, we will developp a computer application which allows the user to adapt output sound to his hearing ability, and to run audio programs with this sound adapting. Then, we could developp the same application on an Android phone, and then users would use it easier.
2.2 Product functions
At first, our applicaiton asks the user to create an account in order to store his data(name, password,and parameters linked to his hearing abilities) Once the account created, if it is the first use for the user, the application proposes him to make a test in order to determine his hearing abilities which are stored in a configuration file. Then,depending on the result, the application fixes the parameters of the next sounds. Also, the user will be able to change the paramaters manually.
2.3 User characteristics
Have a computer,running on Windows or Linux operating system. Have an android phone. ....And hearing impairment.
2.4 General constraints
This application is mainly dedicated to old people who don't always know how to use correctly a computer or an Android phone to launch the application,some users can need some assistance.
2.5 Assumptions and dependencies
3.Specific requirements, covering functional, non-functional and interface
- 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 :<br\> Produce sounds with a specific processing.<br\><br\> Description :<br\> An application on a computer or/and on an Adroid phone.<br\><br\> Inputs :<br\> A sound<br\><br\> Outputs :<br\> The input sound with a processing making it more adapted to the user's hearing abilities.<br\><br\> Destination :<br\> People suffering from hearing impairments.<br\><br\> Action :<br\> Change sound parameters to make the sound audible.<br\><br\> Pre-condition :<br\> Post-condition :<br\> The program must ensure that all sounds produced can be heard by the user.
4. Product evolution
Make possible running audio/video files with the corrections made by the program.<br\><br\> Create the same application embedded on a card.