Project Work : How I will be evaluated ?

Most students have doubts as to how a common denominator ( in evaluating the quality of work done/knowledge acquired) can be arrived at when each student is into a different project.

The answer is very simple.

The evaluator does not concentrate on the project work you have done ! ....but on how you can apply your acquired knowledge/skills in arriving at solutions to a NEW problem/project.

Examples :

You have done a project using 8051 microcontroller as the system core, C as the programming language. Then , questions can be framed to solve new problems using the same combination of Hardware and Software.

1. I need a Burglar alarm system to be designed. Could you suggest how I should approach ?
2. Do we need to programme the software using C ? Why ? Can't we use ALP ?
3. What architecture would be most appropriate for this design ? RISC or CISC ? Does it really matter ?
4. I have to work on a very small budget and prove the efficacy of the alarm system. But once the system  starts working effectively, I may succeed in getting more budget allocated to my future requirements. What enhancements can I make to the Burglar alarm system (without adding too much cost) in an office environment ?

...like this, the list of questions can go on.

You must have observed that the questions have something in common. Every question is asked with a clear assumption that you are the right person to give the answer...... because you have already done a project on similar lines.

So, the panel assumes that you are the right choice. Now, it is up to you to live up to the panel's expectations by giving meaningful and simple answers.

The trouble starts when you dont.....

Our combined effort is to see that you do :)