Projets-2015-2016-Borne-Interactive: Difference between revisions
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
=== Objectives === |
=== Objectives === |
||
Set up of logbook |
* Set up of logbook |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
=== Work done === |
=== Work done === |
||
Project requirements (SRS). |
* Project requirements (SRS). |
||
| ⚫ | |||
| ⚫ | |||
=== Problems faced === |
=== Problems faced === |
||
Define the features of the software : Does it has to provide a way to answer for the deaf person? => No |
* Define the features of the software : Does it has to provide a way to answer for the deaf person? => No |
||
| ⚫ | |||
| ⚫ | |||
== Week 3 (January 25th - January 31st) == |
== Week 3 (January 25th - January 31st) == |
||
Revision as of 15:20, 25 January 2016
Subject: Borne interactive - Interactive Terminal
Supervisors:
- Jérôme Maisonasse
Students:
- Quentin DUNAND (RICM4)
- Elsa NAVARRO (RICM4)
- Antoine REVEL (RICM4)
Subject summary
Interactive terminal to welcome deaf or hearing impaired people. Transcription of speech into text. Allows deaf people to understand better the reception staff.
Week 1 (January 11th - January 17th)
Objectives
Discover the project. Contact Jérôme Maisonasse for more details.
Work done
Project chose.
Problems faced
None so far
Week 2 (January 18th - January 24th)
Objectives
- Set up of logbook
- Precise the project ideas.
- List all the Google Speech API features.
Work done
- Project requirements (SRS).
- Brainstorming about project's goal.
Problems faced
- Define the features of the software : Does it has to provide a way to answer for the deaf person? => No
- Choose hardware (touchscreen or keyboard & mouse).
Week 3 (January 25th - January 31st)
Objectives
Work done
UML Diagrams (Use Case & Sequence diagrams & State diagram) : link