Work with Wireframes, Business Requirements, Member Architects and clients to write the definitive specification that will be built by TopCoder. In Specification contests, competitors collaborate with winners of previous contests and TopCoder clients in the project forums to help finalize and enumerate the precise Application Requirement Specification for the new system. The Application Requirements Specification identifies and describes the logic requirements that define the User Interface (if there is one) and fulfill the business goals. Competitors compete to concisely document the actions and data of the application.
Specification Contests receive several documents and resources as input: Wireframes, Storyboards, possibly a prototype, a Systems Design Specification (from a Systems Architecture contest) and a Business Requirements Document (from a Conceptualization Contest). The task of the Specification writer is to synthesize a precise Application Requirements Document from these assets. This includes data, user activities, and their relationship to any User Interface. To do this, Competitors will create Use Case diagrams to define scope and Activity diagrams to illustrate actions. The Diagrams are indexed and then defined as a set of Logic Requirements in the Application Requirements Specification document. All Logic Requirements are assertive and written in a testable manner.
In the next phase of the project after Specification, Module Architecture contests will provide detailed interfaces and methods for the low level requirements of the ARS. The Component Design and Development and Application Assembly contests will give shape to the requirements and finally, the Testing contests will ensure they work correctly. Through these contests, TopCoder members are designing the application that the client will use every day, and Specification is where the application takes final shape.
- To learn more about how to compete, click here.
- To start competing on Specification Contests, click here!.
Contests will be posted to the Active Contest List. Each will have a wiki page associated with it to describe the contest details. Review the details, and if you'd like to compete, click the "Register" button.
Competition and Submission Phase
After you have registered, you will be able to download the contest distribution packet (a zip archive or set of documents). Review the instructions in the wiki and distribution. Review the forums too, for any additional instructions or changes.
Because the input material will likely not address all complications, corner cases and input details, forum participation is absolutely crucial.
At the end of the contest, the review panel will begin screening and reviewing submissions. The screening phase verifies that required materials are present and non-trivial. Following Screening, a Review Panel will begin reviewing passing submissions. The Review Panel is composed entirely of TopCoder members.
The winner will be required to support one "downstream" contest via the forums. For the Specification contest, this will usually be a Module Architecture contest. Other contest types are possible (since we will choose whichever form is most appropriate for the situation), but support will always be by forum.