REPOST TC Analytics - Launch Marathon Match Wireframes Contest

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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to “REPOST TC Analytics - Launch Marathon Match Wireframes Contest” contest. The goal of this project is to eliminate all manual process for create and manage marathon matches contest competition and integrated all administration process related to it into Topcoder platform called “TC Direct (Cockpit)”. In this contest, we need your  help to create new workflow for create and manage marathon matches contest in TC Direct.

At the end of this contest, we’re expecting a clear workflow/simulation to create and manage marathon matches contest.

Round 1

Initial submission for client review

Round 2

All contest requirements as stated in contest details with client feedback applied


The current process to create and manage Marathon match contest is usually done by Topcoder employees manually using several different software. We are building a new process to eliminate the need to create and manage all contest in this track manually and integrated all administration process to TC Direct (http://www.topcoder.com/direct) platform.    

In this contest, we need your help to create the new workflow for creates and manage marathon match contest in TC Direct platform. Your workflow must contains all these following requirements  :

1.    General Contest Information contains following fields, contest type, contest name, timeline, copilot, CCA requirements, Review Style, Project Name, Contest Fee and etc. Put  only information that important for marathon match contest.

2.    Each match must have a problem statement. It is developed in an external tool (called MPSQAS) and looks like this:  http://community.topcoder.com/longcontest/?module=ViewProblemStatement&rd=15322&pm=12154

It should be possible to link a specific problem to the match, one easy way is to provide user with some list (maybe selectbox) where they can choose one problem version to be used in the contest. Once this is done, the problem statement should get displayed in the cockpit, including last modification date. The client should be able to approve the problem statement (but not to edit it). The cockpit should display the date of last approval and ideally it should also be possible to check the version of the problem statement which was approved.

3.    Each match also has two specific associated pages – Match Details and Match Rules. User should be able to create content for these pages in two ways, create the content manually OR re-use functionality from TC Direct to select any existing content from our database as the page templates (see predefine_template.zip to get more ideas about templates functionality). Here are more explanation about each page:

Match Details :
http://community.topcoder.com/tc?module=MatchDetails&rd=15327
User should be able to edit this page in cockpit, maybe add some plain text editor with a bit of formatting abilities would be enough for that, or maybe not. Show us your suggestion that appropriate to handle this page. User should be able to review/approve , in a similar fashion as with the problem statement.

Match Rules :
http://community.topcoder.com/tc?module=MatchRules&rd=15327
We will prepare some default rules which can be used for almost all matches. So we need to have a checkbox like 'Use default rules for this match'. If it is checked, then nothing else is needed. If it is unchecked, then we switch to a process similar to the one for match details. So we again get some text editor which first displays the default rules and then allows to make changes into them. And again, the client should be able to review/approve, but not modify the rules.

4.    We also need some button called like 'Activate match'. When user click that button, the match will be 'active', it means everything is ready for launch. The match won't get launched immediately though. It will get launched at start date/time. Similarly, if user not pressed that button, the match will stay 'unactive', it shouldn't get launched even if we are past the start date/time. The client should be able to see the state (active or not), but not modify it.

Important :
1. We would like to keep the overall structure of the UI the same as it is for like currently in Cockpit (TC Direct). In other words, create the navigation, sidebar, and tab layout same like the screenshot attached in this contest.

2. Your wireframes workflow must be created in similar way like our current process to launch software or graphic design contest in TC Direct, we want to re-use as many as possible existing functionality in Direct for the new marathon match launch process (see DESIGN_CONTEST_LAUNCH_PROCESS.zip).

Notes :
1. We’re providing you with our latest wireframes for launch marathon match contest. this wireframes still missing a lot of functionality we needs as stated in contest requirements aboves, However, it might contain a useful general information that can be use as your references.

2. For more information regarding marathon match competition in Topcoder, please refer to these link :
-    http://apps.topcoder.com/wiki/display/tc/How+to+Compete+in+Marathon+Match+Events
-    http://community.topcoder.com/longcontest/?module=ViewActiveContestshttp://community.topcoder.com/longcontest/?module=ViewActiveContests  or
-    http://community.topcoder.com/longcontest/?module=ViewPractice

Target Audience
There will be 2 user roles that using this application, they are :
1.  Marathon Match Copilot
2.   Project Manager

Judging Criteria
Your submission will be judged using following criteria :
1.    Completeness and accuracy of the wireframe as defined in the contest details
2.    How well your submission presenting ideas and simplify marathon match contest creation.
3.    How well you implement the required data and provides suggestion, interactions and the user flow.

Submission and Source Files:   
Preview Image
Create a 1024x1024 JPG or PNG file and place a screenshot from your submission within it.

Submission File
All requested contest requirements/screens as clickable HTML files unless otherwise stated in the contest details.

Source Files
Wireframes should be built in HTML, Axure (.rp).

Finalfix
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

Attachment :
-   TC Direct screenshot refererences.
-   Latest wireframes for launch marathon match contest.
-   Step by step graphic design contest launch process
-   Predefine template functionality


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.

Challenge links

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

Unlimited

ID: 30031308