We often think of software architecture as one of those things we just have to do right at the beginning of a project, often using fancy tools. This talk offers an alternative. What decisions would we make differently if we had the ability to rapidly evolve our architecture?
We all love pasta and spaghetti, right? Unless you are a software architect: these people who design and envision software systems from the ground up have developed an aversion to spaghetti throughout the years. When supporting the cutthroat business models of our era, it is fundamental to develop ways to evolve your software architecture, to …
“Just Enough Software Architecture” is book that provides guidelines and models on how to include just enough software architecture in your software development activities, following an Agile approach and using risk as the main criteria on how much architecture to include in your current software development activity.
This article describes the famous 4+1 View Model of Architecture proposed by Philippe Krutchen. The 4+1 View Model organizes a description of a software architecture using five concurrent views, each of which addresses a specific set of concerns. Architects capture their design decisions in four views and use the fifth to illustrate and validate them.