In this article, authors present an empirical study based on a survey about the software architecture practices for managing non-functional requirements (NFRs) and decision making in software development process. They also discuss about how these requirements are elicited, documented, and validated at different organizations.
Often, requirements elicited from stakeholders describe a system’s functionality but fail to address qualities such as performance, reliability, & availability. Documenting these requirements is often overlooked because there are implicit assumptions that the system will perform to expected levels. This article describes a process developed on the idea of persona sketches to address this problem.
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.
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