Hi Bill
I went that path in the past.
Here is what I would require:
- All in G (unless it can not be done)
- Use directory structure that make sens (data, code >configurations, custom controls, process control, Globals [LV2 or others] .....)
- Documentation: minimum: a few line of comment next to non obvious code (quick and easy to do), more: comments for each SubVI (takes longer) in the VI documentation box
- Uniform Icons style for sub process of the same nature (critical to be able to quickly graps at a glance what's going on from the hierarchy).
- Naming: if an appropriate directory structure is use naming should not be an issue, although some prefix or suffix might be usefull for categorizing (<- is this a word?) things
- Versioning: Simpler
is to create a new directory called myapp v1.xx for each significant revision. More elaborate: If the contractor is doing the work at your location, and you do have source control, then use it.
The bottom line is, if you have to maintain the code, have the contractor make it in a way that make sens to you.
PJM
