An approach to software architecture analysis for evolution and reusability.
CASCON, page 15. IBM, (1997)Description
The paper introduces a framework for architecture Information Gathering and Analysis. This framework consists of 4 different activities that are performed iteratively instead of sequential.
First off, _gathering_ of information is done in four different categories of information, Stakeholder information, Architectural information, quality information and scenario's.
Secondly, _modeling_ of the information is done in order to map all of the different information sources into reusable artifacts.
_Analyzing_ of the data is done by focusing on specific software architecture analysis. In this case, the SAAM method is adopted and extended.
Lastly, _evaluating_ of the analyzed data results in recommendations, identification of "hot spots" in the architecture and strategies for mitigation of the hot spots are enumerated.
In order to guide the architectural analysis the authors adopt four different views in order to get a complete description of the architecture. These views are:
1) static views
2) Map views
3) Dynamic views
4) Resource views
Each of the views is explained together with several different types of diagrams that can help in visualizing these views for stakeholders.
In the end, the paper gives some examples of Scenario's and analyzes and explains the lessons learned from them.
Links and resources
Tags
community
@ericbouwers's tags highlighted