Judging Criteria

Document created by Stefan Alexandru Malinici Employee on Feb 7, 2016Last modified by Cosmin Stefan Stoica on Feb 19, 2016
Version 2Show Document
  • View in full screen mode

When judging the projects we aim to be as fair as possible and identify the projects which are better than ordinary. We are looking for original ideas, something new or something that is improving what existed before, projects well executed and well documented.


Each project will be ranked in two parts:


  • During the Development period we will rank certain milestones.

      Each milestone will have an associated number of points and deadline. The number of the milestones, interval and assigned points depend on the project itself.


  • During the final we will judge the projects after they have been finalized and presented.


Judging during the final


The jury will be formed by NXP experienced engineers from two business groups who will try to be as objective as possible and determine the top three projects.


The criterion and their weights are depicted below.




Is this something new or improving something that existed before ?20%

Does it do what it should do?

Does it behave according to documentation in multiple scenarios ?

Are there stability problems?


Is the project easy to use and/or integrate ?

Is it easy to understand and learn?

UtilityDoes it have applicability within the IoT or Automotive domains ?10%

Is the documentation easy to be read and understood?

Is anyone with average knowledges on embedded able to reproduce the projects?