which "design pattern" for data acquisition?

[bmihura]

I've got to test 32 different electronic products using data acquisition equipment, running various algorithms on them. The algorithms may vary per module, independently, at run time.

I also need to log results to a database.

Which of the 23 classic design patterns would be appropriate for this?

[DRock]

Hello bmihura,

I'm not really familiar with your classic design patterns, but allow me to suggest a solution that should make your life easier if you're doing automated testing applications.

NI TestStand is a remarkably powerful tool to assist you with your automated test applications.  If you implement an NI TestStand solution, you could focus primarily on the design of the code modules and the sequencing of the tests rather than having to spend the time worrying about developing the code to do all of this from scratch.  As an added bonus, TestStand will log to database for you automatically.  

Our website has quite a few resources that you can use to learn TestStand, and there's a link to a free evalution download, as well.

Best of luck!