SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
Quantifying the costs and benefits of architectural decisions
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Evaluating software architectures: methods and case studies
Evaluating software architectures: methods and case studies
A survey on software architecture analysis methods
IEEE Transactions on Software Engineering
Software Architecture in Practice
Software Architecture in Practice
Comparison of Scenario-Based Software Architecture Evaluation Methods
APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
Scrum and CMMI Level 5: The Magic Potion for Code Warriors
AGILE '07 Proceedings of the AGILE 2007
Empirical Software Engineering
Mature Agile with a Twist of CMMI
AGILE '08 Proceedings of the Agile 2008
SA@Work A Field Study of Software Architecture and Software Quality at Work
APSEC '08 Proceedings of the 2008 15th Asia-Pacific Software Engineering Conference
An Empirical Study of Software Architects' Concerns
APSEC '09 Proceedings of the 2009 16th Asia-Pacific Software Engineering Conference
Scaling up software architecture evaluation processes
ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
Applying the ATAM to an architecture for decentralized control of a transportation system
QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures
Hi-index | 0.00 |
In this paper, we present a novel technique for assessing and prioritizing architectural quality in large-scale software development projects. The technique can be applied with relatively little effort by software architects and thus suited for agile development in which quality attributes can be assessed and prioritized, e.g., within each development sprint. We outline the processes and metrics embodied in the technique, and report initial experiences on the benefits and liabilities. In conclusion, the technique is considered valuable and a viable tool, and has benefits in an architectural, technical, context, as well as in a business and people context.