Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How will the submissions be judged? #6

Open
jonico opened this issue Oct 5, 2016 · 2 comments
Open

How will the submissions be judged? #6

jonico opened this issue Oct 5, 2016 · 2 comments
Labels

Comments

@jonico
Copy link
Contributor

jonico commented Oct 5, 2016

The evaluation criteria for each submission can be found here.

A convenience translation into English:

The jury of the competition is evaluating all submissions based on the criteria

  • theoretical foundations / approach
  • documentation
  • software engineering
  • UI/UX
  • functionality

The order of these criteria is not the order of importance, you should put your focus on the areas as demanded in the actual challenge description. The following points are meant to give you a rough idea what the criteria are about and should not be interpreted too literally.

Theoretic foundations/approach

  • Research
  • Modelling
  • Complexity analysis
  • Effort estimation

Documentation

  • consistency, completenesst and soundness
  • structuring and layout
  • code documentation

Software engineering

  • concise documentation of requirements, design considerations and decisions
  • concise documentation of tests, results and conclusions drawn
  • quality of the software development approach, design decisions and test concept

UI / UX

  • Usability
  • Exciting extensions

Functionality:

  • functional correctness and quality of the solution (according to the challenge description)
  • verifiability of the test results
@jonico jonico added the question label Oct 5, 2016
@Ichaelus
Copy link

Ichaelus commented Nov 8, 2016

While trying to gather test samples, we became more and more unclear about how the functionality of our algorithm will be tested. The given classes (DEV, HW etc.) don't seem to be present in equal amount at Github.
Having that information in mind, has the algorithm to face an amount of per-class-samples that correlates to the reality when tested or will they be nearly equal (like: 10 tests per class)?

Thanks,
Michael

@jonico
Copy link
Contributor Author

jonico commented Nov 8, 2016

@Ichaelus: Your are 💯 that the different classes are not equally represented across GitHub. The test data will reflect that "unbalance" although we will not disclose the actual ratio. Your rationale and documentation around your algorithm will be drawn into the consideration at least as much as the "pure" evaluation results.

Doe this answer your question?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants