Abstract
Software architecture (SA) evaluation is a quality assurance technique that is increasingly attracting significant research and commercial interests. A number of SA evaluation methods have been developed. Most of these methods are scenario-based, which relies on the quality of the scenarios used for the evaluation. Most of the existing techniques for developing scenarios use stakeholders and requirements documents as main sources of collecting scenarios. Recently, architectures of large software systems are usually composed of patterns and styles. One of the purposes of using patterns is to develop systems with predictable quality attributes. Since patterns are documented in a format that requires the inclusion of problem, solution and quality consequences, we observed that scenarios are, though as informal text, pervasive in patterns description, which can be extracted and documented for the SA evaluation. Thus, we claim that the patterns can be another source of collecting quality attributes sensitive scenarios. This position paper presents arguments and examples to support our claim.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2nd edn. Addison Wesley, Reading (2003)
Clements, P., Kazman, R., Klein, M.: Evaluating software architectures: methods and case studies. Addison-Wesley, Boston (2002)
Lassing, N., Rijsenbrij, D., Vliet, H.v.: The goal of software architecture analysis: Confidence building or risk assessment. In: Proceedings of First BeNeLux conference on software architecture (1999)
Kazman, R., Klein, M., Barbacci, G., Longstaff, T.: The Architecture Tradeoff Analysis Method (1998)
Lassing, N., Bengtsson, P., Bosch, J., Vliet, H.V.: Experience with ALMA: Architecture-Level Modifiability Analysis. Journal of Systems and Software 61, 47–57 (2002)
Bengtsson, P., Bosch, J.: An Experiment on Creating Scenario Profiles for Software Change. University of Karlskrona/Ronneby, Sweden (1999)
Bass, L., Bachmann, F., Klein, M.: Deriving Architectural Tactics-A Step toward Methodical Architectural Design (2003)
Bushmann, F., Meunier, R., Rohnert, H., Sommerlad, P., Stal, M.: Pattern-Oriented Software Architecture - A System of Patterns. John Wiley&Sons, Chichester (1996)
Shaw, M., Garlan, D.: Software Architecture: Perspectivies on An Emerging Discipline. Prentice-Hall, Englewood Cliffs (1996)
Kazman, R., Abowd, G., Bass, L., Clements, P.: Scenario-based analysis of software architecture. IEEE Software 13, 47–55 (1996)
Dobrica, L., Niemela, E.: A survey on software architecture analysis methods. Software Engineering, IEEE Transactions on 28, 638–653 (2002)
Fowler, M.: Patterns of enterprise application architecture. In: The Addison-Wesley signature series, pp. xxiv, p. 533. Addison-Wesley, Boston (2003)
Marinescu, F.: EJB design patterns: advanced patterns, processes, and idioms, pp. xxii, p. 259. John Wiley, New York (2002); [1] folded leaf
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2004 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Zhu, L., Babar, M.A., Jeffery, R. (2004). Distilling Scenarios from Patterns for Software Architecture Evaluation – A Position Paper. In: Oquendo, F., Warboys, B.C., Morrison, R. (eds) Software Architecture. EWSA 2004. Lecture Notes in Computer Science, vol 3047. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-24769-2_19
Download citation
DOI: https://doi.org/10.1007/978-3-540-24769-2_19
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-22000-8
Online ISBN: 978-3-540-24769-2
eBook Packages: Springer Book Archive