Mobile Projects 2009

Projects Evaluation
Academic Year: 2008/2009

Maximum points 15 (50% of the total)

Students: 7568 and 7565
Grade: 14
Motivations:Good project. The functionality is simple but everything is working fine. There are no major problems or exceptions: just one uncaught exception. The code is similar to that presented in the lectures when we made examples on SMS. The report is too short: the structure of the code is just sketched and there is no section on the technical issues found. The report simply illustrate the user interface. The user interface is OK, but the simulator of the house should have a different interface from the controller (the interface for the user that controls the house).

Students: 3044 and 7544
Grade: 15
Motivations:Very good project. A new function that could become a real service. Clean interface, but the direction of the arrows indicating if message is received or sent is not self explaining. Anyway the logic of the system is clean. Code is well structured. The report is a bit short but it provides all the required information.

Student: 4962
Grade: 15
Motivations: Excellent project, especially considering that you are a bachelor student. Clean interaction, simple but effective. The code is well structured and the report is very informative.

Student: 10030271
Grade: 14
Motivations: The code is excellent (no doubt about that), well structured. The interaction design is a bit cumbersome, and not intuitive in many steps. There are also some inconsistencies. For instance when viewing the graphs the "next" command scrolls through the pages but the "back" command exit from this view. For some operations buttons are used together with commands (there is no need to have buttons if you have a command). The report is really too short (just 1000 words) and it is not clear at all the structure of the code and the role of different classes. As I said, the code is very good, but to understand what you have implemented I had to "reverse engineer" the code.

Students: 3941, 3794
Grade: 14
Motivations: The project is clean and you have also developed a server. The server component has some problems (for instance I got from the server also expenditures that I have not inserted into the system). The code is ok and the interaction is good, but there are some issues. For instance when you get the results of a query there is no possibility to run another query but only to show all. It is unclear why this command is missing, and you have to step back to run another query. Moreover, it is hard to find how one can delete an expense. This should be a command, but it is buried down in the form for editing the expense. If you do not scroll you never find it.

Students: 4128, 3043
Grade: 15
Motivations: Excellent project. The interface is very good and the code is really well structured and complete.

Students: 3098,3195
Grade: 15
Motivations: Excellent project. The interface is good, the code is really well structured and the report is very informative. You have also developed the server component, and it is running fine in Tomcat.

Students: 7237, 7577
Grade: 13(+)
Motivations: There are some problems with the connection with the yahoo server; it works only if the emulator is running in the "maximum" security domain. In other words, the interface is looked if you choose to see an event (this is a major issue). There is a bug in the initialization of the friends; the friends are added to the list every time you look at them, so the list is repeating the same firends many times (keeps growing). The interaction design is incomplete. When a friend receives an invitation he can only see this event, but cannot really accept or reject the invitation. If an event is canceled by the friend that sent the invitation the friends that received the invitations are not notified (as the report says).

Students: 7515
Grade: 13(+)
Motivations: There are some problems with the interaction with this application. When you enter the patient system no boundaries are set. After you set the boundaries there is no way to make the application active and to send sms to the caregiver; you must exit and enter again. The caregiver application has some problems with the alerts. Alerts are generated every time the patient sends an sms with the position. The application does not check if another alert is still displayed, so many alerts are accumulating and in order to go back to the main screen one has to dismiss all the alerts that have been generated. The report is almost ok, but it is not correct to say that the user has uses cases like: UpdateLocation, SendAlert and VibratePatient. There are no defaults for running the demo, so I had to look at the xml scripts to determine the lat-long coordinates to insert into the boundary form and run the demo.