Six components, three .NET and three Java components have been set up as practice components. These components are actual components that have been used in previous rated events. This gives the event participants a chance to identify their errors or fine-tune their solutions, and it gives others a chance to get a feel for the types of problems that are used in a rated event. These practice components are different than rated components since a Review Board is not involved; rather there are self-evaluations for each person to use in evaluating their work. Also, the practice components do not involve all of the work of rated components.
It is highly recommended that all new members try a practice component prior to competing in a rated component competition. By participating in a practice component, you will learn to use the required toolset, the nature of the designs and implementations, and the expected structure of your submission. You will also get a chance to look at an winning submissions from previous .NET and Java competitions.
At the very least, looking at submissions from others and following the guided self-evaluation will show you
- exactly how to structure your submission
- samples of the various deliverables, and
- how to evaluate your own work.
- Selecting a Problem
Below is a list of six components. Read the requirement specifications to decide which one you would like to practice on or complete them all!
- Submission of the Practice Components
The practice components are designed to allow you to take your time and get a feel for the tools and skills required to compete. These components are not reviewed or submitted.
- Self Evaluation
Although you will not receive peer review, you will be able to score yourself using our scorecard and the self evaluation form included with each download. Evaluating your own work and identifying areas to improve is a key skill set in component competitions. Honing that skill now through these practice competitions will greatly improve your chances of winning.
- Additional questions
If you still have questions about your design, or why one technique was used over another, please feel free to post questions in the Getting Started forum
. Here you can interact with other TopCoder members to discuss best practices and the components in general.
The link for Requirement specs for Rounding Factory is wrong. It points to the requirement specs for String Filter. The correct link should be: http://www.topcoder.com/i/development/downloads/RoundingFactoryDevelopmentPracticeTasks.pdf