The micro-workflow framework targets developers who want to separate the control and logic aspects in their programs, thus making them flow independent. A well-factored flow independent application facilitates change because the most frequent business changes translate into process changes, thus leaving the code intact. Flow independence also fosters reuse, because domain objects make fewer assumptions about the control context in which they operate.
However, a workflow component aiming at separating the logic and control aspects within object-oriented applications has radically different requirements than the ones typical of traditional workflow management systems. Therefore, because most existing workflow systems and engines have been built with different design goals, they cant serve this purpose. The micro-workflow framework solves this impedance mismatch.