BONUS: 4‌ CHECKPOINTS AWARDED WORTH ‌$50‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to TC Direct Contest Detail Page 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.

In this contest, we need your help to create a wireframe for creating Contest Details in Cockpit. Requirement detail is provided in Conceptualization Document. At the end of this contest we are looking for a process flow and layout design of the functionality mentioned in document.

Round 1

You must submit your all mentioned requirements.

Round 2

You must submit your all mentioned requirements and fix your solution based on miletone feedback.


Primary Goals

TopCoder is going to convert Bug Race competiton into standard competition. The goal of this contest is to create a solution for Contest Details Page in TC Direct (Cockpit).

 

General Requirements

  • The contest details page must be intuitive and user friendly and should look as close as possible to contest details page for Studio and Software contest type in Cockpit. Example screenshot is provided.
  • Your solution should work for both Bug Race for Studio and Software contest type.
  • You must use wireframe note pane in every single page you design, to explain what all items are addressed in that page, 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

Refer to Conceptualization Document, following are requirements you need to implement in your solution:

  • Link Bug Race to a contest/project (Refer to section 4.4.2.3)
  • View Bug Race in Cockpit (Refer to section 4.4.2.4)
  • Choose Bug Race winner in Cockpit (Refer to section 4.4.2.6)
  • Create new version of Bug Race in Cockpit (Refer to section 4.4.2.7)
  • View Bug Race registrants in Cockpit (Refer to section 4.4.3.1)
  • Choose a Copilot to manage the Bug Race in Cockpit (Refer to section 4.4.3.3)
  • Option to open a reviewer position in Cockpit (Refer to section 4.4.4.1 and 4.4.4.2). We will have separated Review Board for Bug Race contest type.
  • An option to choose if a Bug Race needs a terms agreement or not (CCA Requirements).
  • View and download Bug Race submission in Cockpit (Refer to section 4.4.16.5)
  • In the timeline there will be 3 phase Registration, Submission and Review. Show solution how to present numbers of closed review phase and numbers of open review phase. The end of registration and submission phase are not shown until the winner is picked. We have an original idea in the conceptualization document but you do not have to follow it. You can use your creative idea in design. It is expected to use similar style with current timeline in your submission. We want to keep timeline views consistent.

 

Target Audience

TC Copilot, Project Manager and TC Client.

 

Judging Criteria

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

- Completeness and accuracy of 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 it in a file text.

 

Final Fix

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

3 submissions

ID: 30031441