In this week's meeting we displayed the version of our app that is capable of communicating with the server. There is still some work to do on the user interface to make it more dynamic across devices with different screen sizes. The current state of the app is shown below on an Android device:
 |
Initial log in screen
|
|
|
|
 |
Error upon bad authentication attempt
|
 |
| Screen where attendance evidence will be submitted |
 |
| Evidence success screen |
There are still many evidence methods that have yet to be implemented. In the user study we will have the ability to disable certain methods so that we are able to choose which ones will be tested at one time. We have given some thought to a system where students are required to use a certain number of evidence methods simultaneously in order for their attendance to be considered valid. Requiring students to submit 2-3 different types of evidence can help in reducing fraud.
In this next week we will continue developing the server-side component to ensure that information is being sent successfully. We also have to determine what other information can be sent to the server, i.e., WiFi information and device information. This type of information will be useful in the user study.
--Eugene
No comments:
Post a Comment