Since I haven’t managed to find any example-applications (or even “loose” code) using the context.distribution and context.privacy parts of MUSIC, I have mailed Paolo Barone (editor of documentation about the system design of the architecture), asking him whether he had some example-code for me.
I will update this post as soon as I get an aswer.
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. Continue reading ‘Structure of the demo application’
I made a new survey, which is less general then the previous one about a selection of questions.
The survey can be found here: http://www.surveymonkey.com/s/P575NYK
The more people that answer the questions, the more accurate the requirements for my implementation will be. So feel free to take the survey..
I did an intermediate thesispresentation this week, the pdf files of which can be found here.
During this presentation, I showed screen prints of my first application. What this application does is explained in the presentation. The .jar files to run the application can be found here:
To run the application, install each of these .jar files in equinox, and start them (if you want to see the plugins appear in the GUI of the application, start the application first, but the other way around works too).
If there are any questions, feel free to leave a comment or send me a mail.
While reading papers and thinking about how the ideas described in them, could be applied to my thesis, I decided it would probably be best to split the communication in two groups. By splitting it up, a different approach can be taken for each group (see part 1).
A first draft of possible ways to implement the security/privacy in the context scenario I will be developping, is also given in part 2.
Continue reading ‘Trust in ubiquitous social networks’
I finally managed to compile the new version of the music middleware, and get it to work. I will shortly point out the different problems I encountered.
Two different projects needed new versions of libraries which weren’t included, and could not automatically be found by maven:
A quick howto on adding these files in the projects in eclipse: make a new directory in the project, paste the file in it. In eclipse, right click the file, choose Import > Install or deploy an artifact to a Maven repository. Type the correct Group ID, artifact ID and version. Then right click the project, and go to Maven > Update Project Configuration. This update is needed before trying to compile again.
When these files were added, the project compiled but I encountered another problem: while trying to deploy the context project, equinox complained about a missing the jar file for jdom.
Appearantly, this jar was moved to a higher level in the music project inbetween versions 3 (which I originally got from “nearchos.blogspot.com”) and 5 (which I will work with). When compiling the entire music project, a jdom-1.0.jar file is created. To run the context project, it is necessary to also install and run this particular file.
Now that everything is up and running, I can start developping, using the newest version of the music middleware.
I made three diagrams to describe the hospital scenario I posted earlier:
We assume that the user’s pda can communicate with its environment (hospital, waiting room, waiting room computer, doctor computer…) by bluetooth. The third diagram also explicitely shows this (by using a bluetooth plug-in). If working with bluetooth ends up not being realistically possible, this can be changed to wireless, without having to change the use cases or sequence diagrams.
These diagrams will hopefully allow for a cleaner approach to the implementation.
I spent my day trying to get the middleware compiled. Until now, I had been working with the console version of Maven, and I finally got all the dependencies in order (I figured out the eswt-converged.jar wasn’t the right version either). Now everything seemed to work, but the tests failed, which means the middleware cannot get compiled.
Because finding the errors that made the test fail, didn’t seem like an easy task in the console, I decided to switch to Eclipse. This would also allow for easier changes in the source code of the middleware, in case they are needed further on in my thesis.
This means I have to fix the “broken” dependencies in Eclipse. I’ve not yet managed to do this but I’ll write an update when I do.
I have found out what the first problem I was encountering was: the version of the jar (ch.ethz.iks.slp) I tried to add was an old one… I found the new version here: http://jslp.sourceforge.net/jSLP-OSGi/userguide.html.
Although this fixed the build error I got and described in my previous post, I am now getting a new one.
Again, I’ll post an update as soon as I find a solution.
I came up with a scenario that can be used to base a context-aware application on.
The scenario uses an application that, in a particular situation (in a hospital) communicates with systems (for example computers) around it. The application will react appropriately to its environment, and only give out the necessary information.
A written down version of this scenario can be found here: scenario.
