2. Practical Challenges
MDA is usually associated with UML and related
standards. Any application has two parts, the model and
the actions on the model.
Model is easy to express using UML. But the actions are
very difficult to express using the models. Action scripting
language was designed to implement logic on UML. Once
again we are trapped in another language.
The problems with existing languages are, they don’t
change as the model changes. Thus lots of recording is
required to implement new model changes. This makes
MDA practically very less value.
4. How we Achieve?
We decided to create an MDA for Business applications
like ERP. Our model was the ER diagram. For action part,
we could have used stored procedures and triggers
instead we designed our own XML schemas optimized for
SQL based logic.
To mask the end users from the complexity of XML
schema, we use business patterns. Business patterns are
logic that are used often such as auto number generation,
primary key, unique key, foreign key, master detail etc.
Using the business patterns and model complete
application is generated in Java, PHP & C#. The code
generator can be extended to other languages too.
5. DB Model Vs. Business Pattern
Advantages of Database based modelling approach
• The model is easy to realize.
• The model can be tested with test data easily.
• Knowledge of UML is not required.
Advantages of business patterns
• It is easy to use.
• The intention of the logic is very clear.
• Faster development
7. Portfolio
• Some of the Sample Applications built using
practical MDA approach:
• Online QUIZ –
www.goralsoft.com/quiz/login.aspx
• BTS (Bug Tracking System) -
www.goralsoft.com/bts/login.aspx
• Examination System -
www.goralsoft.com/exam/login.aspx
• DB Mail –
www.goralsoft.com/dbmail/login.aspx