Your entry into Code Clash will be judged by Design Data employees on the areas explained below. Projects are judged from the viewpoint of a typical SDS/2 user who may be new to downloading and running parametrics and Custom Members. Judges within Design Data will include a representative from Support, Sales, Programming, and at least one floater who can assist with tie breakers. If your project includes connection design, it may be evaluated by a Design Data Engineer.

Usefulness and Creativity
Your project should provide a feature or a tool to the community that is unique, creative and useful. It should benefit its users by saving them the hassle of doing something in a more difficult and time-consuming way. The key is that it needs to be something that its users will benefit from having, and it is something that does not already exist in either the SDS/2 software or as a parametric or Custom Member available on the SDS/2 Web site.

Documentation and Help
The amount and quality of your documentation, especially your readme.txt file that instructs the customer how to install and run your project. Readability and grammar are considered.

Ease of Use
How simple and intuitive your project is to use and to obtain the desired result. Even if your project generates complex output, getting to that result should be a relatively simple and straightforward process.

User Interface
Your project should have a consistent look and feel throughout all dialog boxes and user prompts. This look and feel should be easy on the eyes, such that text and entry fields are arranged in a manner that feels organized and keeps relevant data together.

Code Clarity and Quality
Code evaluation is based on the readability of your code, and on the quantity and relevancy of its comments. Code is not judged on your personal programming style. Use of whitespace and visual flow of the code are key elements.