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. He took them through the steps needed to create a textual DSL from defining the grammar to processing a domain model.
In this presentation, John Steven talks about modeling security threats as a way to discover, understand and counteract threats while designing the system architecture. John presents threat modeling through examples focusing on authentication, authorization and session management.
Picture a system so large it cannot be comprehended. Can such a system be "designed" in any conventional sense? Will machines help design it? Will it help design itself? How will it keep running? Will it be alive? 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. Both the problem space and the solution space are described by models, using a model-to-model transformation to map problem space variability to solution space variability.
This talk introduces two broad principles for strategic design. 'Context mapping' addresses the fact that different groups model differently. 'Core domain' distills a shared vision of the system's "core domain" and provides a systematic guide to when "good enough" is good enough versus when to push for excellence.
This talk will outline some of the foundations of domain-driven design:How models are chosen and evaluated;How multiple models coexist;How the patterns help avoid the common pitfalls, such as overly interconnected models;How developers and domain experts together in a DDD team engage in deeper exploration of their problem domain and make that understanding tangible as a practical software design.
Mark shares tips and tricks focused on maximizing the development strength of your team. This session filled with real-world examples will cover all the benefits, one of the greatest being that a small team can produce with the force of a large one, and compete on the same level as much bigger teams who are still working with standard architectures.
Bob Martin of Object Mentor presents the first of his five principles of agile design. Beginning with an explanation of the real purpose of object-oriented design - the management of dependencies - Bob walks through a code example to illustrate how dependencies can be managed with abstractions, and that good designs are those in which high-level abstractions do not depend on low-level details.