Functionality and documentation points on CLD test

[K.Waris]

What are the chances of passing CLD if following have been implemented/not implemented?

Style:

Producer/consumer architecture with a seperate loop for display

Type def for queue dataypes and subvi based modular application.

All processing done in consumer via dedicated vis such as initializaiton, shut down, error handling, file io, and some for updating front panel e.g update programs etc.

Functionality:

No broken arrow

Initialized propertly, error and file io subvi working properly. Application stops on pressing stop button. Errors found on stopping vi e.g open/close file error 8 which are then overidden by using clear errror vi.

However, application certain logic was not implemented at all e.g following sequences as per requirement.

Documentation:

Subvis contained free labels and necessary documentation in vi properties. Tip strips for front panel controls in subvis e.g error in, error out, enums were not added.

Main vi : Tip strips and documentation for all controls/indicators done. VI properties contained documentation.

Kind Regards

Austin

[mikeporter]

All the things you mentioned are important and are things that a professional developer does all the time. Hence, the question is not which features you can get away with not including. The question is how good are you? Or to put it another way, how professional are you?

Note that it doesn't matter what your degree is in. It also doesn't matter how often you write software. Finally, it doesn't matter what you think your "real work" is. If you are getting paid to write software that work is part of your profession.

Mike...