Heiko Behrens shows how to create an iPhone domain specific language using model-driven software development.
Eric Evans advocates on gradual blending of modeling and design into iterative development in an attempt to create a solution that expresses the domain and is flexible enough to support changes.
Don Box and Amanda Laucher present “M”, a declarative language for building data models, domain models or external DSLs. Don Box's demos show some of M’s features and latest changes of the language.
Eoin Woods explains how Barclays Global Investors (BGI) designed Apex to meet the challenges it faces and the Java technologies which were chosen for an architecture with variations on standard J2EE.
Stefan Tilkov offers guidelines for the architect looking for a solution to his problem. Should it be a generic or a specific one? He compares several such solutions outlining the pros and cons.
Tim McCarthy talks about preserving the purity of the domain model while using frameworks. The presentation is targeted at developers and demoes a .NET SharePoint real application.
Janos Sztipanovits attempts to tackle the complexity of large scale systems integration by approaching software, systems and control engineering convergence through model-based design.
In this presentation filmed during QCon London 2008, Markus Voelter tried to convince the audience that writing a textual external DSL is fairly straightforward and simple.
John Steven talks about modeling security threats as a way to secure a system while designing its architecture. John focuses on authentication, authorization and session management.
Can a system that is so large it cannot be comprehended be "designed" in a conventional sense? The foundations of computing are about to change. In this talk, Richard P. Gabriel explores why and how.
In this talk, Markus Völter illustrates how model-driven and aspect oriented software development help addressing the challenge of managing variability in product line engineering.
This talk introduces two broad principles for strategic design: 'Context mapping' - different groups model differently and 'Core domain' - the distilled shared vision.