Appearing for CLD...Your tips?

[FraggerFox]

---

tbob wrote:

Functionality:  I've heard of some people passing even though the VI didn't work perfectly.  They had enough style and documentation points, and the VI worked partially.  They still passed.  Don't get hung up on one functional problem.  Let it go and tackle it if you have time at the end.

Good Luck.

---

So if I get short of time, should I give priority to documentation and cleanup in last 20 minutes and not the functionality????

[JÞB]

---

Fragger Fox wrote:

---

tbob wrote:

Functionality:  I've heard of some people passing even though the VI didn't work perfectly.  They had enough style and documentation points, and the VI worked partially.  They still passed.  Don't get hung up on one functional problem.  Let it go and tackle it if you have time at the end.

Good Luck.

---

So if I get short of time, should I give priority to documentation and cleanup in last 20 minutes and not the functionality????

---

Absolutely NOT.

    Give priority to documentation in the FIRST 20 minutes (or longer)  then make the functions act like the documentation says they will.  Under that basic assumption you won't get short on time because you've provided a documented solution.  Implementing it is trivial at that point.

[tbob]

The way I did it was to create the documentation in the VI Properties window first, stating what the vi would do (follow the exam requirements).  Then I created the front panel according to the description given. Then I created tip strips and descriptions for each front panel object.

On to the block diagram.  I put down basic code and added comments as I completed a block.  Don't forget to put labels on long wires.

Then I debugged the whole thing and refined my comments as I changed things.

If you follow this method, I think you will satisfy the documentation part and not run out of time.