Différences

Ci-dessous, les différences entre deux révisions de la page.

--- projets:ocs:20142015:gr8 [2015/01/12 20:37] – [Scenarios of the Project] palma
+++ projets:ocs:20142015:gr8 [2015/02/18 09:40] (Version actuelle) – [Software Specifications and Distribution of the connected Object] palma
@@ Ligne 45: / Ligne 45: @@
 Actually there are plenty of applications that can use our simple buzzer and light and divert from the primary //object// usage.
-=== 3. Configure the AlarmLight application from User's smartphone and BT interface ===
-The //object// could be enhanced with a bluetooth interface.
-Then, from an application installed in his smartphone Bob can configure the AlarmLight application with his agenda login/password, his preferences (minimum wake-up time before an appointment, address, etc...).
 ==== Connected Object Description (Nice students proposal) ====
 == Specification ==
@@ Ligne 126: / Ligne 123: @@
 ==== Software Specifications and Distribution of the connected Object ====
+== Overview ==
-// BE CAREFUL : minimal logic must be embedded in the object. The main purpose of the object is to provide access to the its actuators and sensors//
+{{http://image.noelshack.com/fichiers/2015/08/1424249546-16374577289-5827311736-o.png?600x150}}
 == Software Specifications of the connected Object ==
@@ Ligne 133: / Ligne 131: @@
 ** Web Service for Device Specifications **
-// add the description of the Web Service for Device interface of the connected Object //
+ The main purpose of the object is to give acces to its services through UPnP protocol. In our case, the UPnP services are :
+	- Turning on and off the light.
+	- Turning on and off the alarm.
+	- The current State of the light.
+	- The current State of the alarm.
+ In addition of the above, the object owns a physical interface which consists of a touch sensor. This embedded actuator provide the following features:
+	- If the alarm is turned off, each pressure alternately switch on and off the light with each pressure.
+	- If the alarm and light are on, the next pressure turns off the alarm without switching off the light.
+	- If the alarm is on and the light is off, the next pressure turns off the alarm and switch on the light.
 ** Application Protocol over Bluetooth link of the object  **
@@ Ligne 153: / Ligne 161: @@
     * Binary distribution of the developed software for the object and how to install (ex. DLL of new beans and wcc of the WComp the assembly) :
     * Sources distribution of the developed software  and how to build the binary distribution (ex. sources of new beans for WComp):
-// including the list and the  links for all prerequired software //
-  * Mobile Phone Software
-    * The kind of  smart phone that you chose (Reference, Android ? IoS ? Windows Phone X.X ?)
-    * Binary distribution of the developed software for the phone and how to install  :
-    * Sources distribution of the developed software  and how to build the binary distribution :
 // including the list and the  links for all prerequired software //
-==== Software Specifications and Distribution of the high level service for the user ====
+wcc of the embedded software:
-// BE CAREFUL : Here is the main purpose of your project. //
+ [[https://drive.google.com/open?id=0ByF5Pdi4nQlASDNuVUhGU3k3OUU&authuser=0]]
-// BE CAREFUL : The connected object is only a part of the composition/orchestration between other services to build a high level service //
+Beans to install in Bean/ directory in the embedded device
-// BE CAREFUL : Don't forget that the added value and intelligence of the high level service are based on the use of multiple web services like meteo / agenda ... //
+ [[https://drive.google.com/open?id=0ByF5Pdi4nQlAVEVBMEFfS1VRYlU&authuser=0]]
-// BE CAREFUL : The use of a user  terminal and any other Man Machine interface in order to use directly the object is not the purpose of this module //
+Sources of the embedded Beans:
+ [[https://drive.google.com/open?id=0ByF5Pdi4nQlASzdfd1RCcWJaLU0&authuser=0]]
-== Software Specifications of the High Level Service for the user ==
-// add the description of Specifications of the High Level Service for the user //
+  * Mobile Phone Software
+    * The kind of  smart phone that you chose (Reference, Android ? IoS ? Windows Phone X.X ?)
+    * Binary distribution of the developed software for the phone and how to install  :
+    * Sources distribution of the developed software  and how to build the binary distribution :
+// including the list and the  links for all prerequired software //
+==== Software Specifications and Distribution of the high level service for the user ====
-// including the lsit of the Web Services you use to design new High Level functionalities for the user //
-// Example: use of Meteo Web Service to manage the watering of a plant equiped with a connected object //
+== Software Specifications of the High Level Service for the user ==
+The high level service orchestrates the three following WebServices :
+	* Calendar WebService, in our case, Google Calendar. This service is used to know the time of the first user appointement in the morning.
+	* LiveMap WebService,
 == Software Distribution of the High Level Service for the user ==
@@ Ligne 188: / Ligne 197: @@
     * Binary distribution of the developed software for the object and how to install (ex. DLL of new beans and wcc of the WComp the assembly) :
     * Sources distribution of the developed software  and how to build the binary distribution (ex. sources of new beans in WComp):
+wcc of the orchestration software :
+https://drive.google.com/open?id=0ByF5Pdi4nQlAYVExbEZ6RFNUek0&authuser=0
+bridge application for the Google Calendar WebService:
+https://drive.google.com/file/d/0ByF5Pdi4nQlAb2QwUUM1QTFnQ0k/view?usp=sharing
+Beans to add in Bean/ directory:
+https://drive.google.com/file/d/0ByF5Pdi4nQlAcDdjOXZzakVLQnM/view?usp=sharing
+Sources of the Beans :
+https://drive.google.com/file/d/0ByF5Pdi4nQlAYVBGOGNvU0ppMnM/view?usp=sharing