CG2012 Summary, day 3

CG2012 Summary, (part III)

This is the last post in my series of summaries of the Code Generation 2012 conference. After having reviewed the LWC day and days one and two, this third and last day concludes my personal report. Some of you will remember my intense tweeting in such days under the hashtag #cg2012, but I had a good reason: such tweets help me document the event and log the activities, which actually makes the process of writing these summaries possible. So, let’s stop meta-posting and dive into the content of the day D.

Friday 30th, day 3

The last day of the conference started with the keynote “Speed and Innovation through Architecture” by Jan Bosch (@JanBosch). This was very provocative in that it addressed MDSD and Software Architecture within the context of innovation in industrial contexts and presented it from a business perspective: opposite but complementary to the technical content that usually drives a CG session. Jan supported his talk with examples drawn from Nokia, Siemens, and other companies he is either currently working with or worked with prior to his current academic position.

Some of the pearls (argued by the audience in twitter latter) in his talk were:

  • The market is moving from products to services
  • The need for the speed: R&D departments should have very short innovation cycles. Speed is the primary feature to achieve. (Time to Market)
  • Moving faster: no efficiency improvement will outperform cycle time reduction.
  • Traditional SW development does not scale. We need to change the way we create SW.
  • Amazon releases new software every 11 seconds…
  • R&D as an Experiment System
  • Decisions should be based on DATA, not opinions
  • Learning: the company running the most experiments against the lowest cost per experiment wins
  • There are things you can’t predict until you perform tests
  • Lean and Agile as Scale: as a dancing elephant (see the photo in the slides)


Some tweets reactions about it:

  • @delphinocons: Reducing dev. cycle time is 10x more beneficial than improving dev. efficiency I can see him build the case for MD(S)D from here. #cg2012
  • @tvdstorm: No more heavy process. This is going the way of the dinosaurs. @JanBosch #cg2012
  • @stevekmcc: @JanBosch 10% more revenue vs. 10% less dev costs (“efficiency”) assumes rest of org has zero incremental cost & demand is infinite #cg2012
  • @delphinocons Amazon releases new software every 11 seconds… wow. @JanBosch @ #cg2012
  • @pmolinam  “Learning: the company running the most experiments against the lowest cost per experiment wins” @janbosch #cg2012 #innovation –> Google
  • @tvdstorm: @JanBosch’s keynote: crowd sourcing the scientific method at a very high speed. Continuous integration -> deployment -> AB testing. #cg2012
  • @pmolinam Arquitecture goals accordingly to @janbosch Simplify, Decoupling, Lean and agile at scale, End to end quality, fight design erosion #cg2012
  • @pmolinam “Interconnected teams and organizations asymptotically reduce productivity to zero” -> Twitter? @janbosch #cg2012 #innovation
  • @pmolinam Decoupling: NO versions! only the deployed one! @janbosch #cg2012 #innovation <- Hard to achieve out of the web
  • @pmolinam Very great keynote! by @janbosch #cg2012 #innovation very inspiring and totally on-topic.
  • Great slide @janbosch #cg2012 implication http://t.co/OBiSKfjZ
  • @MarkDalgarno: Every engineer at @intuit spends at least 1 day a year with a consumer seeing how their products are used in practice. @janbosch at #cg2012

As commented, this was a great keynote with respect to rethinking the role of MDSD within business organizations and how MDSD is still a great and undiscovered lever to drive innovation inside a company from within the IT and R&D departments. Dear CIOs, take note.

After the keynote, time for a quick coffee and I move quickly to prepare my session on “Multichannel User Interfaces”

In this session, I presented some issues we are working on at Icinetic. When developing a new service or product, UIs are expensive to develop if you have to offer the service in the leading edge mobile platform. The market is fragmented and thus provides several competing platforms and technologies with which to build a UI: XAML/C#, JavaFX/Java, Android, Objective-C/Cocoa, HTML5/Javascript with a JS framework, etc. The technology is changing quite fast and there is an open war to determine who will dominate the mobility space. Developing for any platform’s target UI technologies is neither cheap nor maintainable; is well: they don’t scale. It is in this context where Modeling device independent User Interfaces makes complete sense for business software. I demonstrated one of the prototypes we are building — called Oz UI — which utilizes my work on conceptual user interface patterns and is able to declaratively specify and prototype the UI then generate an implementation based upon any of a set of different widget technologies.

I got a very good feedback from the audience and feel that there is space for creating new tools in this domain that further alleviate the effort required by developers to work within the plumbing present in every development framework.

After the session and with the feeling of work completed, it was time for lunch and relaxation.

My last technical session was: tercnoC xatnyS srettaM (Concrete Syntax Matters) by Steven Kelly. The superbly selected title speaks for itself: when designing a new language there are many considerations to be taken into account in order to make the language pleasant for your users. Usability, concreteness, unambiguity, homogeneity, human perception of colors, forms and text are all relevant when addressing the design of a new language. The success of your language — measured in number of users — will be influenced greatly by these choices. See Steven in action.

Following our last coffee/orange-juice break, we all moved to the closing session: a panel discussion on “Code Generation – how far have we come in 5 years?”, lead by Andrew Watson, who introduced the topic and the panelists: Wim Bast, Steven Kelly, Darius Silingas, and Markus Völter.

Some ideas that were discussed:

  • MDSD Commoditization
  • Moving from a technical discourse to the necessary business discourse
  • The complexity of SW is ever growing; MDSD helps manage the complexity

Some interesting tweets about the panel supporting it:

  • @lmontrieux: Final panel session begins at code generation #cg2012 http://t.co/ffQOqyQ6
  • @delphinocons: Wim Bast: competing DSLs and LWBs is good for innovation, but bringing MD(S)D to the market requires commodity as well. #cg2012 closingpanel
  • @pmolinam @CompSciFact “Before you can design a good DSL, you have to understand the D.” On-topic for #cg2012
  • @tvdstorm: Need: live prototyping environments to be able to try out many different designs. Modeling needs immediacy, liveness and directness. #cg2012
  • @delphinocons Wim Bast/Darius Silingas: we have to avoid focusing too much on the technical side in favor of the business benefits of MDSD. Agree! #cg2012
  • @pmolinam On SoC and abstractions in DSLs #cg2012 Panel
  • @stevekmcc We are building the complex systems as ever. DSL helps in this race. #cg2012

Summing up

Finally, I present my personal conclusions on the State of the Art in MDSD based on what I have seen at CG2012:

  1. Two main lines of work have arisen in MDSD seen this year:
    • Bottom-up using a low-level general language and adding extensions that raise the abstraction level (eg.: mbeddr over C or Webr-DNQ over Java) for a specific purpose (domain), and
    • Top-down using a high-level DSL/language with a specific, targeted level of abstraction in order to describe a domain (hiding technology details and other concerns) upon which code generation is applied (samples: Radarc, IFML, MetaEdit+).
  2. More effort is needed to explain ROI for potential MDSD consumers (customers).
  3. Increasing complexity and diversity (mobile) in technology pushes the market ever closer to MDSD (as there are no other choices).
  4. Technology independence (one of the foremost qualities of systems developed via MDSD) provides even greater value when technology is undergoing rapid advances (see the mobile arena for example).
  5. Some MDSD technologies are powerful yet also rather complex; more work is required to simplify their presentation in order to increase user adoption.
  6. User Interface modeling is gaining momentum this year (with at least four sessions), that being a great and challenging DSL domain.
  7. The cloud provides opportunities for applying MDSD; this context already showing adoption in transparent infrastructure (see Mendix for a sample), deployment and configuration (cloud operation).
  8. Multi-core CPUs provide opportunities for executing DSL specs with efficient parallel processing.


As always, CG2012 was a great opportunity to take the pulse of the MDSD community, providing a good overview of the current problems and areas of research. If you want to get in the loop don’t miss the next edition — join us in 2013.

I want to thank the work of Robert McCall. He contacted me and volunteered for polishing my sometimes rusty English and making the full text more readable.

Post a comment.