Challenge Summary
Welcome to Asteroid Data Hunter Wireframe Challenge. In this challenge, we are looking for wireframe (Axure) solutions based on requirements from our client. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!
At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.
Round 1
Submit your initial wireframes for Checkpoint feedback
1. Dashboard.
2. Hunt Asteroids.
3. Progress.
4. History.
Notes.jpg: Any comments about your design for the Client
Round 2
Your Final wireframes for all the required pages with all checkpoint feedback implemented
1. Dashboard.
2. Hunt Asteroids.
3. Progress.
4. History.
5. Submit to MPC
Notes.jpg: Any comments about your design for the Client
About Project:
In this project, we are tasking competitors with developing a significantly improved algorithm to identify asteroids in images from ground-based telescopes. The winning solution will increase the detection sensitivity, minimize the number of false positives, ignore imperfections in the data, and run effectively on all computers. Learn more about the project here.
Style Theme:
- We'd like to have a clean and simple design.
- Anything “space” related is a plus.
Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all use cases mentioned in challenge details below.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Suggested Screens:
We are looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions! Here are some of the items that we think should be included:
1. Dashboard
- User should be able to access all the other pages from this page.
- User will see a dashboard of features (Hunt Asteroids, Progress, History and Submit to MPC)
- We do not need a login screen.
- Explore how this page should work (and keep it simple!)
2. Hunt Asteroids
- Users should be able to specify where the data on their local machine is housed and select it. (Browse Functionality).
- After selecting the data, we need a button says “Hunt Asteroids”.
- When user clicks on “Hunt Asteroids” button a search will begin for the Asteroid.
3. Progress
- This page shows the anticipated completion time/date for the current search.
- Can be a cool countdown like: T-minus 01:00 Until Completion.
- Can be a progress bar.
4. History
- In this page user will be able to display previous searches and to drill down into historical results, by entering the following data:
-- Time.
-- Date.
-- Observation position.
-- Celestial pointing.
- User will be able to know if a result were submitted to MPC or not.
5. Submit to MPC
- This page will house mailto links, users can click on any of them and their default e-mail program will launch.
- The two links are:
-- Observations – obs@cfa.harvard.edu
-- New Comet Reports (Discovered Visually) - cbatiau@eps.harvard.edu
- Observations is anything that users may notice, and a New Comet Report is anything that may be brand new.
Target Audience:
- Professional astronomers
- Amateur astronomers
- Educational & Professional organizations
Judging Criteria:
Your submission will be judged on the following criteria:
- User experience
- Completeness and accuracy of the areas of functionality and content
- How well your wireframes provide a consistent user flow and clear information architecture for the application
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
Generated HTML files with all the 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.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
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.