Suppose that your company has just purchased another company and that you've been given the task of merging a system in your company with a similar system in the purchased company. If you're given the resources to produce whatever architecture documentation you need, what views would you call for, and why? Would you ask for the same views for both systems?
Some architects speak of a "security view" or documentation of a "security architecture." What do you suppose they mean? What might this consist of ?
How would you make a cost/benefit argument for the inclusion or exclusion of a particular view in an architecture documentation package? If you could summon up any data you needed to support your case, what data would you want?
Software Architectures and Documentation
Part I. Software Architecture Viewtypes and Styles
The Module Viewtype
Styles of the Module Viewtype
The Component-and-Connector Viewtype
Styles of the Component-and-Connector Viewtype
The Allocation Viewtype and Styles
Part II. Software Architecture Documentation in Practice
Documenting Software Interfaces
Choosing the Views
Building the Documentation Package
Other Views and Beyond
Rationale, Background, and Design Constraints