The Model Driven Software Network

Raise your level of abstraction

The program of Code Generation 2010 conference included BoF-sessions and in one of them, titled “Build or Buy”, we identified different providers of automation (languages and generators) and discussed the related pros and cons.  Within one hour we did not had time to discuss if there are any differences on initial definition, maintenance or ownership, but generally the following were mentioned:

 

A tool vendor provides:

+ a “complete” package

+ quality of generator due to a bigger user base

- dependency on the vendor and particularly the features and their release schedule

- no competitive advantage as competitors have the same automation

 

Developed in-house:

+ full control

+ learn and gain knowledge of the development process

- harder to introduce

(+/-) important to remember and document everything (+ because it allows the company better understand what they are doing, - because it requires resources)

 

Developed by consultant

+ enables quick start

+ extra resource, especially for the initial phase

- knowledge disappears when exit (thus consulting mainly in the early phases)

 

The list of obviously not complete, but summarizes the discussion topics. Most importantly it provides a good starting point for extensions and debate…

 

Views: 1

Reply to This

Replies to This Discussion

Thanks for this feedback.
I agree with almost everything. But I would like to discuss some points :
- The first one is that we often see a tool vendor sending a guy to work with clients developers. So this is a positive point to introduce MDE.
- The second one is if the consultant share his knowledge with clients developers, the knowledge doesn't disappears, and you can also sign a maintenance/help contract with the vendor.

My 2 cents,

Regards,

Xavier

RSS

Badge

Loading…

© 2012   Created by Mark Dalgarno.   Powered by .

Badges  |  Report an Issue  |  Terms of Service