Interesting mail-discussion going on with some colleagues at the moment… can you e.g. adhere to MDA using Simulink or, being an OMG initiative and all, is UML (or UML-like modeling-languages) implied. Personally I don’t think that MDA contains any prescriptive view upon which modeling language to use… but some fit the purpose better than others.
What do you think?
Visar inlägg med etikett model driven architecture. Visa alla inlägg
Visar inlägg med etikett model driven architecture. Visa alla inlägg
torsdag 25 mars 2010
onsdag 2 december 2009
Execute this
I am currently having a late evening with the report on Model Driven Architecture and executable/translatable UML.
One thing that intrigues me is that during research, on MDA in particular, the notion of platform in the context of PIM and PSM (Platform Independent Model and Platform Specific Model) seems quite single-sided. In most MDA-papers I have yet to find a different meaning to platform than language + compiler + hardware. In other words MDA shall basically only be used to separate us from the implementation in software.
Why is there so little written about PIM/PSM where platform is put in a product context? Where the PIM is your model of the functionality independent on which final product in your palette it will end up in? And where the “PSM” is your “PIM” (in normal terms) for that specific product? This is nothing new and breath-taking in e.g. PLA-ideas but there isn’t a lot of practical reading where those two have been put together.
A practical approach from PIM, P for product or project then, to PIM (if needed) to PSM would be interesting to see (or create).
For a larger product company enabling this would probably yield a substantial improvement.
Time for a break and some serious running in -6degC.
One thing that intrigues me is that during research, on MDA in particular, the notion of platform in the context of PIM and PSM (Platform Independent Model and Platform Specific Model) seems quite single-sided. In most MDA-papers I have yet to find a different meaning to platform than language + compiler + hardware. In other words MDA shall basically only be used to separate us from the implementation in software.
Why is there so little written about PIM/PSM where platform is put in a product context? Where the PIM is your model of the functionality independent on which final product in your palette it will end up in? And where the “PSM” is your “PIM” (in normal terms) for that specific product? This is nothing new and breath-taking in e.g. PLA-ideas but there isn’t a lot of practical reading where those two have been put together.
A practical approach from PIM, P for product or project then, to PIM (if needed) to PSM would be interesting to see (or create).
For a larger product company enabling this would probably yield a substantial improvement.
Time for a break and some serious running in -6degC.
måndag 19 oktober 2009
Model Driven Architecture
During the past weeks I've been discussing Model Driven Architecture with some co-workers and done some soul-searching on my own.
To be honest I have difficulties to see the "architecture" in MDA... maybe my notion of architecture is on a higher layer of abstraction or maybe I simply don't understand.
To me MDA, as it is explained, looks more like Model Driven Design with the possibility to generate code.
Am I missing the point?
To be honest I have difficulties to see the "architecture" in MDA... maybe my notion of architecture is on a higher layer of abstraction or maybe I simply don't understand.
To me MDA, as it is explained, looks more like Model Driven Design with the possibility to generate code.
Am I missing the point?
Prenumerera på:
Inlägg (Atom)