which "design pattern" for data acquisition in C#?

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?
Who is Participating?
Any given task could make use of a number of patterns.  It depends on what classes you intend to create and what role you intend for them to play.

On the surface, the strategy pattern looks like a match, mapping the same interface to separate functions for the different products


But there could well be opportunities for other patterns as well.
bmihuraAuthor Commented:
Wow! That's exactly the solution I independently chose, but this is my first time to ever use design patterns.  Thanks for the confirmation.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.