The increase in number of integrated systems in today’s enterprise solutions necessitates dealing with dependency and environment failures in a systematic way. By modeling dependency failures at the architecture stage, system response to failures can be communicated, tested and implemented reducing the business risk and cost.
Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Nick Rozanski and Eoin Woods have continued their journey of building a comprehensive handbook on Systems Software architecture with the publication of the second edition of Software Systems Architecture. InfoQ spoke to the authors on a couple of new topics, the System Context viewpoint and Agile, that are covered in the latest edition.
Agile Modeling adheres to and aligns with Agile values and principles and should be one of the practices within your Agile toolkit. 2
InfoQ spoke with Lee and Celso about the Patterns-Based Engineering: Successfully Delivering Solutions via Patterns book, discussing patterns for working with patterns, MDD and the promise of reuse.
Text-based DSLs are useful, an custom editor for the DSL is even better. Concrete allows to build customized editors for JSON-based DSLs/Models. InfoQ talked to Concrete's creator Martin Thiede.
Just Enough Software Architecture book, by author George Fairbanks, focuses on a risk-driven approach to software architecture development. InfoQ spoke with George about the book and his thesis. 6
Andreas Kaltenbach explains how MSDS solves backward software programs compatibility problems by negotiating the differences between versions to ease the upgrading process. 4
This article introduces RGen, a modelling framework inspired by openArchitectureWare. RGen uses internal DSLs for defining metamodels and offers a full modelling stack for Ruby. 2
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