Outils pour utilisateurs
projets:oc:oc_2013_2014:ubiquidouche
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
|
projets:oc:oc_2013_2014:ubiquidouche [2014/02/19 19:56] etudiant_oc_2013_2014 [Specifications and interface of the service on the object] |
projets:oc:oc_2013_2014:ubiquidouche [2014/02/19 20:58] (Version actuelle) etudiant_oc_2013_2014 [Object Shape :] |
||
|---|---|---|---|
| Ligne 9: | Ligne 9: | ||
| == Group Composition : == | == Group Composition : == | ||
| BOURSIER Alexandre | BOURSIER Alexandre | ||
| + | |||
| CACCIUTTOLO Olivier | CACCIUTTOLO Olivier | ||
| + | |||
| MARIE Aurélien | MARIE Aurélien | ||
| Ligne 52: | Ligne 54: | ||
| [[https://drive.google.com/file/d/0B4GQO5e_oFeKMnc2aXZMUFkwV1U/edit?usp=sharing]] | [[https://drive.google.com/file/d/0B4GQO5e_oFeKMnc2aXZMUFkwV1U/edit?usp=sharing]] | ||
| + | |||
| == Demonstration Video : == | == Demonstration Video : == | ||
| + | |||
| + | [[https://docs.google.com/file/d/0B4GQO5e_oFeKQnczVDdjRlU3MmM]] | ||
| ==== Hardware specifications : ==== | ==== Hardware specifications : ==== | ||
| Ligne 77: | Ligne 82: | ||
| The high added value service is connected to an UPnP proxy. When the service has received the three informations, it first writes them in a text file. Then the service converts the informations in JSON format. Then it makes a call to a weather service, a humidity service and a calendar service. All informations collected through those services are written in a CSV file. | The high added value service is connected to an UPnP proxy. When the service has received the three informations, it first writes them in a text file. Then the service converts the informations in JSON format. Then it makes a call to a weather service, a humidity service and a calendar service. All informations collected through those services are written in a CSV file. | ||
| + | |||
| + | You can see the data received by the service in C:\ubi\ubi_records.data (open with a text editor like notepad++). The CSV file is also in C:\ubi. | ||
| [[https://docs.google.com/file/d/0B4GQO5e_oFeKWkY2U1laS3dpZ1E/edit]] | [[https://docs.google.com/file/d/0B4GQO5e_oFeKWkY2U1laS3dpZ1E/edit]] | ||
| Ligne 137: | Ligne 144: | ||
| ==== Results of the relations with Reims (being factual without personal opinion) ==== | ==== Results of the relations with Reims (being factual without personal opinion) ==== | ||
| + | In the beginning the relations worked fine. The contact seemed to understand our expectations. at the beginning there was a real exchange on both sides. | ||
| + | |||
| + | However, thereafter, the design has often been conducted unilaterally. When we asked for a picture of our modeled object, only the showerhead itself was shown to us. Then the surprise was to see that he was part of a complete wall bracket. The contact imposed his choices to us, explaining a lack of time on his side. We understand that time is an important factor, but a communication as its design steps were going on would have been welcome. | ||
| + | |||
| + | Finally, the modeling that was sent to us didn't really looked like the object that we received. | ||
| + | |||
| + | We regret that the assembly takes hardly even glued as indicated in the instructions. In addition, it is difficult to keep our object vertically. | ||
| ==== Prospects : ==== | ==== Prospects : ==== | ||
| == Possible extensions of the object == | == Possible extensions of the object == | ||
| + | |||
| + | We don't get the average water flow. The values returned by the sensor seem random. For a future implementation, it would be great to get a significative value. Then we would be able to give information about the average consumption of water. | ||
| + | |||
| + | We could also add a accelerometer. Then we would be able to tell if the user take the showerhead in hand or let it on the wall. It might be relevant of his mood. | ||
| + | |||
| == Possible extension of the service on the Object == | == Possible extension of the service on the Object == | ||
| + | |||
| + | If we get a correct water flow value, we could give the average consumption by shower. | ||
| + | We could also connect this service to others outside the bathroom to know if someone, or something, interrupt a shower. By this way, the user wouldn't have spend as much time as he would like and might get frustrated. | ||
| + | |||
| == Possible extension of the high added value Service == | == Possible extension of the high added value Service == | ||
| + | |||
| + | Possible extension is a more services called to get more informations. For example, you could call like an electric service to calculate how much cost you a shower. A tenant might be interessed in that information to control his spendings. | ||
| + | |||
| == Possible GUI for data visualization == | == Possible GUI for data visualization == | ||
| + | There could be a dashboard in the bathroom were informations from the other services would be displayed. The dashboard would get turned on at the end of the shower with the evend send by the embedded service. Also we could give him a graph like produced in the CSV, even if a doctor would be more interesseted than the user himself. From this dashboard, he could consult a historic od the datas and also send it to his doctor. | ||
projets/oc/oc_2013_2014/ubiquidouche.1392836214.txt.gz · Dernière modification: 2014/02/19 19:56 par etudiant_oc_2013_2014
Outils de la page
Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : CC Attribution-Noncommercial-Share Alike 4.0 International
