Reed Little

TL;DR: This lecture maps the concepts and templates explored in this tutorial with well-known architectural prescriptions, including the 4+1 approach of the Rational Unified Process, the Siemens Four Views approach, and the ANSI/IEEE-1471-2000 recommended best practice for documenting architectures for software-intensive systems.

TL;DR: The theme of the work is that documenting an architecture entails documenting the set of relevant views of that architecture, and then completing the picture with documentation of information that transcends any single view.

TL;DR: This report represents another milestone of a work in progress: a comprehensive handbook on how to produce high-quality documentation for software architectures, tentatively titled Documenting Software Architectures, to be published in early 2002 by Addison-Wesley.

TL;DR: This report proposes an approach for capturing architecture information in a way that is consistent with agile methods, and compares the Software Engineering Institute's Views and Beyond approach for documenting software architectures with the documentation philosophy embodied in agile software-development methods.

TL;DR: A practical approach for documenting software architectures is presented, based on the well-known architectural concept of views, and holds that documentation consists of documenting the relevant views and then documenting the information that applies to more than one view.