BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$75‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to TC Online Review Timeline Wireframe contest.

TopCoder has a competition type known as Bug Races. They are used to tap into the community's talent for smaller tasks that don't quite fit into a larger scoped contest. They cover more than "bugs", and are often used for incremental improvements, UI updates, documentation updates, etc. We currently run the Bug Races using Jira. There is some integration currently that allows users to create/view Bug Races from Cockpit, but there is not a clean integration between our Bug Race process/technology and our core platform technology (Online Review, Cockpit, etc.).

We would like to convert the Bug Races process so it runs as a competition type within Online Review, which is then exposed to the community sites and Cockpit as a standard contest type. We want to gain the advantages that Online Review gives us such as registration management, terms management, resource management, payment management, review processes, associations to cockpit projects and billing accounts, etc. Also, from the customer/Cockpit perspective it will make it easier to include Bug Races in game plans, schedule them for future dates, create dependencies to other contest types, select winners, etc.

The new Bug Race will have multiple submissions/review phases so we will have new timeline view in Online Review.

In this contest, we need your help to create a wireframe based on provided conceptualization document. At the end of this contest we are looking for a process flow and layout design of the functionality mentioned in document. You solution must have all required functionality, user friendly, intuitive and easy to use.

Round 1

You must submit your the whole solution for client to review - it should address all the mentioned requirements.

Round 2

You should submit your final submission for the client to review based on the milestone feedback from the client and copilots.


Primary Goals

Topcoder is going to convert Bug Race competition into a standard competition. New Bug Race will have multiple submission/review phases. This Wireframe contest is to create a solution the new timeline view in Online Review application.

 

General Requirements

- The timeline must be intuitive and user-friendly.

- The position of new timeline will remain same in Online Review application.

- Your solution must represents all requirements about the timeline in conceptualization document. We have some discussion about how it looks like in this document. But we are still open for your creative idea.

- You must use wireframe note pane in every single page you design, to explain what all items are addressed in that page, what things you added/changed/removed, use it to make your idea clearer and help us to give you constructive feedback.

- We suggest you to follow high level requirements details with use case diagram, it is provided in conceptualization document.

 

Wireframe Requirements

- Please read the conceptualization to get the idea of the new Bug Race flow. It will help you to understand the multiple timeline.

- New Bug Race process has 3 kind of phases: Registration, Submission and Review.

- After a competitor register a Bug Race, he will be able to view timeline in the contest detail page from Online Review.

- A competitor can submit multiple submission before the contest is completed. Every submission will have a submission phase in timeline. If the competitor has no submission, he still has a submission phase shown in timeline. After he submits one, the previous submission will close and a new one will open.

- Start date of each submission timeline will be the registration date of the competitor.

- Every closed submission phase time line and its review phase timeline will be viewable for all competitors. It will show the user handle for each submission/reivew phase timeline.

- If the contest is not completed or cancelled, every closed submission phase will has a review phase.

- We want your solution to has group feature to timeline. We want to group submission phases by submitter.

 

Refer to Conceptualization Document, following are functionality that must be implemented. Some of those functionality are also needed to be implemented Cockpit, Forum, Contest Details Page, Online Review and Member/Copilot profile. But in this contest, you only need to create solution that working in Online Review.

  • View Bug Race in Online Review (refer to section 4.4.2.4).
  • Choose Bug Race winner in Online Review (refer to section 4.4.2.6)
  • Manage Registrants in Online Review (refer to section 4.4.3.1)
  • View Bug Race Timeline in Online Review (refer to section 4.4.9.3)
  • View Review Scorecard in Online Review (refer to section 4.4.9.4)
  • Unregister From Bug Race via Online Review (refer to section 4.4.10.2)
  • Submit a fix via in Online Review (refer to section 4.4.12.1)
  • View Submission in Online Review (refer to section 4.4.12.2 & 4.4.16.4)
  • Download Submission in Online Review (refer to section 4.4.12.3 & 4.4.16.3)
  • View Result Scorecard in Online Review (refer to section 4.4.12.4)
  • Score Submission in Online Review (refer to section 4.4.16.6)
  • Post Review Distribution in Online Review (refer to section 4.4.16.7)
  • Show Online Review Timeline (refer to section 4.4.25.1)

 

Target Audience

TC Member, TC Copilot (Reviewer), Project Manager and TC Client.

 

Judging Criteria

- How well your solution provides good and intuitive user experience.

- Completeness and accuracy of the wireframe as defined in conceptualization document.

 

Submission Deliverables

Preview Image

Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission Files

Wireframes should be built in HTML or Axure. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.

Source Files

All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.

 

Final Fixes

As part of the final fixes phase you may be asked to modify content or user click paths.

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.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2013 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30031442