A pattern language for pattern writing
Pattern languages of program design 3
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Generative programming: methods, tools, and applications
Generative programming: methods, tools, and applications
Evaluating software architectures: methods and case studies
Evaluating software architectures: methods and case studies
Software Architecture in Practice
Software Architecture in Practice
Non-Functional Requirements in Industry - Three Case Studies Adopting an Experience-based NFR Method
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Pattern Oriented Software Architecture: On Patterns and Pattern Languages (Wiley Software Patterns Series)
"The Golden Age of Software Architecture" Revisited
IEEE Software
Quality-driven architecture development using architectural tactics
Journal of Systems and Software
Architectural variability management in multi-layer web applications through feature models
FOSD '12 Proceedings of the 4th International Workshop on Feature-Oriented Software Development
| Hi-index | 0.00 |
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.