advising on IT-business alignment
IT-business alignment about us blog our services articles & reports resources your profile exposure
blog
blog
Saturday, September 13, 2008

Ignore the spin: Microsoft's membership of the OMG is good news for all concerned

Tony Baer's one of the analysts who's picked up on Microsoft's recent announcement that it's joining the OMG and backing UML and BPMN. His post is pretty interesting and outlines some of the relevant history - particularly relating to DSLs and the OMG's UML. But I'd like to add to that, and talk a bit about what the announcement means to the IT industry and the wider community of enterprise software developers.

Ignoring the "bringing modelling to the mainstream" spin that Microsoft has put on the announcement, Microsoft joining the OMG is a good thing for all concerned. Modelling is already a mainstream activity to most involved directly with the production of software, whether in the software vendor community or the wider software developer community. What it isn't, for the most part, is consistent, fully-integrated or shared within and across organisations - or seen by enterprises as something with real strategic importance.

Modelling holds great powers for shared communication between stakeholders. Through the power of abstraction and collective representation, model-driven development is an efficient and effective way of communicating requirements, goals and outcomes against the backdrop of existing constraints and platforms, and then automating the activities of the delivery process (i.e. development, testing and production) to ensure that what is deployed works how it was intended to (and to a sufficient level of quality).

So Microsoft's commitment to the OMG, simply put, finally gives model-driven software development a truly united voice - and also an united industry body for driving the education and strategic importance of modelling to the wider community. The environment and process framework created and managed by the OMG for collaboration, sharing strategy, and generating best practices that ultimately get incorporated into standards, has strong input from end user organisations and commercial vendors alike. A supply community that is united behind a common industry body is an important criterion for helping to drive modelling and model-driven development being seen as strategically important activities beyond the confines of the software vendor community.

Ultimately this announcement says a lot about how far both Microsoft and the OMG have come (in equal measures), the importance of modelling for the future of software for all concerned – enterprises in particular – and a recognition from Microsoft that it does actually need the OMG. The OMG needs Microsoft too (but perhaps a little less so in my opinion).

Microsoft joins the OMG with proven technology and a vision that makes it as good a first-class citizen as IBM with its Rational toolset and strong contribution to modelling technology (an aside: the Microsoft-OMG "war" was never really about the OMG per se, but rather about IBM Rational's dominance). Microsoft has realised the power and importance of UML and the wide adoption within the market. As Tony correctly mentioned, this was vital if Microsoft was to progress with Oslo.

The outcome here is that debate (and vital energy) is no longer focused on the political and market agendas of the modelling tool vendors. Don't get me wrong, there are still political and market agendas in play, there always will be. But for the meantime and in general these will play out more "behind the scenes" than before - and that has to be good for everyone.

Labels: , , , , , ,

Comments:
You write about "Microsoft's commitment to the OMG". I'll wait and see before calling it that. What I see so far, is "Microsoft's membership in OMG", which is different. All it tells me is that Microsoft is considering using the OMG to achieve its goals.

It's worth looking into what happened at DMTF with WSDM and WS-Management. WSDM was not a DMTF standard but there was some agreement to use it as SOAP-based management protocol.

Microsoft did what was needed to get DMTF to throw this away (in practice, not officially) and instead take Microsoft's WS-Management as a replacement.

You can call this "Microsoft's commitment to DMTF" if you want. But it's a commitment to the org after they reshape it, not to the org as it stood before. Same thing might apply to OMG now. We'll see.

In effect, their success with DMTF might be the precedent that makes them confident that they can walk into an org in which IBM has a lot of influence and take over control from them.

I am also surprised that no-one is talking about what this OMG move means for SML, now at W3C.

And just to be clear, all in all I still think it would be a good thing for Microsoft to engage the OMG with its recent modeling efforts. I too am intrigued by Oslo.

PS: I have all kinds of personal involvement with the specs mentioned above. Definitely not a neutral observer.
 
Thanks for the comment William. I was following developments with WSDM and WS-Management. Microsoft may well have joined the DMTF with a view to getting WS-Management adopted in preference to WSDM and I am obviously not in a position to comment on what happened within the DMTF. However, your analysis suggests that Microsoft had a "special" voice in the DMTF which allowed it to speak louder than the other participants and get its way against the wishes of others.

I have also been following Service Modeling Language and it'a not ovcious to me what the linkage is between Microsoft's membership of OMG and SML given that they are operating in different domains. Those domains should be related if the end-to-end lifecyle management of software, from development through to operations, is to be achieved but I am don't think that relationship has been clearly established, yet - by Microsoft let alone the broader community. Does it have anything to do with the fact that IBM is also involved in SML? I (and I am sure others) would be interested in your insights.
 
I wrote a bit about SML here, where I describe my view that Microsoft was pushed towards using XSD, which turned out to be an error. SML came from the System Center guys. My impression is that they are now in the back seat wrt to app modeling, now that Oslo has taken off, driven by the guys from the developer side of the house. I think SML is going to be Oslo roadkill (assuming it wasn't dead already). Unless IBM runs with it.
 
Post a Comment

<< Home


Burn this feed
Burn this feed!

Creative Commons License
This work is licensed under a Creative Commons License.

Blog home

Previous posts

Links for 2008-09-11 [del.icio.us]
IBM, Business Event Processing, and CEP: behind th...
Links for 2008-09-12 [del.icio.us]
ECM vendors collaborate on interoperability standard
Links for 2008-09-08 [del.icio.us]
Software AG goes in an interesting direction for S...
Links for 2008-09-07 [del.icio.us]
Links for 2008-09-04 [del.icio.us]
A new MWD FM podcast series: Software Delivery InF...
Links for 2008-08-28 [del.icio.us]

Blog archive

March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009

Blogroll

Andrew McAfee
Andy Updegrove
Bob Sutor
Dare Obasanjo
Dave Orchard
Digital Identity
Don Box
Fred Chong's WebBlog
Inside Architecture
Irving Wladawsky-Berger
James Governor
Jon Udell
Kim Cameron
Nicholas Carr
Planet Identity
Radovan Janecek
Sandy Kemsley
Service Architecture - SOA
Todd Biske: Outside the Box

Powered by Blogger

Weblog Commenting and Trackback by HaloScan.com

Enter your email address to subscribe to updates:

Delivered by FeedBurner