1st Annual BoE Programming Contest
Submissions and Scoring Rubric

Submissions

(Look here after the contest entry deadline passes to download entries.)


BoE Code Sequence Judge Info

Your Name:
Your E-mail Address:
Your Judge's Code:

BoE Code Sequence Info

BoE Code Sequence Reviewed:
BoE Code Sequence Programmer Name:

BoE Code Sequence Score

Originality (0-10)

0=
Very common - used everywhere.
1=
Quite common. Used often.
2=
Somewhat common.
3=
Used before, but not overly so.
4=
Seen in several scenarios.
5=
Seems like an altercation or moderate improvement of a previously used sequence.
6=
Unique but not very useful.
7=
Unique and somewhat useful.
8=
Quite original or a vast and/or creative improvement on a previous code.
9=
Unique and very useful in many circumstances.
10=
Never seen before this designer's use of it, revolutionary, a totally new concept that has the potential to greatly strengthen all future scenarios using it.

Your Score:


Documentation and Legibility (0-5)

0=
No documentation.
1=
Too difficult to follow, OR contains many spelling/grammar errors.
2=
Documentation can be followed, but with great difficulty, OR part of it is missing, OR contains some minor spelling/grammar errors.
3=
Documentation is complete, but is difficult to follow. It may be hard to exactly recreate the code sequence. No spelling/grammar errors.
4=
Documentation is complete and can be followed. It is possible to exactly recreate the code sequence. No obvious spelling/grammar errors.
5=
Extremely thorough and well explained. It is easy to recreate the code sequence. No obvious spelling/grammar errors.

Your Score:


Efficiency (0-5)

0=
Totally inefficient and bulky, there are obvious better ways to code this.
1=
Inefficient and bulky in two or more areas, there are obvious better ways to code this.
2=
Inefficient and bulky in one area, there is an obvious better way to code it.
3=
Can be improved somewhat, but not in an obvious way.
4=
Mostly concise, but could be improved in a minor way.
5=
Concise. Cannot be condensed further without compromising function.

Your Score:


Usefulness (0-15)

0=
Not useful at all and/or too buggy to use.
3=
Usefulness is limited dependant on highly contrived and/or unusual situations.
5=
Usefulness is limited dependant on somewhat contrived situations.
8=
Usefulness is somewhat limited, requires specific plot parameters for use, but can be generally justified without feeling too contrived.
10=
Definitely applicable to some situations, may require some general and minor plot modification and fitting to implement. However, these modifications can be easily justified.
13=
Can potentially improve most scenarios if applied. Modifications are easy to implement.
15=
Revolutionary, will improve all scenarios if applied. Modifications are easy to implement.

Your Score:


Additional Bonus Points (0-15)


Awarded for extra creativity and innovation. The purpose of this category is to allow judges to go beyond “just the facts,” judging each submission on its unique merits.
These points are awarded at the judge’s discretion. For example, customized graphics only need to be described in the accompanying documentation. However, if customized graphics are needed for the programming submission and are included in both .BMP and .MEG format, the judge may decide to award 10 points in this category, especially if the graphics are of high quality and are gamma-corrected for each platform. If the graphics are submitted for only one platform, or are not gamma corrected, perhaps only 5 points are awarded.


These can be used towards overall presentation points as well. For instance, just handing in a sequence would not earn points in this category. But actually presenting it and explaining it in the editor (via a quasi-scenario) would definitely merit some extra points.

Your Score:


Comments:

When you finish scoring this BoE Programming Sequence, click on the Submit button.

...until something better comes along!