Overview
|
Rich Internet Application (RIA) Build Competitions provide the build of small applications used both on the Internet and on the desktop. Most of the competitions here are for JavaScript developers, Java/.NET desktop application developers and Flash/Flex designers and developers. RIA Build JavaScript contests use server side operations such as AJAX calls, Service calls or Database operations etc. and which is different from JavaScript UI contests on UI Prototype Competitions track.
The competitions take the graphics (UI storyboards) and Information Architecture (IA wireframes) of the application to be built and create the working application. Storyboards and wireframes are developed in TopCoder Studio Contests.
RIA Build track has the following contests:
|
 
|
Introduction to RIA Build Contests
Comparison between Flash, Desktop Application and JavaScript RIA Build Contests
RIA Build Guide
Section 1: Flash Contest
A Flash contest is one of the contest types in a RIA Build competition. The goal of this competition is to build out the provided storyboard designs into an interactive and functional flash content such as animations, vector graphics, charts and audio-video playback etc.
The deliverables should include FLA updated files, all source files with updated prototype files. Must check the Browser compatibility testing in the given browsers.
Section 1.1: Technologies
- HTML, JavaScript, ActionScript, Adobe Flex, Adobe AIR and Flash etc.
The versions of HTML, JavaScript, ActionScript and Flash to be used for a particular contest will be specified in that contest's detail page. For example, HTML 4.01, HTML 5, JavaScript 1.2, ActionScript 3, Flash 11 etc.
Section 2: Desktop Application Contest
The purpose of this contest is to convert the provided wireframe into a working prototype written in C#.NET with WPF, Java SWING UI etc. The inputs to this contest are the storyboard and wireframe, deliverable is a single zip file containing all the files necessary to view and run your submission properly (i.e. an .exe file, .jar file and the source files).
Section 2.1: Technologies
- Java, Swing, C#.NET, WPF, etc.
The versions of above technologies to be used for a particular contest will be specified in that contest's detail page. For example, C#.Net Framework 4, Java 1.6, Java SWING UI etc.
Section 3: JavaScript Contest
The goal of this contest is to create JavaScript code. Your JavaScript code needs to be well documented, unit tested, browser tested and ready for assembly. The HTML/CSS was created in a previous contest, so this contest is focused on creating the correct JavaScript interactions that will be used in the actual application.
The inputs to this contest are the storyboard and wireframe, deliverable is the working prototype with the necessary JavaScript and unit test files.
RIA Build JavaScript contests use server side operations such as AJAX calls, service calls or database operations etc. and which is different from UI Prototype JavaScript contests.
Section 3.1: Technologies
- HTML, JavaScript, AJAX and CSS etc.
The versions of above technologies to be used for a particular contest will be specified in that contest's detail page. For example, HTML 4.01, HTML 5, CSS2, CSS3, AJAX etc.
Section 4: Contest Posting
TopCoder posts the competition details, specification deliverables, IA deliverables, UI deliverables and timeframe for Active Contests. Members can read through the documentation and decide in what capacity they would like to be involved, as a Competitor or as a Reviewer.
- When the contest is posted the competitor can view it in the Active Contests.
- The contest will be going through stages such as Submission, Screening, Review, Appeal, Appeal Response, Aggregation, Final Fix, Final Review, Approval etc. Competitor can view the status from Contest Status.
- When the competition is over (After the approval phase) the contest can be viewed in Past Contests.
- Upcoming contests can be viewed in Upcoming Contests.
 | In any phase of a contest, extensions can be requested if the submitter or reviewer requires. The extensions in the submission phase will be granted only if there's still more than 24 hours before the Submission deadline. (And also depends on factors such as how many competitors require an extension. For example, if only one competitor is requesting an extension and all the others do not require any extensions, request for extension will be rejected). The extensions can be requested via the forum or by contacting the copilot. For more details on extensions click Contest Management. |
Section 4.1: Active Contests
Competitors can view the current RIA Build contests list through the Active Contests page. This page will consist of the following information:
Contest : This is the name of the current contest.
Register by : Registration ending date and time.
Submit by : Submission ending date and time.
Payment : Prize of the 1st place.
Reliability Bonus : Reliability bonus prize for the First place winner. For more details click Reliability Bonus.
DR Points : This is the total Digital Run Points allocated for the contest. For more details on DR Points click: DR Overview.
Registrants (Rated/Unrated) : The competitors who are registered to the contest and whether they are rated or not rated.
Submissions : Number of submissions received for the contest.
Section 4.2: Contest Status
Competitors can view the status of the UI Prototype contests that are not currently ended through Contest Status page. This page will consist of the following information:
Contest : This is the name of the contest.
Registrants (Rated/Unrated) : The competitors who are registered to the contest and whether they are rated or not rated.
Submission due date : The date by which the competitor should upload the submission.
Final Review due date : The date by which the final review should be finished.
Current phase : The stage in which the contest is currently in, such as Submission, Screening, Review, Appeal etc.
Winner : The competitor who received the highest marks for the submission.
Second place : The competitor who received the second highest marks for the submission.
Section 4.3: Past Contests
Competitors can view the past RIA Build contests which are currently ended through the Past Contests page. This page will consist of the following information:
Component : This is the name of the past contest.
Category : Name of the Category.
Complete date : The date the contest ended.
Registrants : The number of competitors who were registered to the contest.
Submissions : Number of submissions received.
Passed screening : Number of submissions that passed the screening.
Winner : The competitor who received the highest marks for the submission.
Score : The score of the winner.
Contest details link : This is the link to the completed contest detail page where further details on winners, screening marks, Review marks can be found.
Section 5: Competition
During the competition the competing individuals build the application utilizing the provided resources. The creation of the RIA Build is based on the specification deliverables included in the Contest Posting phase as well as any other documentation and instructions that are included in the contest posting. The end result of RIA Build varies depending on the scope of the contest.
Each competitor will be responsible for creating their working environment unless otherwise specified in the competition details.
Note - Each competitor must submit a Deployment Guide with the submission. You can get that template here.
Contest type : This is the current contest type heading which is a UI Prototype contest.
Contest name : This is the name of the current contest.
Register button : Competitors click Register button to register to the contest. Upon registration it is required to agree to Terms of Use applied to the particular contest.
Submit button : To submit their submissions the competitors must access online review tool by clicking on the Submit button.
Winning prizes : These are the winning prizes for the First and Second places.
Reliability bonus : Reliability bonus prize for the first place winner. For more details on Reliability Bonus click Reliability Ratings and Bonuses.
DR Points : This is the total Digital Run points allocated for this contest. For more details click DR Overview.
Contest timeline : The contest posted date, registration dead line, submission and final submission dates are given in this section.
Contest detail section : This section contains the detailed requirements of the contest including main tasks, technologies to be used, submission deliverables, etc.
Review board : Use this link to view review board of the RIA Build contests.
Contest forum : This is the link to the forum of the contest where you can post your questions and get them clarified.
Screening scorecard : Screening scorecard is used to screen the submissions of this contest.
Review scorecard : The submission will be reviewed according to the guidelines in this review scorecard.
Downloads : The support documents required for the contest such as Storyboard, Wireframe are provided here. Only the registered competitors can download them.
|
If you reviewed a contest that failed and you had access to other members' submissions, you may not submit for the reposted contests (but you may still review them). |
 |
You can get notifications about active RIA Build contests by RSS. |
Section 6: Forums
For any extra requirements or clarifications you can access the forum of the contest. Only the registered users have access to the forum. For each contest a separate forum is available.
Section 7: Scores
Section 7.1: Screening
Screening Scorecard - Submissions must score 100% to pass.
Section 7.2: Review
RIA Build Scorecard - Submissions must score 65 or higher to pass.
Section 8: Review
At the completion of the Submission phase, the contest will enter the Screening phase. Screening will be done according to the Screening Scorecard. Submissions that do not pass screening will not be reviewed. (Please visit the Screening Scorecard link provided in the Section 7.1)
The submissions which pass the screening will enter the Review phase. Each submitter will have a scorecard set up in Online Review. Reviewers will score each submission based on a scorecard. The scorecard will ensure that the submission meets the required functionality, looks exactly like the storyboards, uses the required technologies and everything is completed as outlined in the contest deliverables. (The links to score cards and the passing marks are given in the Section 7.2)
The Review phase is followed by the Appeals and Appeals Response phases. Each submitter may appeal any reviewer's statement, as long as it is factually wrong. The Reviewers will respond to the appeals.
Based on the final scorecard standings after all appeals have been settled, a winner will be determined. Winners in this contest are designated based solely on their scores from the Review phase.
In Aggregation phase any defects identified by each of the reviewers are consolidated into a single list of fixes that the winner must make before the competition is completed. This list is put together by the primary reviewer.
The winner will then do the Final Fixes. During this stage, all identified bugs and Review Board comments must be integrated into the prototype. After Final Fixes have been completed, the prototype will be reviewed again to verify the correctness and completeness of the fixes and pass for the Approval. All prize winners are subject to Final Fixes and must meet their deadlines to avoid payment penalties see Late Deliverables.
|
Ratings and reliabilities are calculated for a particular contest after the approval phase. For more details on Reliability Bonus click Reliability Ratings and Bonuses. |
Section 9: Support
The first place winner will be awarded 75% of the prize at the completion of the RIA Build competition after Final Fix. The remaining 25% of the prize will be awarded after the first place winner has successfully supported the work as described below.
The second place winner will be awarded 100% of the prize at the completion of the RIA Build competition.
After the Review phase, the winning submission will move on to the Support phase. The winner will support the build for 30 days following the Final Fix phase, including fixing all the bugs. After the 30 days support period, any identified bugs will run through the standard TopCoder bug fixing processes which the winner may or may not choose to participate in. Any requests for enhancements will result in additional payments to the winner.
If a defect is found in a build, it will be fixed through TopCoder's standard component bug fixing process. An appropriate deadline will be set to fix the build and the winner will integrate the patched build once it has been fixed. If the build fix falls outside the scope of the 30 days support period, the winner will be paid additional money to integrate the build into the web site/application once it has been fixed.
If the winner misses any deadlines for fixing defects, they will lose a percentage of their remaining prize in accordance with the following schedule:
- If 3-5 bug fixes are late 5% will be deducted.
- If 5-10 bug fixes are late 15% will be deducted.
- If more than 10 bug fixes are late 40% will be deducted.
View more on Late Deliverables.
Section 10: Review Board Creation
Members to the RIA Build Review Board will be selected based on a set of predefined requirements. Please click on the Reviewer Qualification Requirements page to see the required qualification to become a RIA Build Reviewer.
If you would like to review RIA Competitions, you may send an email to support@topcoder.com requesting permission to perform reviews. You can view the latest RIA Build Review Board from the following link : Meet the Review Board. Once you become a "Reviewer", you can apply to review the listed contests from the following page: Review Opportunities.
Section 11: Tools and Resources
Most of the RIA Build competitions require CCA (Competition Confidentiality Agreement). Refer this link to get more details: CCA (Competition Confidentiality Agreement)
Common Resources
RIA Build Review Board Guidelines - An explanation on the review process and guidelines that should be followed during RIA Build contests.
RIA Build Review Board - List of current members on the RIA Build Review Board.
RIA Build Review Scorecard - The latest scorecard for RIA Build contests.
Additional RIA Build Resources
W3 Schools - HTML - Useful reference material and a good resource for new developers to learn HTML.
W3 Schools - JavaScript - Useful reference material and a good resource for new developers to learn JavaScript.
C# Tutorials - Useful reference material for C#.
Adobe Flex - Useful reference material for Adobe Flex.
Adobe Flex 3 - Useful reference material for Adobe Flex.
Adobe ActionScript 3 - Useful reference material for Adobe ActionScript 3.
Getting Started with WPF - Useful reference material for WPF.
WPF Documentation - Useful reference material for WPF.
Java Swing UI tutorial - Useful reference material for Java Swing UI.
