Challenge Summary
The DARPA CS-STEM project will contain a number of different activities for users to participate in. We have a number of ideas that are going to be implemented, and one is the "Scavenger Hunt". This activity is intended for 13-18 year old demographic.
For more information about the project, please visit the following pages:
Main DARPA CS-STEM page | DARPA CS-STEM blogs | DARPA CS-STEM general forums
This is a contest re-post from http://studio.topcoder.com/?module=ViewContestDetails&ct=1002242 this is open to anyone, and those who submitted on that contest can resubmit to this contest.
Primary Goal & Design Considerations
For this contest, you will update a wireframe to make additional pages for the Scavenger Hunt activity. In this activity, the users will visit participating web sites to look for a hidden ball on the sites. When a ball is found the user will need to complete an activity (puzzle/game) in order to "unlock" the ball. When a ball is "unlocked", the user will be offered a link to a new web site to search for a new hidden ball, until all balls are "unlocked"
This activity is well defined in the provided conceptualization document.
One round was already completed on this contest. Feedback on those results will be posted to both the old forum and the forum for this contest. Please see the forums for details.
Requirements
The goal of this contest is to update the provided wireframe. You are asked to add the additional features outlined below.
Wireframe Requirements:
1) On the Homepage, change the link of "Scavenger Hunt" and "Learn more about this activity" under the Scavenger Hunt activity section to the new Scavenger Hunt activity page.
2) Design a page or pages that define the features or sections for:
- description of what the scavenger hunt activity is
- guidelines on how scavenger hunt activity is played
- showing how multiple scavenger hunts can be displayed to competitors
- showing how leaderboards for each scavenger hunt can be supported
- showing description, guidelines, hints, and tips for each scavenger hunt
- placement of help text
- placement for FAQ
3) Provide sample display of different scavenger hunt status, the status are:
- Not yet started
- Already started but not yet complete
- Completed
For "Not yet started" status, provide a link/button to start the scavenger hunt activity.
For "Already started but not yet complete" status, provide the following information:
- link/button to resume the activity
- display of current accumulated awards/points/achievements so far
- display of time related feature like time started and time spent so far on the activity
For "Completed" status, provide the following information:
- link/button to restart the activity
- display of awards/points/ achievements received
- display of time related feature like time started, time ended, and time spent on the activity
Do not DELETE any old page as they will be needed in the future build. The provided wireframe has two version (normal and wide screen) versions; please create the updates on both versions.
Judging Criteria
Your submission will be judged on the following criteria:
- How well your wireframes provide a consistent user flow
- How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
All Requested Contest Requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.