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 Flash/Flex designers and developers. The competitions take the graphics (UI storyboards) and information architecture (IA wireframes) of the app to be built and create the working application. Storyboards and wireframes are developed in TopCoder Studio. |
|
Contest Timeline
Contest Posting
TopCoder posts the competition details, specification deliverables, IA deliverables, UI deliverables (which may include a UI prototype) and timeframe for active contests
. Members can read through the documentation and decide in what capacity they would like to be involved - Competitor or Review Board Member.
Review Board Creation
The Competition Manager (a TopCoder employee) will select the Review Board from the pool of pre-qualified members who are members of the RIA Build Review Board. If you would like to review RIA Component Competitions [please click here].
Competition
The Competition phase consists of competing individuals building the application utilizing the deliverables provided. 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 your submission. You can get that template here
.
Review
At the completion of the Submission phase, the contest will enter the Review phase. This phase will consist of testing the prototype in all applicable browsers and reviewing the code.
Before the full review can begin on any submission, it will be screened. Submissions that clearly would not pass review will not pass screening and will not be reviewed.
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 Appeals and Appeals Response phases will follow the Review phase. Each submitter may appeal any reviewer statement, as long as it is factually wrong. Each Reviewer will respond to the Submitters' 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. The winner will then enter Final Fixes. During this stage, all identified bugs and Review Board comments must be integrated into the submission. After Final Fixes have been completed, the submission will be reviewed again to verify the correctness and completeness of the fixes.
All prize winners are subject to Final Fixes and must meet their deadlines to avoid payment penalties (see below).
Support
The first place finisher will be awarded 75% of his/her prize at the completion of the RIA Build competition (after Final Fixes). The remaining 25% of the prize will be awarded after the first place winner has successfully supported his/her work as described below.
The second place finisher will be awarded 100% of his/her 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 Fixes phase, including performing all bug fixes. After the 30-day 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-day 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 be lose a percentage of their remaining prize in accordance with the following schedule:
- If 3-5 bug fixes are late, then 5% is lost.
- If 5-10 bug fixes are late, then 15% is lost.
- If more than 10 bug fixes are late, then 40% is lost.
