Goal

Communicate the distinct advantages of systems that preserve the form of a model across the application lifecycle:

• The model is drawn by and for business people.
• They are NOT transformed into a different model for development.
• They are NOT converted to a different model for execution.

The model drawn by business people is the same model executed in the engine.

Goal is to have a clear message, so that industry analysts will know, and can communicate those things which a Model Transforming Strategy is good for, and those things that it is not. If analysts can communicate this, then users in the marketplace will learn of it, and can make more knowledgeable decisions.

Program Proposal

Plan B is simply to use grass roots approach: publish the ideas in the blog and then network around it. The bog posts will define terms to be used consistently by those talking about this.

Related Pages

• http://kswenson.wordpress.com/2009/02/09/model-strategy-preserving-vs-transforming/
• http://kswenson.wordpress.com/2009/02/11/model-strategy-analytics/
• http://kswenson.wordpress.com/2009/02/12/model-strategy-round-trip-agile-development/
• http://www.bp-3.com/blogs/2009/02/preserving-the-model/

• Support for Model Transforming Strategy
• Benefits Statement for Funding Participants
• Elevator Pitches
• WfMC
• Model Preserving Strategy Conf Call Nov 14 2008
• Model Preserving Strategy Conf Call Nov 21 2008
• Model Preserving Strategy Conf Call Dec 5, 2008
• Runtime Modification of BPEL