Skip to main content

Jorn Bettin has written this comment on the "Standardisation of Model Driven Approach"

Jorn Bettin has written this comment on the "Standardisation of Model Driven Approach":

Also, beyond the realm of MDA, in relation to model driven approaches and the use of domain-specific languages in general, there is the question of when and to what degree will standardisation occur. Usually the more domain-specific a language can be made, the more value it adds. Yet, the closer a domain-specific language gets to capturing part of the competitive edge of an organisation, the less incentive for industry wide "standardisation".

From my point of view standardisation will only happen if we could get a direct positive impact from it. So, this is actually very pragmatic. A very good example is the use of AndroMDA. I could imagine that there are a lot of organisations out there - which are all the user of AndroMDA - which have standardised their "DSL" based on AndroMDA DSL elements like Entity, Service, tagged values, etc. Why? Because you get directly benefits from it. You can generate your codes easily when you use AndroMDA DSL.

So, just a specification will not help to standardise anything (or at least it will take very long = OMG). I always take the example of JCP (Java Community Process). You need 3 components to be able to standardise APIs:
- Specification
- Reference Implementation
- Test Compatibility Kit


... and this is not the case with OMG. No reference implementation, no test compatibility kit. IMO, Open Source project like AndroMDA could bring the standardisation a step further. Just like succesful Open Source projects Hibernate, Spring, Struts, etc. which are de-facto standard and not de-jure standard.

Comments

Popular posts from this blog

Creating Spring Bean dynamically in the Runtime

In my training someone asked me whether it is possible to create an object (a Spring Bean) dynamically so you can choose which implementation you want to have in the runtime. So at the compile time you don't know what object actually should be created yet. The application should decide what object to be created based on a property file.

1. We create an annotation so we can mark the method which should be able to create the object dynamically:

...
package your.package;
...
@Retention(RetentionPolicy.RUNTIME)
public @interface InjectDynamicObject {
}
...
2. Use the new created annotation in your method which should be able to create the object dynamically:
... @Named("customerBo") public class CustomerBoImpl implements CustomerBo { ...     @Override @InjectDynamicObject public Customer getDynamicCustomer() {         return this.dynamicCustomer; } ...
3. Write an aspect with Pointcut and Advise which change the object returned by the method in the step 2:
... @Named @Aspect public class Dyn…

Software Development Macro and Micro Process

If you think that in year 2012 all companies which produce software and IT divisions in our world have already their optimized software development process, you are wrong. It seems that we - software architects, software developers or whatever your title is - still need to optimize the software development process in many software companies and IT divisions.

So what do you do if you enter a software company or IT division and you see following things:

1. There is a perfect project management process to handle all those development of software butit is a pure project management without a context to software development. So basically you only take care of cost, time, budget and quality factors. In the software development you still use the old fashioned waterfall process.

2. From the tooling point of view: you have a project management planning and controlling tool but you are still in the beginning of Wiki (almost no collaboration tool) andyou don't use issues tracking system to han…