Software architecture in practice
Software architecture in practice
Performing architecture tradeoff analysis
ISAW '98 Proceedings of the third international workshop on Software architecture
Experience with performing architecture tradeoff analysis
Proceedings of the 21st international conference on Software engineering
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Reviewing Product Line Architectures: Experience Report of ATAM in an Automotive Context
PFE '01 Revised Papers from the 4th International Workshop on Software Product-Family Engineering
Six years of evaluating software architectures in student projects
Journal of Systems and Software
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 |
Software architecture may go through many changes during its existence. Architecture evaluation can point out current problems, help to anticipate some of the future changes, and also show the absolute limits of a design. This paper presents experiences from eleven scenario based architecture evaluations with ATAM. The evaluations were completed on a tight two day evaluation schedule. This limited time forced to search for alternative scheduling options. The evaluated system designs had relatively long life cycle up to 30 years and all the designs were evaluated for the first time. We have learnt that in evaluations current issues often overshadow the long view of the future. We suggest that architecture evaluations should be integrated to the development process as a tool not only for today but also for tomorrow.