Fall 17 CS465 - User Interface Design Final Project
Video Introduction: https://youtu.be/mZ3_xzuH-rE
RackM8 is an Android application that primarily addresses an interface design problem using a task-centered design approach. This application enables users to search for bicycle racks based on academic buildings surrounding the UIUC Engineering Quad. Users can search for bike racks by building, by distance, and by safety rating. The app also allows users to leave ratings and indicate which bike rack they have parked their bike. Please see the Functional Prototype powerpoint to learn more about our design process.
-
The project must primarily address an interface design problem. This is not the place to focus on algorithms or database solutions for which the interface is well-known or obvious. It is also best to avoid well-known problems which have been addressed many times over. Showing the locations of friends on a map, course planners, course schedulers, study team organizers, to-do lists, restaurant, menu, and recipe interfaces, and chat interfaces all fall into this category and should be avoided.
-
The project must be suitable for the task-centered design approach we will learn in the course. That rules out most applications where users interact without specific goals or tasks to accomplish. For example, a purely decorative screen-saver would not fit. Game-related applications should be reviewed carefully. We will help you determine whether a project is likely to work well, and we can often help you identify an aspect of a domain that interests you that would be suitable.
-
The project should be relatively self-contained and scoped appropriately for the course. You will have only a few weeks to perform the implementation. It is therefore best if the project delves deep into a small problem as opposed to trying to build a large application. It is acceptable to simulate aspects of a project that cannot be feasibly implemented. It is typically unnecessary to manage a live database or use real sensors for input. In general, you should avoid working on the "system side" of the project.
- Week 3 (Due Sep. 11 @ 11:59PM): Complete the CATME survey (0%)
- Week 5 (Due Sep. 27 @ 3:30PM): Submit and present the project proposal (10%)
- Week 6 (Due Oct. 4 @ 3:30PM): Submit revised project proposal (10%)
- Week 7 (Due Oct. 11 @ 3:30PM): Submit user research report (10%)
- Week 9 (Due Oct. 25 @ 3:30PM): Submit and present low-fidelity prototype (10%)
- Week 10 (Due Nov. 1 @ 3:30PM): Submit revised low-fidelity prototype (10%)
- Week 11 (Due Nov. 8 @ 3:30PM): Submit results of a user evaluation of the low-fidelity prototype (10%)
- Weeks 11 to 14: Work on functional prototype
- Week 14 (Due Nov. 29 @ 11:59PM): Submit and present functional prototype (20%)
- Week 15 (Due Dec. 6 @ 3:30PM): Submit revised functional prototype (10%)
- Week 16 (Due Dec. 13 @ 11:59PM): Submit results of a user evaluation of the functional prototype (10%)
- Extra Credit (Due Dec. 8 @ 11:59PM): Submit a video demonstration of your revised project proposal (up to 5%)
Search View:
Nearby View:
Map View:
