Does MDA mean OOAD?
I have just finished my thesis about MDA (in Czech). I have learned much about MDA. I have tried few many MDA tools. There was also chapter about combining MDA and SOA. See abstract below.
Does MDA mean OOAD? - that’s question that I was not able to answer in my thesis.
I mean MDA as described by MDA Guide V1.0.1 and MDA Foundation Model from OMG. The main statement (from my point of view) is: MDA is now too object oriented.
I learned that tools support OOAD (Object oriented analysis and design). The majority only transforms class models into static object structure. That’s useful. It could save time during developmnet phase. Etc…
But OOAD is not enough. The world is not composed only from objects (object model). There could by another views - service oriented, event oriented, hirearachical or data (document) oriented (mixture possible). Detailed example of OOAD inadequacies for SOA were described at Elements of Service-Oriented Analysis and Design. But there is no Rational for SOA, if you want to do SOA you have to use at least five different tools. Does this mean that is too hard to make homogenous tools supporting SOA?
October 20th, 2008 at 5:33 pm
MDA vs OOAD
ooad is a way of system development by defining objects and their relationships between them. MDA further enhance this view by allowing object definition to be , first , specified in platform independent way and then transform it a specific implemention model. the key word in MDA here is “automatic transformation” and “metamodel”