Steven Kelly and Risto Pohjonen continue their hands-on session developing apps with MetaEdit+. (see: Moving From Coding To Model-Driven Development: Hands-On with MetaEdit+, Part 1)
Risto Pohjonen and Steven Kelly conduct a hands-on session using MetaEdit+ to create several graphic DSLs.
Marina Haase runs a highly participatory session collecting and analyzing ideas meant to help understand how MDSD works, and to uncover new techniques and tools.
Pedro J. Molina discusses the concepts behind UI and challenges met trying to model user interfaces, and how code generation can be used to create UIs.
Richard Pawson discusses a case study of a large pure OO project for the Irish government, presenting the challenges met, the reason for choosing pure OO, and lessons learned implementing it.
Tim Trew presents several model-driven software development scenarios along with suitable testing approaches, contrasting the roles of MDSD and model-based testing.
Stéphane Bégaudeau discusses Acceleo, an open source code generator based on EMF and MOFM2T, presenting its basic concepts, how it was created, how it can be improved, deployed, and used.
Darius Silingas discusses Test-driven Modeling, Model-driven Requirements Management and System Documentation, and Architecture Planning & Code Review, noting that MDD is more than code generation.
Heiko Behrens shows how to create an iPhone domain specific language using model-driven software development.
Eric discusses the need for strategic thinking an how early design decisions have major impact on the organization and the entire development process. He uses the lens of DDD Strategic Design principles (emphasizing "Context Mapping" and "Distilling the Core Domain") to show how to avoid strategic failures and achieve strategic successes. Winning strategy starts with the domain.
Eric Evans reviews what he has learned in the 5 years since the publication of Domain Driven Design - what works, what doesn't work, and how to conceptualize and describe it all. He argues that the fundamentals have held up well but there are differences in how I do things and look at things now. He also describes some new patterns and talks about changes of emphasis for existing patterns.
Sir Tony Hoare discusses the relationship between the science of computing and the engineering of software. First, he looks at the general concerns of science (e.g. long term, ideal, formality) and engineering (e.g. short-term, adequacy, and dependability) before delving on the interdependencies of the two viewpoints. He concludes with a vision of what software will be like: "Someday ...".