As the field of software architecture has evolved over the past decade, there is much more to say, many more do we know, and much more we can reflect on from what has worked? And what hasn t? And writers here to do all this, and much more.? ? From the Foreword by Grady Booch, IBM Fellow Software architecture conceptual glue that holds every phase of a project with many stakeholders? It is widely recognized as an important element in modern software development. Documenting Software Architecture, Second Edition, provides complete and current guidelines for the most part, regardless of language or notation, of how to capture the architecture in a form commonly understood. This book has rules for sound documentation, objectives and strategy documentation, views and architectural styles, documentation for software interfaces and software behavior, and templates to capture and manage information to generate a coherent package. New and better in this second edition: The scope of architectural styles such as service-oriented architecture, multi-tier architecture, and modelsGuidance data for documentation in the development of treatment environmentDeeper Agile documentation of rational, reflecting industry best practicesImproved template, reflecting years of use and feedback, and more new layout documentation optionsA example, comprehensive (available online), display the documentation of a web-based guide systemReference this service-oriented architecture for three languages important documentation: UML, AADL, and SySML