James Kovacs explains how to use TDD and BDD to focus the architectural efforts on the high-value areas of the code in order to obtain just-in-time software architecture.
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.
Rick Bullotta and Emil Eifrem discuss how to use graph databases to model the real world, people, systems and things, talking advantage of the relationships between various data elements.
David Starr presents some of the tools in Visual Studio Ultimate 2010 helpful for building an application’s architecture: Architecture Explorer, Dependency Graphs, UML Modeling, and Layer Diagrams.
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 Evans advocates on gradual blending of modeling and design into iterative development based on a correct and deep understanding of the domain, avoiding both “analysis paralysis” and the “easiest solution” for a user story, in an attempt to create a solution that expresses the domain and is flexible enough to support future variations of the model.
Don Box and Amanda Laucher present “M”, a declarative language for building data models, domain models or external DSLs. Most of the presentation consists of Don Box doing hands-on code writing demoing some of M’s features and latest changes of the language.
Eoin Woods explains how Barclays Global Investors (BGI) designed Apex, a new porfolio management system, to meet the challenges it faces and why BGI chose to combine mainstream, boutique and open source Java technologies, including Oracle, WebLogic, Spring, Swing, JIDE, Flux, CPLEX, MVEL and XStream, to create an architecture with some interesting variations on the standard J2EE form.
What is better, a generic solution or a specific one? Stefan Tilkov’s answer is “It depends.” He compares XML vs HTML, DSM-UML, Internal-External DSL, SOAP-REST, and others, outlining the advantages and disadvantages of each solution, showing that there is no certain answer to an architect’s quest to solve his problem, but there are some guidelines helping along the way.
In this presentation recorded during QCon SF 2008, Tim McCarthy talks about preserving the purity of the domain model while using frameworks. Frameworks can be very useful when developing applications, but they can present some pitfalls, mudding the domain, if they are not used properly. The presentation is targeted at developers.