Development Challenge Types


NOTE: This track is being redeveloped. Today you will find more architecture style challenges being run as proof of concepts in the Code track.

This contest asks competitors to define the technical approach to implement the requirements. The output is a technical architecture document and finalized plan for assembly contests.

Software Assembly and Code

These challenge types cover the bulk of our competitive development challenges. Participants are asked to implement code to match the stated requirements and the results are reviewed by members of the Topcoder Review Board. The Topcoder forums are used to flush out requirements between the challenge manager and the community members.

The big difference between Assembly and Code challenges is the addition of the final fixes phase in Assembly. Assembly challenges are more well defined and have a very specific expected deliverable. Any deviation from this deliverable will be cleared up and implemented during Final Fixes. Code challenges are used to implement specific requirements as well but are geared more of an iterative approach to development where follow-on challenges are run to implement additional functionality and iterate on the previous deliverables.

See the review process for more details.

Test Suites

Competitors produce automated test cases to validate the quality, accuracy and performance of applications. The output is a suite of automated test cases.

UI Prototype

Competitors take the graphics (UI storyboards) and information architecture (wireframes) of a web site or application and create a working front end for evaluation and further development. The output is browser tested HTML website front-end with CSS.

Test Scenarios

Competitors define a testing strategy for the application (QA plan) including both high level application test cases and detailed test scenarios. The output is a QA Plan Document including scenario setup, pre/post conditions to the scenario, step by step instructions to execute the scenario, whether the scenario can be automated or not, and expected results to determine success.

First2Finish (F2F)

First2Finish is a race to develop the code as fast as possible while maintaining high quality.  Unlike other Topcoder competitions, an F2F ends as soon as a participant submits and passes review.  Review will occur as soon as a submission occurs.  If a submission fails review, the next submitter will be reviewed, if a submission passes review, the challenge ends and other submissions will NOT be reviewed.  If a participant re-submits before a review occurs, their previous submission is removed from the queue and their new submission enters the back of the queue.

Bug Hunt

Competitors identify defects by user testing applications and comparing final products to the requirements and architecture deliverables. The output includes a list of software defects found.

Have more questions? Submit a request


Please sign in to leave a comment.