What is your favorite architecture?

[BJD1613]

The most common architecture I use is the state machine with three states (init, run, end) where there is an event structure in the run case.  See Attached.  This architecture allows for the handling of all UI events while allowing for processing in the timeout event.  I use a boolean flag to control if my test is running or is stopped. 

[#2]

Personally, I'm a big fan of spaghetti code.  It makes for interesting upgrades as well as eases debugging...just kidding!  Architecture really depends on the application.  Just because you have a favorite doesn't necessarily mean it's the best for every application.  I'm in favor of using the best architecture for the application.

[spsuamin]

For me it depends on the level of the vi in the heirarchy. At the top level I like using master slave for the user interface. I mix the state machine into the master while loop while it is controlled by a seperate loop to hold the event structure. I can then add as many slave loops necessary for the main functions of my programming.

[JTerosky]

I find that I use the Queued Producer-Consumer architecture a lot.  I have a user interface as a Producer and another loop as the Consumer.  This other loop can then handle the event (if it is simple) or act as a Producer for additional Consumer loops.  I also do this with a Status Window display.  I find that the users of the software like to have a text window at the bottom of the screen confirming the actions of the program.  They also have a menu selection that allows them to store this text window to a file so they have a time stamped record of when everything occurred.