UML WF

The use of MDA tools to convert PIM's (platform independent models) to PSM (platform specific models) is interesting but in practice hard to keep the discipline of maintaining models after the coding has begun. Models and code can quickly go out of sync especially in terms of dynamic models. In addition the domain specific nature of many projects mitigates benefits of UML, as the Software Factory folks argue.

The question of converting UML dynamic diagrams through MDA into workflow models, I think in practice, suffers from the round tripping problems for dynamic diagrams. Everyone can round trip class diagrams. There is one tool out there I know of that attempts to reverse engineer dynamic diagrams. Once code starts, I think, the dyanamic diagrams become a reference or documentation rather than a live member of the developement project.

..."The workflow model is build to allow executable parts of the workflow including state management and execution management to be represented. A workflow model could be used as a common language for software designers as they structure their ideas about the architecture of a software project. But that's not the primary focus of the technology."...

Another thought is to have WF, VS 2005 Class designer, and Software Factories as a replacement of UML.

Most of the UML dynamic or "behavioral" diagrams (state, activity, collaboration, communication, sequence, timing, and interaction) can be viewed as a workflow for different perspectives. Rules might be considered the superset analog to OCL (object contraint language).

The idea is to have WF designer to the utlize the visual motifs of UML to get different views of a workflow. WF and class designer would then replace UML as a design, documentation, and "code generation" tool. WF, as opposed to UML/MDA, is closer or rather on the pavement. This assumes a philosophy that everything is essentially workflow and rules. Design of a software project may not be the primary focus of WF but it may be an extension.

I want to apologize after the fact. I am a non-technical stakeholder who has gone through the UML-MDA process. I liked the idea of MDA, in that you have the most skilled persons, i.e. architects, control the process. In practice, the UML-MDA paradigm requires great discipline that generally disipates in the heat of battle.

mmarsh at 2007-9-9 >