...
1. Upon logging in, John is greeted with a search bar and a main frame containing a graphical summary of the completion of his degree requirements.
2. He expands the relevant tree node to view his degree requirements, which will distinguish between classes that have been taken, classes that are not offered this term, and classes that may be selected this term.
3. If John clicks on one of the hyperlinked requirements, the search frame will produce a list of expandable results similar to this example. The unexpanded class only displays very basic information and class ratings.
4. John adds 8.08 by clicking on the "add" button, which instantly changes to a "remove" button.
5. After adding another physics class, John searches for other classes in the Search field. He receives another list of results from which he can choose.
6. John decides to look over his schedule by clicking the "Selections" tab in the top of the main frame. He sees a list of the classes he has selected, recitation options, and a weekly schedule.
7. Having finalized his schedule, John syncs his classes with his Google calendar.
8. John tabs back to his degree requirements, retrieves classes to take later in the search results, and places them in his projected schedule.
9. Clicking on the "add to projected schedule" button produces a popup allowing John to choose the relevant semester.
10. John can now view his projected schedule by tabbing in the main frame. He can remove classes from this page.
| Anchor | ||||
|---|---|---|---|---|
|
Some visibility is compromised in this design, since users cannot view their current selections at the same time as their degree requirements. Efficiency is also suboptimal if users wish to view many class descriptions at once, since they must click individually to expand details, but the design is highly efficient for quickly browsing through classes. We can improve efficiency by experimenting to determine what content should be included in class summaries. This design should be extremely learnable for MIT students, as the search results, degree requirements, and current selections are formatted very similarly to the current equivalents. It will not allow for errors if implemented properly; for example, double-booking can be prevented by deactivating the option to add a class in a pre-booked time slot. We may include an option to turn off this feature for the benefit of overzealous classtakers.
Some visibility is compromised in this design, since users cannot view their current selections at the same time as their degree requirements. Efficiency is also suboptimal if users wish to view many class descriptions at once, since they must click individually to expand details, but the design is highly efficient for quickly browsing through classes. We can improve efficiency by experimenting to determine what content should be included in class summaries.
| Anchor | ||||
|---|---|---|---|---|
|
Design 2
...