To be considered for judging, your team and the site you produce must abide by the competition rules.
When judging contest submissions, we will focus on four main areas:
- Functionality: whether the site functions without errors; whether the exposed features deliver usable results
- Usability: the overall ease-of-use of the site
- Aesthetics: the attention paid to graphic and UI design; the overall look-and-feel of the site
- Concept Execution: the degree to which the site identifies a problem and provides a realistic solution
More details about each category are below.
Functionality concerns the ability of user to visit your site and perform the actions that are advertised.
- Errors: Does your site load without errors? Are there portions of the site that are not implemented or don't work as intended? Do actions on the site cause uncaught errors or exceptions?
- Features: How many features are implemented? Are they useful, nontrivial, and well-polished? Note that this is not a race to implement as many features as possible -- judges will be more impressed with a reasonable number of polished, well-executed features than a large number of poorly-implemented features. A large, incohesive feature set also reflects poorly on usability and concept execution (see below).
- Response time: Does your site take an egregiously long time to display results? Note that we are not going to benchmark your site or judge your algorithms, but a site that takes five minutes to load query results is unreasonable.
- Security: Can the site be broken with the simplest of attacks? Note that we will not mount complex attacks against your site. The basic mitigations discussed in lecture will suffice.
Usability concerns the ease-of-use and learnability of the site. At a high level, is it obvious to the user what can be done, and does your system behave as expected?
- Ease of learning: Can a user encountering this web site for the first time easily discover what the web site does and how to make it work?
- Visibility: Is important information and system state readily visible on the site? Are features clearly indicated?
- Efficiency: Is it easy for the user to access all features of the site and be able to use them? Are there mechanisms built in for experienced users to save time? Efficiency generally does not refer to response time, but to how easily the user can perform common tasks on the site. For example, a feature that requires many mouse clicks across many menus to access has poorer efficiency than a features that requires few clicks.
- Safety and recovery: Is it easy for a user to make a mistake? Is it easy for a user to recover from a mistake, via undo, edits, or other mechanisms?
Aesthetics concerns the overall look-and-feel of the site and the impression it makes on the user.
- Layout: Is the overall layout of your site simple or cluttered? Are the user's eyes immediately drawn to the most relevant parts of the page?
- Consistency: Is the visual design of your site consistent across its components? Is there a familiar, comfortable set of colors, shapes, and fonts used?
- Attention to graphic design: Have you considered the basics of graphic design, including: color, balance and whitespace, and typography?
- Aesthetic innovation: Does your site do something particularly fresh, bold, or innovative in its visual design? This could be in the execution of a single feature or visualization or in taking a bold approach to the overall design of your site.
Concept execution concerns whether you have identified a real, existing problem and presented a compelling solution.
- Problem statement: Is the problem clear and well-defined? Is it a real, existing problem?
- Conceptual clarity: Does your solution employ a number of clearly-defined concepts? Concepts are ideas and notions that manifest themselves clearly in the implementation of your solution, or a common thread that runs through your feature set.
- Feature set: Does your application consist of a coherent, well-thought-out set of features? Do the features make sense when considered as part of a larger whole? Do the features address the problem to be solved?
- Originality: Does your application solve the problem in a way that hasn't been done before? Note that you may do well in this category even with a well-established problem, as long as your solution is novel.
The final submission will be a form, to be posted to the Milestones page at a later date. This form will close at exactly 11:59 AM (in the morning!) on Tuesday 1/31/17.
After the submission form closes, the staff will identify semifinalists. We expect to have around 12-18 semifinalists (for the Main Division) depending on the quality of the submissions. Results will be announced by 8:00 PM of the same day.
Semifinalists will have a 15 minute time slot on Wednesday 2/1/17 from approximately 8:30 AM to 4:00 PM to give a 5-minute presentation to the judges and answer questions about their site. We recommend that your presentation explain:
- What problem does your site aim to solve?
- How does your site fit the theme?
- Why is there a need for this problem to be solved?
- Why does your site solve this problem well?
Semifinalists will also give a short presentation at the Award Ceremony and must attend a mandatory Winner's Luncheon from 12 PM - 2 PM on Friday.
From the pool of semifinalists, the sponsor judges will determine the teams to win cash prizes. The results will be announced at the Award Ceremony.
PLEASE NOTE: Your team is allowed to make changes to your site after the final submission deadline. However, if you site is broken when we look at it, you will not have a second chance, so make updates at your own risk.