air - User contributions [en]

Projets 2017-2018

2018-04-08T08:47:25Z

Julien.Cordat-Auclair: /* Affectations */

<<[[Projets 2016-2017]] | [[Projets]] | [[Projets 2018-2019]]>>
=RICM=
==RICM3==

==RICM4==
===Projet Semestre S8===

Enseignants responsables : Olivier Richard, Didier Donsez

* Dates : Lundi après-midi, Mardi après-midi
* Lancement: 15/01/2018 en 257 à 15h45
* Soutenances: '''Lundi 9 avril''': [[Ordre_passages_soutenances_RICM4_2017_2018 | Ordre de passages]]
* Soutenances à mi-parcours: Lundi 12 et mardi 13 mars: [[ordre_passages_mi_parcours_RICM4_2017_2018 | Ordre de passages]]

* '''Evaluation à mi-parcours le lundi/mardi ???''': Format: 10min (5min de présentation 3 slides au plus, 5min de discussion). Cette évaluation sera prise en compte dans la note finale.

'''Consignes générales:'''

* '''Vous devez être pro-actifs !!!''': Si des points sont pas ou mals spécifiés, vous le faîtes et vous justifiez vos choix. Pour les problèmes techniques éventuels vous pouvez: creuser la question, contacter l'auteur du code si il y a lieu, écrire un rapport de bug ('''Attention:''' ca se prépare !), soumettre un patch/pull request, contacter l'enseignant ou la personne référente du projet.

* '''Vous devez maintenir une fiche de suivi de projet''': elle doit être mise à jour chaque semaine, elle rassemble les élements essentiels du projet, elle indique les évolutions du projet et présente sa feuille de route. '''Note:''' le nom de la fiche doit être composé du nom du projet et suffixé par ricm4_2017_2018. '''Cette fiche compte pour la note finale'''

* '''Votre code''' pour doit être hébergé sur le gitlab et à l'URL suivante https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18 , vous utiliserez votre compte UGA.

* Les documents public doivent être rédigés en anglais (README, documentation, commentaires de code, nom de variables et de fonctions). Une bonnification sera accordée si le rapport et les transparents sont en anglais (la soutenance sera en francais).

'''Propositions de projets:'''

# [[QCM C2I]] , Pierre Gillois, Didier Donsez
# [[Dashboard pour gestionnaire de tâches]] (Angular 5): Olivier Richard
# [[Moteur de workflows distribué]] (WDL/Cromwell): Olivier Richard
# [[ESP32 et language D]]: Olivier Richard
# [[Serious game multi-joueurs pour tables tactiles en réseau]] : Didier Donsez, Anne-Laure Finkel, Stéphanie Diligent.
# [[Challenge OpenCity]] : Georges-Pierre Bonneau, Didier Donsez
# Projet [[UltraTeam]] avec des trackers [[ESP32-LoRa]] + GPS : Reprise partielle du projet eCOM de gestion des courses sportives et du projet [[UltraTeam]] 2017 pour la partie backend et frontend du projet : Didier Donsez
# Projet [[Réseau Social LoRa]] avec des pods [[ESP32-LoRa]] : Olivier Richard.
# Contribution et evaluation au/du projet [https://github.com/IntelLabs/hpat HPAT] (A compiler-based big data framework in Python): Olivier Richard.
# [[Ruche connectée LoRa]] : Nicolas Palix
# [[Serres connectées]] : Nicolas Palix
# [[I-Greenhouse]] : [[Serre connectée aquaponie]] : Nicolas Palix
# Projet "Plateforme de mise en relation pour les entrepreneurs sociaux" : Didier Donsez
# [[Chatbot pour borne d'accueil handicap]] : Didier Donsez, Marie-Paule Balicco et Jérôme Maisonnasse (service accueil handicap COMUE UGA)
# Connected Shop (avec [[Eclipse SmartHome]]) : Didier Donsez.
# [[Deploiment Nucleo | Déploiement sécurisé et sans fil pour carte Nucleo]]: Olivier Richard et Sylain Toru
# [[RobAIR]] : Cobot Majordome : Jérôme Maisonnasse, Germain Lemasson, Bastien Scher (FabMSTIC).

==== Affectations ====
{|class="wikitable alternance"
|+ Affectation des projets RICM4 2017-2018
|-
|
!scope="col"| Sujet
!scope="col"| Etudiants
!scope="col"| Enseignant(s)
!scope="col"| Fiche de suivi
!scope="col"| Dépot git
|-

!scope="row"| 1
| [[QCM C2I]]
| NON ATTRIBUÉ
| Pierre Gillois, Didier Donsez
| [[RICM4_2017_2018_-_| Fiche]] - [[RICM4_2017_2018_-_/_SRS|SRS]] - [[RICM4_2017_2018_-_/UML | UML]]
|
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 2
| [[Dashboard pour gestionnaire de tâches]] (Angular 5)
| BELGUENDOUZ Sekina, LARNICOL Titouan
| Olivier Richard
| [[RICM4_2017_2018_-_Dashboard| Fiche]] - [[RICM4_2017_2018_-_Dashboard/SRS|SRS]] - [[RICM4_2017_2018_-_Dashboard/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/2 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:Dashboard_en.pdf|Presentation de mi-parcours EN]] - [[Media:Dashboard_fr.pdf|Presentation de mi-parcours FR]] - [[Media:Dashboard_fr.pptx|Presentation de mi-parcours en pptx]]
|-

!scope="row"| 3
| [[Moteur de workflows distribué]] (WDL/Cromwell)
| NON ATTRIBUÉ
| Olivier Richard
| [[RICM4_2017_2018_-_| Fiche]] - [[RICM4_2017_2018_-_/_SRS|SRS]] - [[RICM4_2017_2018_-_/UML | UML]]
|
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 4
| [[ESP32 et language D]]
| MANGER Raphael, HOUBRON Adrian
| Olivier Richard
| [[RICM4_2017_2018_-_ESP32_D| Fiche]] - [[RICM4_2017_2018_-_ESP32_D/_SRS|SRS]] - [[RICM4_2017_2018_-_ESP32_D/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/4 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 5
| [[Serious game multi-joueurs pour tables tactiles en réseau]]
| LEPAGE Tim, SERGEANT Dimitri
| Didier Donsez, Anne-Laure Finkel, Stéphanie Diligent
| [[RICM4_2017_2018_-SeriousGame Polystar | Fiche]] - [[RICM4_2017_2018_- SeriousGame Polystar /_SRS|SRS]] - [[RICM4_2017_2018_- SeriousGame Polystar /UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/5 gitlab]
| [[Media:xxx_.pdf|Rapport final]] - [[Media:xxx_.pdf|Presentation finale FR]] - [[Media:xxx_.pdf|Final Presentation EN]] - [[Media:affiche_Polystar.pdf|Affiche]] - [[Media:PolyStar.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 6
| [[Challenge OpenCity]]
| BOUCHERIMA Amina, FOMBARON Quentin
| Georges-Pierre Bonneau, Didier Donsez
| [[RICM4_2017_2018_-_OpenCity| Fiche]] - [[RICM4_2017_2018_-_OpenCity/_SRS|SRS]] - [[RICM4_2017_2018_-_OpenCity/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/6 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 7.1
| Projet [[UltraTeam]] avec des trackers [[ESP32-LoRa]] + GPS
| TERRIER Bastien, GROS-DAILLON Hugo
| Didier Donsez
| [[RICM4_2017_2018_-_UltraTeam_7.1| Fiche]] - [[RICM4_2017_2018_-_UltraTeam_7.1/_SRS|SRS]] - [[RICM4_2017_2018_-_UltraTeam_7.1/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/7.1 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:UltraTeam_7.1_Flyer.jpg|Flyer]] - [[Media:UltraTeam 7.1 Mid Presentation.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 7.2
| Projet [[UltraTeam]] avec des trackers [[ESP32-LoRa]] + GPS
| MOLION Enzo, VALETTE Léo
| Didier Donsez
| [[RICM4_2017_2018_-_UltraTeamMV| Fiche]] - [[RICM4_2017_2018_-_UltraTeamMV_:_SRS|SRS]] - [[RICM4_2017_2018_-_UltraTeamMV_:_UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/7.2 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 8
| Projet [[Réseau Social LoRa]] avec des pods [[ESP32-LoRa]]
| VEGREVILLE Thibaud, GENTILLON Loris, ZHENG Jian
| Olivier Richard
| [[RICM4_2017_2018_-_Réseau_Social_LoRa| Fiche]] - [[RICM4_2017_2018_-_Réseau_Social_LoRa/_SRS|SRS]] - [[RICM4_2017_2018_-_Réseau_Social_LoRa/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/8 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 9
| Contribution et evaluation au/du projet [https://github.com/IntelLabs/hpat HPAT]
| NON ATTRIBUÉ
| Olivier Richard
| [[RICM4_2017_2018_-_| Fiche]] - [[RICM4_2017_2018_-_/_SRS|SRS]] - [[RICM4_2017_2018_-_/UML | UML]]
|
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 10
| [[Ruche connectée LoRa]]
| BESNIER Benjamin, LÉVESQUE Théo, WEILL William
| Nicolas Palix
| [[RICM4_2017_2018_-_Ruche_Connectee_| Fiche]] - [[RICM4_2017_2018_-_Ruche_Connectee_/_SRS|SRS]] - [[RICM4_2017_2018_-_Ruche_Connectee/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/10 gitlab]
| [[RICM4_2017_2018_|Rapport final]] - [[RICM4_2017_2018_|Presentation finale FR]] - [[RICM4_2017_2018_|Final Presentation EN]] - [[RICM4_2017_2018_|Flyer]] - [[Media:RICM4_2017_2018_-_Ruche_Connectee_Mi_parcours_presentation.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 11
| [[Serres connectées]]
| BESNARD Guillaume, DEPRIESTER Timothée
| Nicolas Palix
| [[RICM4_2017_2018_-_Serre_Connectee| Fiche]] - [[RICM4_2017_2018_-_Serre_Connectee_/_SRS|SRS]] - [[RICM4_2017_2018_-_Serre_Connecte/UML | UML]] - [[RICM4_2017_2018_-_Serre_Connecte/Schedule | Schedule]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/11 gitlab]
| [[Media:RICM4_2017_2018_-_Serre_Connecte_Rapport_Final.pdf|Rapport final]] - [[Media:RICM4_2017_2018_-_Serre_Connecte_Presentation_Final_FR.pdf|Presentation finale FR]] - [[Media:RICM4_2017_2018_-_Serre_Connecte_Presentation_Final_EN.pdf|Final Presentation EN]] - [[Media:RICM4_2017_2018_-_Serre_Connecte_Mi_parcours_presentation.pdf|Presentation de mi-parcours]] - [[Media:RICM4_2017_2018_-_Serre_Connecte_Poster.pdf|Poster]]
|-

!scope="row"| 12
| [[I-Greenhouse]] : [[Serre connectée aquaponie]]
| SURIER GAROFALO Aurélien, FERREIRA Joffrey, OZENDA Thomas
| Nicolas Palix
| [[RICM4_2017_2018_-_IGreenHouse| Fiche]] - [[RICM4_2017_2018_-_IGreenHouse_/_SRS|SRS]] - [[IGreenHouse/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/12 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 13
| Projet "Plateforme de mise en relation pour les entrepreneurs sociaux"
| AUBERT Vincent, COURTIAL Julien
| Didier Donsez
| [[RICM4_2017_2018_-_Entrepreneur| Fiche]] - [[RICM4_2017_2018_-_Entrepreneur_AUBERT_COURTIAL/_SRS|SRS]] - [[RICM4_2017_2018_-_Entrepreneur_AUBERT_COURTIAL/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/13 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 14
| [[Chatbot pour borne d'accueil handicap]]
| AUCLAIR-CORDAT Julien, BAMBA Samuel
| Didier Donsez, Marie-Paule Balicco et Jérôme Maisonnasse (service accueil handicap COMUE UGA)
| [[RICM4_2017_2018_-_ChatBot| Fiche]] - [[RICM4_2017_2018_-_/_SRS|SRS]] - [[RICM4_2017_2018_-_/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/14 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 15
| Connected Shop (avec [[Eclipse SmartHome]])
| CUZIN Florian, ECHEVET Théo
| Didier Donsez
| [[RICM4_2017_2018_-Connected_shop| Fiche]] - [[RICM4_2017_2018_-_/_SRS|SRS]] - [[RICM4_2017_2018_-_Connected_Shops/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/15 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:Presentation_mi_soutenance_fr_Connected_Shops.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 16
| [[Deploiment Nucleo | Déploiement sécurisé et sans fil pour carte Nucleo]]
| CHANET Zoran, CHARLOT Servan
| Olivier Richard, Sylain Toru
| [[RICM4_2017_2018_-_Nucleo | Fiche]] - [[RICM4_2017_2018_-_Nucleo/_SRS|SRS]] - [[RICM4_2017_2018_-_Nucleo/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/16 gitlab]
| [[RICM4_2017_2018_|Rapport final]] - [[RICM4_2017_2018_|Presentation finale FR]] - [[RICM4_2017_2018_|Final Presentation EN]] - [[RICM4_2017_2018_|Flyer]] - [[Media:Projet_Nucleo_diapo_mi_parcours.pdf‎|Presentation de mi-parcours]]
|-

!scope="row"| 17.1
| [[RobAIR]] : Robot Majordome
| DEVOS Xavier, LAFRASSE Cédric
| Jérôme Maisonnasse, Germain Lemasson, Bastien Scher (FabMSTIC)
| [[RICM4_2017_2018_-_RobAIR17-1| Fiche]] - [[RICM4_2017_2018_-_RobAIRDL/_SRS|SRS]] - [[RICM4_2017_2018_-_RobAIRDL/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/17.1 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 17.2
| [[RobAIR]] : Robot Majordome
| JEAN Jordan, EZ-ZINE Najwa
| Jérôme Maisonnasse, Germain Lemasson, Bastien Scher (FabMSTIC)
| [[RICM4_2017_2018_-_robair2| Fiche]] - [[RICM4_2017_2018_-_robair2/_SRS|SRS]] - [[RICM4_2017_2018_-_robair2/UML | UML]]
| [https://gricad-gitlab.univ-grenoble-alpes.fr/Projet-RICM4/17-18/17.2 gitlab]
| [[Media:xxx.pdf|Rapport final]] - [[Media:xxx.pdf|Presentation finale FR]] - [[Media:xxx.pdf|Final Presentation EN]] - [[Media:xxx.pdf|Flyer]] - [[Media:xxx.pdf|Presentation de mi-parcours]]
|-

|}

==RICM5==
===Projet IoT S9===
Enseignants responsables : Bernard Tourancheau

Calendrier: ??? Septembre à ??? Décembre 2017.

* Projet IoT 3 : [[Ski-locator]] (Bernard Tourancheau)

===Projet Semestre S10===

Enseignants responsables : Didier Donsez

Calendrier: 29 Janvier à 15 Mars 2018.

Séances de Management de projets innovants:
* Mercredi 31/01 de 8h à 12h: Stéphanie Diligent
* Mercredi 7 février de 8h à 12h : Stéphanie Diligent
* Mardi 15 février de 8h à 12 : Emmanuelle Tréhoust
* Lundi 26 février de 8h à 12h : Olivier Gilles
* Mardi 13 mars de 8h à 12h : Stéphanie Diligent et Emmanuelle Tréhoust

Réunion de présentation : 8 Janvier 2018 Matin à 9H00-10H00 (RdV Salle P257 et Salle AIR P259). Faire couler le café.

Hackathon Vinci (8,9,10/02) : http://hacktogether.vinci-energies.com/

Démarrage : Lundi 29 Janvier 2018

Soutenance à mi-parcours : Mercredi 14 Février 2018, 8H00-11H00 (30 minutes par équipe).

Rendu rapport de management : Mardi 13 Mars 2018 - Matin

Soutenance (puis Pot de la fin) : Jeudi 15 Mars 2018

Vendredi 16 Mars : 10000 ans de RICM

==== Planning soutenances mi-parcours ====
Mercredi 14 Février 2018, salle P144, 8H00-11H00 (25 minutes TTC par équipe).

* 8H00-8H30 [[Real Time Subtitles 2017-2018| Real Time Subtitles]]
* 8H30-9H00 [[Deep Learning 2017-2018 | Deep Learning]]
* 9H00-9H30 [[EasyFlight_2017-2018|EasyFlight]]
* 9H30-10H00 [[ Réalité virtuelle et Augmentée pour la maintenance d'usines]]
* 10H00-10H30 [[R'Montagne]]
* 10H30-11H00 [[SmartMove]]
* 11H00-11H30 [[RICM5 2017 2018 - UGAChain|UGAChain]]

==== Planning soutenances finales ====
Jeudi 15 Mars 2018
Matin (Salle P251)
* 8H00-9H00 [[R'Montagne]] (50 minutes TTC)
* 9H00-10H00 [[SmartMove]] (50 minutes TTC)
* 10H00-11H00 (50 minutes TTC) [[ Réalité virtuelle et Augmentée pour la maintenance d'usines]]
* 11H00-12H00 (50 minutes TTC) [[RICM5 2017 2018 - UGAChain|UGAChain]] : Blockchain for Education
Pause déjeuner
Matin (Salle P249)
* 13H00-14H00 [[Real Time Subtitles 2017-2018| Real Time Subtitles]] (50 minutes TTC)
* 14H00-15H00 [[SmartRecruiting]] (50 minutes TTC)
* 15H00-16H00 [[EasyFlight_2017-2018|EasyFlight]] (50 minutes TTC)

====Instructions pour la soutenance====
* Chaque soutenance comporte 20 minutes de présentation, 10 minutes de question et 20 minutes de démonstration. Un transparent doit être consacré au travail confié et réalisé par les étudiants en DUT (AVOSTI) pour R'Montagne.
* La présentation est constituée des chapitres suivants:
** Rappel du sujet/besoin et cahier des charges
** Technologies employées
** Architecture techniques
** Réalisations techniques
** Gestion de projet (méthode, planning prévisionnel et effectif, gestion des risques, rôles des membres, ...)
** Outils (collaboration, CD/CI par exemple ...)
** Métriques logiciels : lignes de code, langages, performance, temps ingénieur (d'après vos journaux)...)
** Conclusion (Retour d'expérience)
** Transparent introduisant la démonstration
* Répétez plusieurs fois votre présentation et votre démonstration. Il y aura des personnalités invitées. Prévoyez un démonstration filmée pour palier à l'effet "démo".
* L'ensemble des documents (y compris photos, vidéos et ''[[Logiciels#Screencast|screencast]]s'') doivent être accessibles depuis le tableau ci-dessous et dans chaque fiche de suivi. Prévoyez une copie sur clé USB.
* Les étudiants de DUT vous accompagnent lors de votre soutenance et présenteront leur travail. Coordonnez vous avec eux et faites les répéter.
* '''TOUT Le matériel prêté devra être rapporté et restitué dans un sac cabas lors de la soutenance.'''

==== Affectations ====
{|class="wikitable alternance"
|+ Affectation des projets RICM5 2017-2018
|-
|
!scope="col"| Sujet
!scope="col"| Etudiants
!scope="col"| Enseignant(s)
!scope="col"| Fiche de suivi
!scope="col"| Dépot git
|-

!scope="row"| 1
| [[Real Time Subtitles 2017-2018| Sous-titre d'un cours en temps réel]]
| '''Estelle ALLARD''' / Aymeric BROCHIER / Louis COCHINHO / Oriane DALLE / Alexandre FERRERA / Alice RIVOAL
| Didier Donsez, Laurent Besacier, François Portet, Marie-Paule Balicco, Jérome Maisonnasse
| [[Real Time Subtitles 2017-2018| Fiche]] - [[Real_Time_Subtitles_2017-2018/SRS|SRS]]
| [https://gitlab.com/LouisCochinho/RealTimeSubtitles GitLab]
| [[Media:RICM5_2017_2018_Real_time_subtitles_rapport.pdf|Rapport final]] - [[Media:RICM5_2017_2018_Real_time_subtitles_slides.pdf|Presentation finale]] - [[Media:RICM5_2017_2018_Real_time_subtitles_mi.pdf|Presentation de mi-parcours]] - [[Media:RICM5_2017_2018_Real_time_subtitles_flyer.pdf|Flyer]] - [[Media:RICM5_2017_2018_Real_time_subtitles_poster.pdf|Poster]] - [[Media:Demo_RealTimeSubtitles.rar|Video]]

|-

!scope="row"| 2
| [[Réalité Augmentée pour le Smart Campus 2018|Réalité Augmentée pour le Smart Campus]]
| Lucas LESAGE / '''Denis LACHARTRE''' / Douria ZENNOUCHE / Gilles BONHOURE / Maxime DEREYMEZ
| Didier Donsez, Georges-Pierre Bonneau
| [[Campus_Augmente_2017-2018|Fiche]] - [[Media:SRS_ProjetAR_2018.pdf|SRS]]
| [https://github.com/ProjetS10-CyberHoloMachin Organisation Git]
| [[Media:Guide_developpeur_ProjetAR_2018.pdf|Guide developpeur]] - [[Media:Presentation_finale_ProjetAR_2018.pdf|Presentation finale ]] -[[Media : Cyberposter_ProjetAR_2018.pdf | Poster]] - [[Media:Rapport_final_MPI_ProjetAR_2018.pdf‎ | Rapport final MPI ]] - [[Media:Guide_utilisateur_ProjetAR_2018.pdf|Guide utilisateur]]- [[Media:Presentation_Mi_parcours_ProjetAR_2018.pdf|Presentation de mi-parcours]] - [http://youtulle.com/XXXX Vidéo 1]
|-

!scope="row"| 3
| SmartRecruiting : [[SmartRecruiting|Deep Learning]] avec [[TensorFlow]] sur les référentiels de compétence
| Héloise FERNANDES DE ALMEIDA / '''Romane GALLIER''' / Alicia AUBERTIN / Antoine GAMBRO / Qianqian FU
| Didier Donsez
| [[SmartRecruiting| Fiche]] - [[SmartRecruiting/SRS|SRS]]
| [https://github.com/Projet-DeepLearning-RICM5-2018 Organisation Git]
| [[Media:RICM5_2017_2018_DeepLearning_rapport.pdf|Rapport final]] - [[Media:RICM5_2017_2018_DeepLearning_presentation.pdf|Presentation finale]] - [[Media:RICM5_2017_2018_DeepLearning_mi-parcours.pdf|Presentation de mi-parcours]]
|-

!scope="row"| 4
| [[RICM5 2017 2018 - UGAChain|UGAChain]] : Blockchain for Education
| Charles MARCHAND / '''Antoine BOISADAM''' / Ahmed NASSIK / Simon CHAMBONNET / Lucas GUERRY / Aymeric VIAL-GRELIER
| Didier Donsez & co
| style="white-space: nowrap;"|[[RICM5 2017 2018 - UGAChain| Fiche]] - [[RICM5 2017 2018 - UGAChain /_SRS|SRS]]
| [https://github.com/RICM5-BlockChain Github]
| [[Media:RICM5_2017_2018_-_UGAChain_-_Rapport_MPI.pdf|Rapport final]] - [[Media:RICM5_2017_2018_UGAChain_-_Soutenance_fianale.pdf|Présentation finale]] - [[Media:RICM5_2017_2018_UGAChain_-_Soutenance_mi-parcours.pdf|Présentation de mi-parcours]] - [[Media:RICM5_2017_2018_UGAChain-Flyer.pdf|Flyer]] - [[Media:RICM5_2017_2018_XXXX_poster.pdf|Poster]] - [http://youtulle.com/XXXX Vidéo 1]
|-

!scope="row"| 5
| [[R'Montagne]]
| '''Hugo AMODRU-FAVIN''' / Antoine DELISE / Gwenaël MOREAU
| Bernard Tourancheau
| [[R'Montagne| Fiche]] - [[RICM5_2017_2018_-_RMontagne_/_SRS|SRS]]
| [https://github.com/delisea/R-Montagne Github]
| [[Media:RICM5_2017_2018_RMontagne_MPI.pdf|Rapport final]] - [[Media:RICM5_2017_2018_RMontagne.pdf|Presentation finale ]] - [[Media:RICM5_2017_2018_RMontagne_MiParcours.pdf|Presentation de mi-parcours]] - [[Media:RICM5_2017_2018_RMontagne_Flyer.pdf|Flyer/Poster]] - [http://youtulle.com/XXXX Vidéo 1]
|-

!scope="row"| 6
| [[SmartMove]]
| '''Anthony GEOURJON''' / Timothée LEMAIRE / Clément ROUQUIER / Vincent TURRIN
| Bernard Tourancheau
| [[RICM5_2017-2018 - SmartMove| Fiche]] - [[RICM5_2017-2018-SmartMove-SRS|SRS]]
| [https://github.com/orgs/SmartMove-PolytechGrenoble/dashboard Github]
| [[Media:RICM5_2017_2018_XYZ.pdf|Rapport final]] - [[Media:RICM5_2017_2018_SmartMove.pdf|Presentation finale]] - [[Media:RICM5_2017_2018_XYZ.pdf|Presentation de mi-parcours]] - [[Media:RICM5_2017_2018_XXXX_flyer.pdf|Flyer]] - [[Media:RICM5_2017_2018_XXXX_poster.pdf|Poster]] - [http://youtulle.com/XXXX Vidéo 1]
|-

!scope="row"| 7
| [[EasyFlight 2017-2018|EasyFlight]]
| '''Boris ODIEVRE''' / Remi SAVARY / Lambert ROCHER / Hervé BECHER
| Didier Donsez
| [[EasyFlight_2017-2018/Fiche_de_suivi| Fiche]] - [[RICM5_2017-2018-EasyFlight-SRS|SRS]]
| [https://github.com/lambertrocher/EasyFlight Github]
| [[Media:RICM5_2017_2018_XYZ.pdf|Rapport final]] - [[Media:RICM5_2017_2018_XYZ.pdf|Presentation finale]] - [[Media:RICM5_2017_2018_XYZ.pdf|Presentation de mi-parcours]] - [[Media:RICM5_2017_2018_XXXX_flyer.pdf|Flyer]] - [[Media:RICM5_2017_2018_XXXX_poster.pdf|Poster]] - [http://youtulle.com/XXXX Vidéo 1]
|-

|}

==== Sujets non choisis ====
* [[Contributions open-source au projet JHipster]] (Didier Donsez)
* [[Contributions à Software Heritage]] (Didier Donsez and co)
* Projet IoT 3 : [[Ski-locator]] (Bernard Tourancheau)

= Projets collectifs MAT/IESE =

== Années 3 et 4 ==

* [[ASAC/SJC|Serres connectées @ Jardin du coteau]]
* [[ASAC/GEJC|Gestion de l'eau @ Jardin du coteau]]
* [[ASAC/AP|Aquaponie @ Polytech]]

=[[Projets M2PGI Services Machine-to-Machine et Internet-of-Things]]=
==[[PM2M/2018/TP|PM2M]]==

RICM4 2017 2018 - ChatBot

2018-04-08T08:45:54Z

Julien.Cordat-Auclair:

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better and more adaptive technology.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

== Week 5 - 12, 16 Feb. ==

Getting familiar with the Messenger platform:
* Samuel learned how to implement a chatbot on the platform [https://developers.facebook.com/docs/messenger-platform/getting-started/quick-start]
* Samuel started to code some basic exemples and test it on a Facebook page created on purpose
* Julien kept working on the conversation tree

== Week 6 - 17, 25 Feb. ==

The same work as the previous week has been done.

== Week 7 - 26, 4 Mar. ==

Kept working on the two major aspects of the project:
* Localhosted API development in Node.js and Express.js
* MongoDB database connection to store the users' answers, which will be really useful for the SAH (namely with the forms)
* Julien finished to build the conversation tree

== Week 8 - 5, 11 Feb. ==

* Implementation of the disabled persons form in Glitch server
* State graph of the conversation tree added into our chatbot.

RICM4 2017 2018 /!\ ChatBot

2018-04-08T08:40:51Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 /!\ ChatBot to RICM4 2017 2018 : ChatBot

#REDIRECT [[RICM4 2017 2018 : ChatBot]]

RICM4 2017 2018 : ChatBot

2018-04-08T08:40:51Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 /!\ ChatBot to RICM4 2017 2018 : ChatBot

RICM4 2017 2018 --ChatBot

2018-04-08T08:40:25Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 --ChatBot to RICM4 2017 2018 - ChatBot over redirect

#REDIRECT [[RICM4 2017 2018 - ChatBot]]

RICM4 2017 2018 - ChatBot

2018-04-08T08:40:25Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 --ChatBot to RICM4 2017 2018 - ChatBot over redirect

#REDIRECT [[RICM4 2017 2018 /!\ ChatBot]]

RICM4 2017 2018 -ChatBot

2018-04-08T08:38:27Z

Julien.Cordat-Auclair:

RICM4 2017 2018 - ChatBot

2018-04-08T08:36:52Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 --ChatBot to RICM4 2017 2018 /!\ ChatBot

#REDIRECT [[RICM4 2017 2018 /!\ ChatBot]]

RICM4 2017 2018 : ChatBot

2018-04-08T08:36:52Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 --ChatBot to RICM4 2017 2018 /!\ ChatBot

RICM4 2017 2018 -ChatBot

2018-04-08T08:34:52Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 -ChatBot to RICM4 2017 2018 ChatBot

#REDIRECT [[RICM4 2017 2018 ChatBot]]

RICM4 2017 2018 ChatBot

2018-04-08T08:34:52Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 -ChatBot to RICM4 2017 2018 ChatBot

RICM4 2017 2018 : ChatBot

2018-04-08T08:34:32Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - ChatBot to RICM4 2017 2018 --ChatBot

RICM4 2017 2018 : ChatBot

2018-04-08T08:32:35Z

Julien.Cordat-Auclair:

RICM4 2017 2018 ChatBot

2018-03-12T12:44:12Z

Julien.Cordat-Auclair:

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better and more adaptive technology.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

== Week 5 - 12, 16 Feb. ==

Getting familiar with the Messenger platform:
* Samuel learned how to implement a chatbot on the platform
* Samuel started to code some basic exemples and test it on a Facebook page created on purpose
* Julien kept working on the conversation tree

== Week 6 - 17, 25 Feb. ==

The same work as the previous week has been done.

== Week 7 - 26, 4 Mar. ==

Kept working on the two major aspects of the project:
* Samuel managed to find a way to save the users' answers, which will be really useful for the SAH (namely with the forms)
* Julien finished to build the conversation tree

== Week 8 - 5, 11 Feb. ==

We started to implement the conversation tree into our chatbot.

RICM4 2017 2018 ChatBot

2018-03-12T12:43:20Z

Julien.Cordat-Auclair: Blanked the page

RICM4 2017 2018-ChatBot

2018-03-12T12:39:42Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018-ChatBot to RICM4 2017 2018 - ChatBot over redirect

#REDIRECT [[RICM4 2017 2018 - ChatBot]]

RICM4 2017 2018 : ChatBot

2018-03-12T12:39:42Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018-ChatBot to RICM4 2017 2018 - ChatBot over redirect

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better and more adaptive technology.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

== Week 5 - 12, 16 Feb. ==

Getting familiar with the Messenger platform:
* Samuel learned how to implement a chatbot on the platform
* Samuel started to code some basic exemples and test it on a Facebook page created on purpose
* Julien kept working on the conversation tree

== Week 6 - 17, 25 Feb. ==

The same work as the previous week has been done.

== Week 7 - 26, 4 Mar. ==

Kept working on the two major aspects of the project:
* Samuel managed to find a way to save the users' answers, which will be really useful for the SAH (namely with the forms)
* Julien finished to build the conversation tree

== Week 8 - 5, 11 Feb. ==

We started to implement the conversation tree into our chatbot.

RICM4 2017 2018 : ChatBot

2018-03-12T12:39:10Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - ChatBot to RICM4 2017 2018-ChatBot

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better and more adaptive technology.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

== Week 5 - 12, 16 Feb. ==

Getting familiar with the Messenger platform:
* Samuel learned how to implement a chatbot on the platform
* Samuel started to code some basic exemples and test it on a Facebook page created on purpose
* Julien kept working on the conversation tree

== Week 6 - 17, 25 Feb. ==

The same work as the previous week has been done.

== Week 7 - 26, 4 Mar. ==

Kept working on the two major aspects of the project:
* Samuel managed to find a way to save the users' answers, which will be really useful for the SAH (namely with the forms)
* Julien finished to build the conversation tree

== Week 8 - 5, 11 Feb. ==

We started to implement the conversation tree into our chatbot.

RICM4 2017 2018 : ChatBot

2018-03-12T12:38:26Z

Julien.Cordat-Auclair: /* Week 3 - 29, 4 Feb. */

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better and more adaptive technology.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

== Week 5 - 12, 16 Feb. ==

Getting familiar with the Messenger platform:
* Samuel learned how to implement a chatbot on the platform
* Samuel started to code some basic exemples and test it on a Facebook page created on purpose
* Julien kept working on the conversation tree

== Week 6 - 17, 25 Feb. ==

The same work as the previous week has been done.

== Week 7 - 26, 4 Mar. ==

Kept working on the two major aspects of the project:
* Samuel managed to find a way to save the users' answers, which will be really useful for the SAH (namely with the forms)
* Julien finished to build the conversation tree

== Week 8 - 5, 11 Feb. ==

We started to implement the conversation tree into our chatbot.

RICM4 2017 2018 : ChatBot

2018-03-12T12:37:44Z

Julien.Cordat-Auclair: /* Week 8 - 5, 11 Feb. */

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better solution.

Meanwhile, we kept building our conversation tree.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

== Week 5 - 12, 16 Feb. ==

Getting familiar with the Messenger platform:
* Samuel learned how to implement a chatbot on the platform
* Samuel started to code some basic exemples and test it on a Facebook page created on purpose
* Julien kept working on the conversation tree

== Week 6 - 17, 25 Feb. ==

The same work as the previous week has been done.

== Week 7 - 26, 4 Mar. ==

Kept working on the two major aspects of the project:
* Samuel managed to find a way to save the users' answers, which will be really useful for the SAH (namely with the forms)
* Julien finished to build the conversation tree

== Week 8 - 5, 11 Feb. ==

We started to implement the conversation tree into our chatbot.

RICM4 2017 2018 : ChatBot

2018-03-12T12:37:30Z

Julien.Cordat-Auclair:

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better solution.

Meanwhile, we kept building our conversation tree.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

== Week 5 - 12, 16 Feb. ==

Getting familiar with the Messenger platform:
* Samuel learned how to implement a chatbot on the platform
* Samuel started to code some basic exemples and test it on a Facebook page created on purpose
* Julien kept working on the conversation tree

== Week 6 - 17, 25 Feb. ==

The same work as the previous week has been done.

== Week 7 - 26, 4 Mar. ==

Kept working on the two major aspects of the project:
* Samuel managed to find a way to save the users' answers, which will be really useful for the SAH (namely with the forms)
* Julien finished to build the conversation tree

== Week 8 - 5, 11 Feb. ==

We started to implement the converation tree into our chatbot.

RICM4 2017 2018 : ChatBot

2018-03-12T12:28:33Z

Julien.Cordat-Auclair:

= Project presentation =

The project subject : [https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better solution.

Meanwhile, we kept building our conversation tree.

== Week 4 - 5, 11 Feb. ==

We met Marie-Paule Balicco, director of the SAH, in order to talk about our project.

She told us that the tablet wasn't currently available.

Hence, we had no support at all (nor Rasa or the tablet) to work with and we had to find something new.

Redefining our work:
* We thought about creating a Facebook page for the SAH
* We thought about using Facebook Messenger in order to use our chatbot
* We throwed ideas our chatbot could talk about and which it would make it easier for the SAH to get in touch with the students (forms)

At this point, we decided to implement our bot on [https://fr-fr.messenger.com/ Facebook Messenger] as well as creating a Facebook page for the SAH, which would help SAH's team a lot with administrative work.

RICM4 2017 2018 ChatBot

2018-03-12T12:19:57Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 -ChatBot to RICM4 2017 2018 - ChatBot

#REDIRECT [[RICM4 2017 2018 - ChatBot]]

RICM4 2017 2018 : ChatBot

2018-03-12T12:19:57Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 -ChatBot to RICM4 2017 2018 - ChatBot

RICM4 2017 2018 -

2018-03-12T12:19:17Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - to RICM4 2017 2018 -ChatBot

#REDIRECT [[RICM4 2017 2018 -ChatBot]]

RICM4 2017 2018 : ChatBot

2018-03-12T12:19:17Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - to RICM4 2017 2018 -ChatBot

RICM4 2017 2018 : ChatBot

2018-03-12T12:18:33Z

Julien.Cordat-Auclair: /* Project presentation */

RICM4 2017 2018 : ChatBot

2018-03-12T12:18:23Z

Julien.Cordat-Auclair: /* Project presentation */

= Project presentation =

The project subject : [[https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap ChatBot]].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better solution.

Meanwhile, we kept building our conversation tree.

== Week 3 - 5, 11 Feb. ==

RICM4 2017 2018 : ChatBot

2018-03-12T12:17:22Z

Julien.Cordat-Auclair: /* Calendar */

= Project presentation =

The project subject : [[ChatBot]].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 15th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better solution.

Meanwhile, we kept building our conversation tree.

== Week 3 - 5, 11 Feb. ==

RICM4 2017 2018 : ChatBot

2018-03-12T12:16:50Z

Julien.Cordat-Auclair:

= Project presentation =

The project subject : [[ChatBot]].

The project consist of creating a chatbot which would be able to lead a conversation with a human being.

This bot will help the [https://handicap.univ-grenoble-alpes.fr/ SAH] (which stands for Service Accueil Handicap, located in Grenoble, France) to collect data about the users, namely thanks to forms.

During his conversation with the bot, the user will have access to different services :
* registering in the SAH by completing a form with the help of the bot
* asking for informations about the SAH

Two main constrains :
* the bot must be able to lead a conversation with disabled people
* it will be deployed on Facebook Messenger, which means the user must have a Facebook account

The original project mentionned that the chatbot had to be deployed on a tablet which is at the SAH, but this tablet is currently not availble and it's already used by another team of engineers.

= Team =

* Supervisor: [http://lig-membres.imag.fr/donsez/ Didier Donsez]

* Members: Julien Cordat-Auclair, Samuel Bamba

* Department: [http://www.polytech-grenoble.fr/ricm.html RICM4] (Polytech Grenoble)

= Calendar =
The project started on January 22th, 2018.

== Week 1 - 15, 21 Jan. ==

Subjects were assigned.

First approach of the project:
* We collected a lot of documentation about chatbots
* We browsed [https://rasa.com/ Rasa]'s website, which was the library we had to use for our project
* We started to build the conversation tree

== Week 2 - 22, 28 Jan. ==

Getting familiar with Rasa:
* We installed the required tools to use Rasa properly
* We started to use Rasa by doing simple tests
* We continued to build the conversation tree

== Week 3 - 29, 4 Feb. ==

During this week, we met Dider Donsez as well as an enginner who worked on this project at the [http://fabmstic.liglab.fr/ FabLab].

We've been tought how to implement the chatbot on the tablet in stock at the SAH.

We've also been told that Rasa wasn't the optimal solution to build our chatbot, so we had to find another solution that would be less constraining.

Hence, we left the idea of using Rasa and started to look for a better solution.

Meanwhile, we kept building our conversation tree.

== Week 3 - 5, 11 Feb. ==

RICM4 2017 2018 - ChatBot / UML

2018-03-11T18:09:51Z

Julien.Cordat-Auclair:

[[File:ChatBot - UML - UseCase.jpg|center]]

File:ChatBot - UML - UseCase.jpg

2018-03-11T18:08:22Z

Julien.Cordat-Auclair:

RICM4 2017 2018 - ChatBot / UML

2018-03-11T18:08:04Z

Julien.Cordat-Auclair:

=Use Case=

[[File:ChatBot - UML - UseCase.jpg|center]]

=Sequence Diagram=

RICM4 2017 2018 - ChatBot / UML

2018-03-11T17:11:53Z

Julien.Cordat-Auclair:

=Use Case=

=Sequence Diagram=

RICM4 2017 2018 - /UML

2018-03-11T17:11:12Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - /UML to RICM4 2017 2018 - ChatBot / UML

#REDIRECT [[RICM4 2017 2018 - ChatBot / UML]]

RICM4 2017 2018 - ChatBot / UML

2018-03-11T17:11:12Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - /UML to RICM4 2017 2018 - ChatBot / UML

=Use case=

=Sequence Diagram=

RICM4 2017 2018 - ChatBot / UML

2018-03-11T17:11:02Z

Julien.Cordat-Auclair: Created page with "=Use case= =Sequence Diagram="

=Use case=

=Sequence Diagram=

RICM4 2017 2018 - / SRS

2018-03-11T17:04:19Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - / SRS to RICM4 2017 2018 - ChatBot / SRS

#REDIRECT [[RICM4 2017 2018 - ChatBot / SRS]]

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T17:04:19Z

Julien.Cordat-Auclair: Julien.Cordat-Auclair moved page RICM4 2017 2018 - / SRS to RICM4 2017 2018 - ChatBot / SRS

This document is inspired by the following file : http://www.math.uaa.alaska.edu/~afkjm/cs401/IEEE830.pdf.

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students.

Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
* The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap

* The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector.

Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton.

It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.

It also needs to collect some important informations about the user it’s discussing with.

This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users.
Web hosting, database and user files.

==2.5 Assumptions and dependencies==
The disabled student must have an access to a smartphone or a computer in order to use the application.

=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 1 : ==
'''Function''':

'''Description''':

'''Inputs''':

'''Source''':

'''Outputs''':

'''Destination''':

'''Action''':

'''Non functional requirements''':

'''Pre-condition''':

'''Post-condition''':

'''Side-effects''':

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
'''SRS related documents used to establish this page :'''

* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:58:45Z

Julien.Cordat-Auclair:

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:58:23Z

Julien.Cordat-Auclair:

This document is inspired by the following file : http://www.math.uaa.alaska.edu/~afkjm/cs401/IEEE830.pdf

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students.

Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
* The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap

* The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector.

Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton.

It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.

It also needs to collect some important informations about the user it’s discussing with.

This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users.
Web hosting, database and user files.

==2.5 Assumptions and dependencies==
The disabled student must have an access to a smartphone or a computer in order to use the application.

=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 1 : ==
'''Function''':

'''Description''':

'''Inputs''':

'''Source''':

'''Outputs''':

'''Destination''':

'''Action''':

'''Non functional requirements''':

'''Pre-condition''':

'''Post-condition''':

'''Side-effects''':

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
'''SRS related documents used to establish this page :'''

* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:55:35Z

Julien.Cordat-Auclair:

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

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students.

Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
* The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap

* The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector.

Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton.

It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.

It also needs to collect some important informations about the user it’s discussing with.

This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users.
Web hosting, database and user files.

==2.5 Assumptions and dependencies==
The disabled student must have an access to a smartphone or a computer in order to use the application.

=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 1 : ==
'''Function''':

'''Description''':

'''Inputs''':

'''Source''':

'''Outputs''':

'''Destination''':

'''Action''':

'''Non functional requirements''':

'''Pre-condition''':

'''Post-condition''':

'''Side-effects''':

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
'''SRS related documents used to establish this page :'''

* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:54:06Z

Julien.Cordat-Auclair:

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

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students.

Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
* The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap

* The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector.

Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton.

It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.

It also needs to collect some important informations about the user it’s discussing with.

This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users.
Web hosting, database and user files.

==2.5 Assumptions and dependencies==
The disabled student must have an access to a smartphone or a computer in order to use the application.

=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 1 : ==
'''Function''':

'''Description''':

'''Inputs''':

'''Source''':

'''Outputs''':

'''Destination''':

'''Action''':

'''Non functional requirements''':

'''Pre-condition''':

'''Post-condition''':

'''Side-effects''':

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:50:07Z

Julien.Cordat-Auclair:

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

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students.

Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
* The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap

* The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector.

Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton.

It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.

It also needs to collect some important informations about the user it’s discussing with.

This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users.
Web hosting, database and user files.

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:42:11Z

Julien.Cordat-Auclair:

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

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students.

Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap

The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector.

Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton.

It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.

It also needs to collect some important informations about the user it’s discussing with.

This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users.
Web hosting, database and user files.

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:41:26Z

Julien.Cordat-Auclair:

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

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students.
Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.
The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap
The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector.
Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton.
It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.
It also needs to collect some important informations about the user it’s discussing with.
This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users.
Web hosting, database and user files.

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:40:00Z

Julien.Cordat-Auclair: /* 1.4 References */

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

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR. It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students. Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap
The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector. Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton. It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have. It also needs to collect some important informations about the user it’s discussing with. This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users. Web hosting, database and user files.

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-03-11T16:39:23Z

Julien.Cordat-Auclair:

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

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
The SRS is a document describing the software system of our DashBoard project for OAR. It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
The “Service d’Accueil Handicap” (Disabled Welcoming Service) located in Saint-Martin d’Hères allows more than 900 residents each year to benefit from personal advices and support services for disabled students. Due to a strong affluence and limited space, a need for automation has been felt by the SAH’s team.

The ChatBot project aims to provide a solution to this problem.

==1.3 Definitions, acronyms and abbreviations==
A ChatBot is a conversation program which conducts a conversation via auditory or textual methods.

==1.4 References==
The main page of the project: https://air.imag.fr/index.php/Chatbot_pour_borne_d%27accueil_handicap
The UML:

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
Getting involved in other institutions linked to the health sector. Building a system capable of recognizing vocal phrases for visually impaired individuals.

==2.2 Product functions==
Providing an answer adapted to the requests of a disabled user thanks to an automaton. It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have. It also needs to collect some important informations about the user it’s discussing with. This conversation will take place on a web/mobile app.

==2.3 User characteristics==
Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

==2.4 General constraints==
Disablement of users. Web hosting, database and user files.

==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=
Not acting only for disabled students but also for a wider pool of individuals.

=5. Appendices=
=6. Index=