ABSE shows that software modeling can be both agile and pragmatic.
ABSE features a very simple and pragmatic approach: You can build reusable assets (Atom Templates) that you can immediately combine and (re)use in your projects. These metamodels will map concepts to code.
Atom Templates are made up of parameters that you can add according to your needs. Then you can add code snippets and, if you want a more advanced behavior, add some generation code. So, an Atom Template can be as simple as a code snippet with parameter substitution, and as complete as a full-fledged mini-program. Whatever your needs are, Atom Templates can be configured to generate your own code (no canned third-party code) and then grow with you whenever your development practices evolve.
The typical modeling workflow using ABSE and AtomWeaver:
1 - Create one or more Atom Templates
2 - Define their parameters
3 - Add code snippets or generation code as necessary
4 - Use/reuse by instantiating those Atom Templates on your project
5 - Generate code
6 - Change parameters, refactor, create, instantiate more Atom Templates
7 - Go to any previous step...
How much easier can Model-Driven Development get?
See how it works! Click here. |
Model-Driven Development was off to a bad start...
Most software architects that had their contact with OMG's standards, namely the Unified Modeling Language (UML), Model-Driven Architecture (MDA) and the Meta-Object Facility (MOF), know that these technologies, although mature and capable, are overly complex, and take months, if not years, to get a hold on them. Many past attempts at using MDA have failed and many developers got suspicious about every other form of modeling.
"UML has become complex and clumsy", wrote Ivar Jacobson, one of UML's inventors. Other industry analysts like Scott Ambler think that MDA/UML/MOF are complex and not a viable future option.
|
