Just Enough Software Architecture book, by author George Fairbanks, focuses on a risk-driven approach to software architecture development. George explains Architecture Modeling process from different perspectives such as Engineering Use Models, Conceptual, Domain, Design and Code Models. InfoQ spoke with George about the book and his thesis project on design fragments in software framework.
In this article, Andreas Kaltenbach explains how Model-Driven Software Development (MSDS) can help solving backward compatibility problems when creating a newer version of a software which can mean a new API or a new database schema that old clients cannot use. MSDS is used to negotiate the differences between versions to ease the upgrading process.
In this article, Wil Leeuwis argues there's a lot of old, well understood and practically applied theory that can help us harvesting the profits of the innovation part of the services-world.
We introduce the concept of Composite Oriented Programming, and show how it avoids the issues with OOP and reignites the hope of being able to compose domain models with reusable pieces. 13
If you want to build model-driven software you’ll need to devise a methodology based on ideas and experiences from others. Johan den Haan shares with us 8 gotchas of Model Driven Engineering. 15
Mat Wall and Nik Silver explain how their has been using Domain-Driven Design in an evolving and Agile environment, at high traffic news site guardian.co.uk. 15
Sven Efftinge, Peter Friese, and Jan Köhnlein pass on Model-driven software development best practices they have learned after years of increasing success applying MDD. 6
Architecture is often described non-tangible in documents or is entirely technology-driven. Markus Völter describes a third approach; to evolve a formal language of your architecture. 10
An overview of the emerging programming models in SOA including Windows Communication Framework (WCF), Java Business Integration (JBI) and Service Component Architecture(SCA). 4