%0 Conference Paper %1 kazman_saam_1994 %A Kazman, R. %A Bass, L. %A Abowd, G. %A Webb, M. %B Software Engineering, 1994. Proceedings. ICSE-16., 16th International Conference on %D 1994 %K Analysis Architecture Method;modifiability SAAM;Software analysis;software analysis;user architecture cycle;software engineering;systems interface;formal interfaces; life maintainability;software modularity;software portability;software quality;organization quality;software reusability;user specification;software %P 81--90 %R 10.1109/ICSE.1994.296768 %T SAAM: a method for analyzing the properties of software architectures %X While software architecture has become an increasingly important research topic in recent years, insufficient attention has been paid to methods for evaluation of these architectures. Evaluating architectures is difficult for two main reasons. First, there is no common language used to describe different architectures. Second, there is no clear way of understanding an architecture with respect to an organization's life cycle concerns -software quality concerns such as maintainability portability, modularity, reusability, and so forth. We address these shortcomings by describing three perspectives by which we can understand the description of a software architecture and then proposing a five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method). We illustrate the method by analyzing three separate user interface architectures with respect to the quality of modifiability

@inproceedings{kazman_saam_1994, abstract = {While software architecture has become an increasingly important research topic in recent years, insufficient attention has been paid to methods for evaluation of these architectures. Evaluating architectures is difficult for two main reasons. First, there is no common language used to describe different architectures. Second, there is no clear way of understanding an architecture with respect to an organization's life cycle concerns -software quality concerns such as maintainability portability, modularity, reusability, and so forth. We address these shortcomings by describing three perspectives by which we can understand the description of a software architecture and then proposing a five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method). We illustrate the method by analyzing three separate user interface architectures with respect to the quality of modifiability}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Kazman, R. and Bass, L. and Abowd, G. and Webb, M.}, biburl = {https://www.bibsonomy.org/bibtex/2ed24bb8d3ad4638e033a686f2e337fd4/fritzsolms}, booktitle = {Software Engineering, 1994. Proceedings. ICSE-16., 16th International Conference on}, doi = {10.1109/ICSE.1994.296768}, interhash = {69e987e5a4fe996b3cb4cb9b66aab3bc}, intrahash = {ed24bb8d3ad4638e033a686f2e337fd4}, issn = {0270-5257}, keywords = {Analysis Architecture Method;modifiability SAAM;Software analysis;software analysis;user architecture cycle;software engineering;systems interface;formal interfaces; life maintainability;software modularity;software portability;software quality;organization quality;software reusability;user specification;software}, month = May, pages = {81--90}, timestamp = {2013-02-28T11:14:16.000+0100}, title = {SAAM: a method for analyzing the properties of software architectures}, year = 1994 }