CLD Style and Documentation

[CollinsAero]

Hi all,

From what I have gathered reading this forum, a lot of people are not able to create a completely functional program within the 4 hours.   When I take the exam, I would like to ensure that if I am not able to do the same, I would like to at least get all of the points for Style and Documentation.  So far, this is what I think I should focus on, in terms of Style and Documentation:

• Labels on appropriate wires within the main and subVIs.
• Descriptions for each algorithm.
• Fill in "Documentation" section under "VI Properties" for all VIs.
• Add tip strips and descriptions for front panel controls and indicators.
• Labels for constants.
• Straighten wires as much as possible.
• Create an icon for the main VI and leave the connector pane blank.
• Create icons for subVIs and set terminals to "Required" or "Recommended"

That is all I could think of as of now. Is there anything else that I am missing?

Any help would be greatly appreciated.  Thank you!

[Gregory]

Also, wrap every subVI in an error / no error case structure. I think you can finish in 4 hours, you should run through the practice tests a couple of times. Keep practicing until you finish around 2:45 - 3:00, and you should be in good shape, giving yourself time to understand the new prompt you haven't seen before.

[Fisel]

Hi all. Actually, based on  Darren Nattinger's presentation " An End to Brainless LabVIEW Programming, we have removed the requirement for error/no error wrapper on all SubVIs from our evaluation of CLD exam Style/Documentation.