Platform and Software Requirements

This prototype should be able to run from any OS and has been tested using Chrome and Firefox.

Prototype Instructions

To run our prototype please visit: http://aehsu.scripts.mit.edu/collegeroute/search_schools/
Note: this prototype is now the final version of our implementation and not the original computer prototype. The design flaws described below no longer apply to the website found at this link.

Shallow Prototype Components

  • Since our prototype uses data about colleges around the United States, we have started by using a small subset of schools, mainly those in the Boston area to get a rough idea of interactivity. We are aware that the number of schools we have added makes the transition from the first page to the second page slow to load because there are a significant number of schools. We will optimize the retrieval of schools in future iterations.
  • The GPAs, SAT scores and ACT scores of each school are randomly generated just to give ideas of layout (the locations of the schools on the map are accurate).
  • On the first page, the input filters do not actually connect and filter by school because we had a limited number of schools to work with for this prototype so we didn't want to filter any out.
  • We currently have not implemented the login/logout/save options for itineraries, so the links in the banner are purely aesthetic and do not work.
  • The tour times presented on the planning page are fake and not associated with real days or tour times for schools.
  • The last page where trips are planned is incompletely implemented to get an idea of locking schools and planning routes. The expected calendar affordance has not been implemented yet, and the buttons and styles are not fully formatted on this page.
  • No labels

4 Comments

  1. Unknown User (avogel@mit.edu)

    Here is my heuristic evaluation of your interface.  I really liked your interface and you had a lot of good elements, but I focused on what could be improved because I figured that would be more useful to you.  I hope this helps -Ari

    Ari-Heuristic.pdf

  2. Unknown User (kfish117@mit.edu)

    iceGeckos_kyle.pdf

    -- Here are you comments

  3. Unknown User (jvaladez@mit.edu)

    HW2 - jvaladez.pdf

  4. Unknown User (jks@mit.edu)

    • Wiki presentation: Great prototype depth description.
    • Fidelity:
      • Beautiful computer prototype for the most part, high fidelity in look and breadth for the tasks of finding appropriate schools.
      • However, the prototype is pretty low-fidelity in look for the itinerary planning page - the point of the computer prototype is to design the look of ALL your features, rather than depth for half of them.
    • Usability: 
      • Logo should be more prominent and contrast with the background more strongly.
      • Give the user instructions that they have to *select* schools from the search results. Add a heading indicating that the green outline around selected schools are, in fact, the selected schools.
      • Wonderful interactive map, with great overlays and option to add/remove schools from selection. Change dropped-pin color for selected schools from yellow to green, to match the 'selected' feedback on the left.
      • Again, missing info about how to proceed through the scheduling section. Not obvious that you have to lock school order before you can proceed. Moving school order can be drag-and-drop. Might want stronger instructions and affordances that each school can be selected. I know you're working on this stuff, but it needed fleshing out for GR4, at least in look.
      • What's the end product? A save button should exist in GR4, even if it doesn't do anything. Or do I email the itinerary to myself? Maybe there should be a summary page that includes the routed map as well as my day-to-day plans.
    • Overall:
      • Excellent job overall.
      • Suggestion: Reduce the search complexity by allowing students to OPTIONALLY specify 'schools near X', where X can be a city/state/particular school.