19/10 : Brainstorm possible features + questionary
26/10 : Finish questionary, summarize results
26/10 : Start design web app
29/10 : Start writing code for web app
02/11 : Finish first iteration of web app
04/11 : First report
05/11 : Start design native app
08/11 : Start writing code for native app
16/11 : Finish first iteration of native app
17/11 : Start first serie of user tests
23/11 : Evaluate the results and start redesign both apps
31/12 : First presentation + deadline second iteration both apps
20/02 : End second evaluation
24/02 : Scientific article + start writing code for third iteration
30/03 : Second report + second presentation
11/04 : Deadline third iteration both apps (No more coding!)
18/04 : End third and final evaluation
27/04 : Poster
18/05 : Finish complete draft
08/06 : Ultimate deadline!
dinsdag 18 oktober 2011
Small summary
The main goal of my Thesis is to create a usable interface of Toledo for mobile users, or the lay the foundations for one. And I would like to create this interface in 2 different versions, one as a mobile web page, the other as a native app on a mobile operating system (Android or iOS). Doing this, will show us the opportunities both methods offer. The main advantages of a mobile web page are its massive user reach and instant adaptability. Whereas the native app will have the support of all the native options the smartphone platforms offer these days. For example, calendar and mail integration, file managers, etc.
As for the functions of the web/native app, I would try to keep them as simple as possible. Only the functions that people need or want when the use their smartphone to interact with Toledo will be included. This means there will be no social or fun additions. To find out what the users want from this interface, I will first ask them. To do this, I have a 2 step questionary in mind, first ask them what they would use a mobile Toledo for, and what do would expect from a native app. In the second step I would offer them a listen of functions I came up with it, so they can give those functions a score of how useful they think those functions would be.
After we have formed a core set of functions that users would require, we can start the design and implementation. For this I hope to get the support from the people who administrate Toledo. So we can make a web page and app that users can really use. I've heard some good and bad news about this. The good news being that the guys from Toledo would offer me some help with the API. The bad news is that they don't administrate all the functions of Toledo, a (big?) part of those are under control of the SAP team, who are more reluctant to give access to those features.
After we have a working interface, we can start to evaluate it by a serie of user tests.
As for the functions of the web/native app, I would try to keep them as simple as possible. Only the functions that people need or want when the use their smartphone to interact with Toledo will be included. This means there will be no social or fun additions. To find out what the users want from this interface, I will first ask them. To do this, I have a 2 step questionary in mind, first ask them what they would use a mobile Toledo for, and what do would expect from a native app. In the second step I would offer them a listen of functions I came up with it, so they can give those functions a score of how useful they think those functions would be.
After we have formed a core set of functions that users would require, we can start the design and implementation. For this I hope to get the support from the people who administrate Toledo. So we can make a web page and app that users can really use. I've heard some good and bad news about this. The good news being that the guys from Toledo would offer me some help with the API. The bad news is that they don't administrate all the functions of Toledo, a (big?) part of those are under control of the SAP team, who are more reluctant to give access to those features.
After we have a working interface, we can start to evaluate it by a serie of user tests.
donderdag 13 oktober 2011
Introduction
Hello, I am Tom Crauwels, a master student of the department Computer Science at the KULeuven.
On this blog I will post updates about my master thesis, which is part of the research group Human Computer Interaction of professor Erik Duval.
The subject of my master thesis is a mobile version of the digital learning environment Toledo (Blackboard).
Abonneren op:
Posts (Atom)