Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
ICSE '94 Proceedings of the 16th international conference on Software engineering
Software architecture in practice
Software architecture in practice
Experience with performing architecture tradeoff analysis
Proceedings of the 21st international conference on Software engineering
The unified software development process
The unified software development process
Applied software architecture
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
Quantifying the costs and benefits of architectural decisions
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Tracking degradation in software product lines through measurement of design rule violations
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
A Cost-Value Approach for Prioritizing Requirements
IEEE Software
The Importance of Quality Requirements in Software Platform Development - A Survey
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 9 - Volume 9
Consensus Building when Comparing Software Architectures
PROFES '02 Proceedings of the 4th International Conference on Product Focused Software Process Improvement
Empirical Software Engineering
Characterizing software architecture changes: A systematic review
Information and Software Technology
| Hi-index | 0.00 |
To sustain the qualities of a software system during evolution, and to adapt the quality attributes as the requirements evolve, it is necessary to have a clear software architecture that is understood by all developers and to which all changes to the system adheres. This software architecture can be created beforehand, but must also be updated as the domain of the software, and hence the requirements on the software system evolves. Creating an architectural structure for a system or part of a system so that the architecture fulfils the desired quality requirements is often hard. In this paper we propose a decision support method to aid in the understanding of different architecture structure candidates for a software system. We propose a method that is adaptable with respect to both the set of potential architecture structures, and quality attributes relevant for the system's domain to help in this task. The method creates a support framework, using a multi-criteria decision method, supporting comparison of different software architecture structures for a specific software quality attribute and vice versa. Moreover, given a prioritization of quality attributes for the software system, or part thereof, the most suitable software architecture structure can be indicated using the created framework.