A Study on Software Architecture Evaluation

  • Gu-Beom Jeong
  • Guk-Boh Kim
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3983)


This paper presents an approach to evaluate software architecture. Our approach is divided into three main areas of activities : the work involved in preparation, execution, and completion of the evaluation. Through performing these activities, architectural evaluation can be systematically performed centering around architectural design decisions that have profound impacts on the achievement of quality attributes.


Quality Attribute Functional Requirement Software Architecture Quality Requirement Evaluation Contract 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Kazman, R., et al.: The Architecture Tradeoff Analysis Method. In: The 4th IEEE International Conference on Engineering of Complex Computer Systems, August 1998, pp. 68–78 (1998)Google Scholar
  2. 2.
    Dobrica, L., Niemela, E.: A Survey on Software Architecture Analysis Methods. IEEE Transactions on Software Engineering 28(7), 638–653 (2002)CrossRefGoogle Scholar
  3. 3.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley, Reading (1998)Google Scholar
  4. 4.
    Bosch, J.: Design and Use of Software Architectures. Addison-Wesley, Reading (2000)Google Scholar
  5. 5.
    Clements, P., Kazman, R., Klein, M.: Evaluating Software Architectures. Addison-Wesley, Reading (2002)Google Scholar
  6. 6.
    Allen, R.: A Formal Approach to Software Architectures. In: CMU-CS-97-144, May 1997. Carnegie Mellon University (1997)Google Scholar
  7. 7.
    Abowd, G., et al.: Recommended Best Industrial Practice for Software Evaluation. CMU/SEI-96-TR-025. Carnegie Mellon University (January 1997)Google Scholar
  8. 8.
    Kruchten, P.: The 4+1 View Model of Software Architecture. IEEE Software 12(6), 42–50 (1995)CrossRefGoogle Scholar
  9. 9.
    Eriksson, H., Penker, M.: UML Toolkit. Addison-Wesley, Reading (1998)Google Scholar
  10. 10.
    Klein, M., Kazman, R.: Attribute-Based Architectural Styles. CMU/SEI-99-TR-022. Carnegie Mellon University (October 1999)Google Scholar
  11. 11.
    Inverardi, P., Mangano, C., Russo, F., Balsamo, S.: Performance Evaluation of a Software Architecture: A Case Study. In: Proceedings of the 9th International Workshop on Software Specification and Design, April 1998, pp. 116–125 (1998)Google Scholar
  12. 12.
    Medvidovic, N.: A Classification and Comparison Framework for Software Architecture Description Languages., UCI-ICS-97-02, University of California, Irvine (February 1996)Google Scholar
  13. 13.
    Clements, P., Bass, L., Kazman, R., Abowd, G.: Predicting Software Quality by Architecture-Level Evaluation. In: Proceeding of the 5th International Conference on Software Quality, October 1995, pp. 485–498 (1995)Google Scholar
  14. 14.
    Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns. Addison-Wesley, Reading (1995)Google Scholar
  15. 15.
    Buschmann, F., et al.: Pattern-Oriented Software Architecture – A System of Patterns. John Wiley & Sons, Chichester (2000)Google Scholar
  16. 16.
    Schmidt, D., Stal, M., Rohnert, H., Buschmann, F.: Pattern-Oriented Software Architecture – Patterns for Concurrent and Networked Objects. John Wiley & Sons, Chichester (2000)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Gu-Beom Jeong
    • 1
  • Guk-Boh Kim
    • 2
  1. 1.Dept. of Computer EngineeringSangju National UniversitySang JuSouth Korea
  2. 2.Dept. of Computer EngineeringDaejin UniversityPo ChonSouth Korea

Personalised recommendations