Structure of the demo application

I have been trying to work out the application to know how every part of it would communicate with the rest. In this draft of the design of the application, it is divided into two parts: one on the user’s device, and one on the hospital-devices.

For now, I have assumed that it doesn’t matter how the context.distribution is implemented. The sequential diagrams I made, are “general” enough to allow for both the original code, as my potential changes to this code.Note:

• the entity “Workmonkey” in the diagrams is the code that will do the “low-level work” that isn’t done by the different plug-ins or reasoners.
• the information that can be disclosed by the user’s application are a) name + appointment information, b) name + medical information or c) what the user is doing/where he is.

The different diagrams can be found here:

• User device entities;
• User device sequential diagram; part 1 (finding a new bluetooth device), part 2 (a question being asked) and part 3 (changing relationship or information settings);
• Hospital device entities;
• Hospital device sequential diagram;