In this Chapter the work to be done during this semester, regarding this dissertation is explained. First off all, the thorough list of upcoming tasks is shown in Section Tasks. Then, the scaling of those tasks, with the accompanying Gantt chart is present in Scaling.

Below, are the future necessary tasks of this project:

For the mobile M2M Gateway:

• Complete CoAP implementation;
• Complete ETSI data-structure implementation;
• Add support for chosen external sensors;
• Complete Database implementation;
• Implement Smart2M mirror API;
• Implement specific Use Case requirements;

For the Demonstration Application:

• Implement basic application architecture;
• Implement communication with the Smart2M broker;
• Implement communication with the Gateway API;
• Implement specific Use Case requirements;

For the M2M protocol comparison, with the same set up:

• Test each protocol's battery drain;
• Test each protocol's network traffic;
• Analyze test results.

To successfully terminate this dissertation, there's also some other tasks needed:

• Develop dissertation's website;
• Update website with project's progress;
• Write Master's Thesis;
• Deliver document version for revision;
• Deliver final document, for jury appreciation;

The first priority of the project is to complete the CoAP implementation and the ETSI data-structure, as they are requirements for the proper communication with the NSCL. CoAP is estimated to take one to two weeks opposed to four weeks for the ETSI data-structured, that has a greater complexity. In the first two weeks the base website is also going to be started, and it will continuously be updated for showcasing the progresses in the development throughout the project.

Then, after having the base communication established, the Gateway's database is going to be strengthened, followed by the implementation of the external sensors chosen to fulfill the e-Health Use Cases. This implementation should take two weeks.

After this is completed, it is time to start implementing the base of the Demonstration Application, which should take around 2/3 weeks. Afterward, the development focuses on achieving communication between the Demonstration Application and the M2M Gateway, from both the local API and the Smart2M API. This development is going to be in parallel with the implementation of the local API on the Gateway, given the knowledge needed for the tasks falls under the same scope. It should however, take about 4 weeks, given the complexity of all the tasks involved.

Only after the communication between the Demonstration Application and the M2M Gateway is solid, can the Use Case requirements be implemented and tested. This should take around two weeks.

At this point, the “ecosystem” between the M2M Gateway and the Demo Application should be stable enough to run a few performance tests with each protocol, to establish a comparison between battery drain and bandwidth used. The beginning of these tests should coincide with the start of the write process of the Master's Thesis. The Revised Version should be delivered on 2014/06/16 and the final version on 2014/06/30.