"Good" PAC Development Practices Overview

Shoot This, Opto!

"Good" PAC Development Practices Overview

---

bthomason@cybermetrix.com 06-28-2007, 5:39 AM
Here's a thought - a high level overview of basic "good development practices" - based on input from Opto's application engineering support folks, trainers, OptoPartner integrators, etc. i.e. a "how to get started" for automation developers.

Some prospective items for such a topic could include:
a. Approaches to requirements analysis and design with PAC implementation in mind.
b. PAC h/w and s/w component/tool selection.
c. Common design and coding patterns
d. Coding style, naming conventions, resources.
d. Implementation pitfalls (things to avoid).
e. How to code for testability, common test techniques.
f. How to code for reusability.
g. How to design/code for maintainability.
h. Tools and techniques for troubleshooting design/implementation problems.
i. "Good" documentation practices.
I am sure others can add to the list!

Obviously time constraints would preclude going into detail on each of these, but a high level summary could point to available resources elsewhere in "the Opto 22 system".

Many of these could make good stand-alone topics in their own right!

Opto 22 staff might respond if whitepapers or other resources address these issues.

Cheers and carry on the good work!

Bruce Thomason
CTO (and Opto 22 Integration Services Manager - amongst other things!)
CyberMetrix, Inc.
http://www.cybermetrix.com