What is the best way to architect this?...
I am tryign to do thsi following OOP. Basically I have many steps that occur in a process. At the beginning of each step I grab the current step froma table, do the step, then update the table. So, in theory, the user can stop at any given step and then start up again later; which they need the ability to do. I am just having trouble designing the main class that basically says: start at step X and continue. 
What is the best way to architect this?...
===

I am tryign to do thsi following OOP. Basically I have many steps that occur in a process. At the beginning of each step I grab the current step froma table, do the step, then update the table. So, in theory, the user can stop at any given step and then start up again later; which they need the ability to do. I am just having trouble designing the main class that basically says: start at step X and continue. 