Facilitating the Selection of Architectural Patterns by Means of a Marked Requirements Model
Architecture definition requires architects who are highly qualified in both the use of architectural patterns and the analysis of the application’s requirements. This is because they have to identify what patterns satisfy the application’s functional requirements (FR) and quality attributes (QA), and the interrelationships between them. However, since QAs and FRs are usually addressed separately, their interrelationships are not detailed in full. This situation means that the architect has to expend considerable effort on their identification, with the risk of misinterpretations that lead to an inappropriate choice of patterns. We here present a model that allows the FRs to be marked with the constraints imposed by the QAs. The marks are conceived to be re-used during the architecture definition. The model brings knowledge of the requirements and their relationships closer to the architect, allowing patterns aligned with the requirements to be identified with less effort.
KeywordsRequirements Engineering Quality Attributes Software Architecture
Unable to display preview. Download preview PDF.
- 2.Bengtsson, P.: Towards Maintainability Metrics on Software Architecture: An Adaptation of Object-Oriented Metrics. In: 1st Nordic Workshop on Software Architecture (1998)Google Scholar
- 3.Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley, Boston (2003)Google Scholar
- 4.Avgeriou, P., Zdun, U.: Architectural Patterns Revisited - A Pattern Language. In: 10th European Conference on Pattern Languages of Programs, Germany, pp. 1–39 (2005)Google Scholar
- 5.Clements, P., Kazman, R., Klein, M.: Evaluating Software Architectures: Methods and Case Studies. Addison-Wesley, Boston (2002)Google Scholar
- 9.Bosch, J.: Design and use of software architectures adopting and evolving a product-line approach. Addison-Wesley, Boston (2000)Google Scholar
- 11.Wojcik, R., Bachmann, F., Bass, L., Clements, P., Merson, P., Nord, R., Wood, B.: Attribute-Driven Design (ADD), Version 2.0. Technical Report, Software Engineering Institute, CMU/SEI-2006-TR-023 (2006)Google Scholar
- 12.Bachmann, F., Bass, L., Klein, M.: Moving from quality attribute requirements to architectural decisions. In: 2nd International Software Requirements to Architectures Workshop, Portland, Oregon, USA (2003)Google Scholar
- 14.Czarnecki, K., Eisenecker, U.: Generative Programming: Methods, Tools, and Applications. Addison-Wesley, Boston (2000)Google Scholar
- 15.Doerr, J., Kerkow, D., Koenig, T., Olsson, T., Suzuki, T.: Non-Functional Requirements in Industry - Three Case Studies Adopting an Experience-based NFR Method. In: 13th IEEE Int. Conference on Requirements Engineering, pp. 373–384 (2005)Google Scholar
- 16.Xu, L., Ziv, H., Richardson, D., Liu, Z.: Towards Modeling Non-Functional Requirements in Software Architecture. In: Workshop on Early-Aspect (2005)Google Scholar
- 17.Buschmann, F., Henney, k., Schmidt, D.C.: Pattern-Oriented Software Architecture: On Patterns and Pattern Languages. John Wiley & Sons, England (2007)Google Scholar
- 18.Meszaros, G., Doble, J.: A Pattern Language for Pattern Writing. In: Pattern Languages of Program Design, vol. 3, pp. 529–574. Addison-Wesley, Boston (1998)Google Scholar