• Publications
  • Influence
Software architecture in practice
From the Book: Our goals for this second edition are the same, but the passage of time since the writing of the first edition has brought new developments in the field and new understanding of the important underpinnings of software architecture. Expand
  • 5,237
  • 428
  • PDF
Evaluating Software Architectures: Methods and Case Studies
List of Figures. List of Tables. Preface. Acknowledgments. Reader's Guide. 1. What Is Software Architecture? Architecture as a Vehicle for Communication among Stakeholders. Architecture and ItsExpand
  • 992
  • 104
  • PDF
ATAM: Method for Architecture Evaluation
We have developed an architecture analysis method for analyzing software architectures that has been developed and refined in practice over the past three years. Expand
  • 664
  • 80
  • PDF
The architecture tradeoff analysis method
This paper presents the Architecture Tradeoff Analysis Method (ATAM), a structured technique for understanding the tradeoffs inherent in the architectures of software-intensive systems. Expand
  • 641
  • 66
  • PDF
Software Architecture in Practice: Addison-Wesley
  • 757
  • 50
SAAM: a method for analyzing the properties of software architectures
We describe three perspectives by which we can understand the description of a software architecture and then propose a five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method). Expand
  • 660
  • 42
  • PDF
Scenario-Based Analysis of Software Architecture
We show how to exploit software architectural concepts to analyze2 complex software systems for quality attributes. Expand
  • 550
  • 38
  • PDF
Ultra-Large-Scale Systems: The Software Challenge of the Future
Abstract : The U. S. Department of Defense (DoD) has a goal of information dominance to achieve and exploit superior collection, fusion, analysis, and use of information to meet mission objectives.Expand
  • 580
  • 38
  • PDF
Quantifying the costs and benefits of architectural decisions
The benefits of a software system are assessable only relative to the business goals the system has been developed to serve. Expand
  • 230
  • 26
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. Expand
  • 249
  • 25