Process abstraction for frames reusability

Question

I write a modular desktop application that consists of two parts: manager and worker. Both use one frame called ModuleSelectionFrame. Each program can do common processes like creating or editing some entities using modules.
Each process can be divided into steps (for example: Creating entity: 1. Select module, 2.Fill module-specific form; Editing: 1. Refill form). In fact each step comes to displaying some controls and waiting for user response.
It would be nice to think of process in terms of steps. But how can we control and observe completion these steps?

Answer 1

--- Put a cap on the amount of edits you make to the document ---
Good luck with that approach. I wouldn't even attempt to tell a client "Hey, that's it- you can't make any more changes."
I think it's much easier to reach an understanding with the client before the project begins. I give them an estimate based on a written set of specs, and I make sure they understand that the estimate only covers work done up to the first proof. After that, straight time at the studio rate- same thing if they change the specs once the job has started. It takes as long as it takes, and it costs whatever it costs- it's all up to the client once we get into the end game.