Every complex software product has a variety of software architecture concepts that directly affect the code base. Which types of components do we have, how do we identify these components, how do we structure them and how are they allowed to depend on each other and through which interfaces. However, …
Today it seems like Microservices are the de facto standard for a system architecture, but do they really live up to the hype? The talk will show you an alternative approach – how we can tame complexity with the help of a clean, monolithic software architecture that is modular to …
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 …
Do you want to communicate more effectively? Do you want create better maintainable software? If so, come and listen to this presentation to get some hands on tips on techniques and tools to vizualize your software architecture.
In this article, Simon Brown discusses the impact of the Agile approaches on the conception and representation of software architectures. The main point of the article is that software developers seems to have abandoned the Unified Modeling Language (UML) or just haven’t learned it. The question is then: how would …
“Just Enough Software Architecture” is book that provides guidelines and models on how to include just enough 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 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 …
