• Publications
  • Influence
Software architecture in practice
TLDR
This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.
Evaluating Software Architectures: Methods and Case Studies
TLDR
The ATAM-A Method for Architecture Evaluation focuses on using Quality Attribute Characterizations in the ATAM to evaluate Architecture as a Reusable, Transferable Abstraction of a System.
ATAM: Method for Architecture Evaluation
TLDR
The Architecture Tradeoff Analysis Method (ATAM), a technique for analyzing software architectures that has been developed and refined in practice over the past three years, is presented.
The architecture tradeoff analysis method
TLDR
The Architecture Tradeoff Analysis Method is a spiral model of design: one of postulating candidate architectures followed by analysis and risk mitigation, leading to refined architectures.
SAAM: a method for analyzing the properties of software architectures
TLDR
A five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method) is proposed and illustrated by analyzing three separate user interface architectures with respect to the quality of modifiability.
Ultra-Large-Scale Systems: The Software Challenge of the Future
TLDR
This work states that the U. S. Department of Defense has a goal of information dominance to achieve and exploit superior collection, fusion, analysis, and use of information to meet mission objectives, and these systems will push far beyond the size of today s systems and systems of systems by every measure.
Scenario-Based Analysis of Software Architecture
TLDR
The authors developed the Software Architecture Analysis Method, an approach that uses scenarios to gain information about a system's ability to meet desired quality attributes.
Quantifying the costs and benefits of architectural decisions
TLDR
This work argues that the software architecture is the crucial artifact to study in making design tradeoffs and in performing cost-benefit analyses, and offers an architecture-centric approach to the economic modeling of software design decision making called CBAM, in which costs and benefits are traded off with system quality attributes.
Software Architecture in Practice (Second Edition)
The architect is faced with a swarm of competing, if not conflicting, influences and demands, surprisingly few of which are concerned with getting the system to work correctly. The organizational and
...
...