Boyan Mihaylov covers his experience when working with both traditional waterfall software architectures and agile ones. He depicts the similarities and differences between these with a focus on three areas: the specifics of the software architect role, the timespan of the software architecture, and the output of the software architecture.
Today’s software applications have a lot of concurrent tasks that are distributed over multiple threads, processes, processors and PCs. This article introduces a visual modeling technique to describe and specify the application’s execution architecture. Within Philips Healthcare the Unified Execution Diagram has proven to be very useful for designing and documenting the execution architecture.
In this article, author discusses Architectural Refactoring (AR) techniques to improve the quality attributes without changing the system's scope and functionality. He also provides a TaskCentric Template and Architectural Refactoring Catalog.
In this article, authors present an empirical study about the software architecture practices for managing non-functional requirements and decision making in software development processes. 2
This article shares a simple technique used to address problems such as a system’s intended functionality but also qualities such as performance, reliability, portability, and availability.
Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition. 1
InfoQ spoke with Paulo Merson, co-author of Documenting Software Architectures: Views and Beyond book, on software architecture documentation and how it can help the design of software applications.
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