Evaluating software architectures: methods and case studies
Evaluating software architectures: methods and case studies
Scenario-Based Analysis of Software Architecture
IEEE Software
Architecture-level modifiability analysis (ALMA)
Journal of Systems and Software
Comparison of Scenario-Based Software Architecture Evaluation Methods
APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
Proceedings of the 24th ACM SIGPLAN conference on Object oriented programming systems languages and applications
Identifying program, test, and environmental changes that affect behaviour
Proceedings of the 33rd International Conference on Software Engineering
Towards architectural information in implementation (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Supervising the evolution of web service orchestrations using quality requirements
ECSA'11 Proceedings of the 5th European conference on Software architecture
Controlling software architecture erosion: A survey
Journal of Systems and Software
A tactic-centric approach for automating traceability of quality concerns
Proceedings of the 34th International Conference on Software Engineering
Hi-index | 0.00 |
Traditional scenario-based architectural analysis methods rely on manual review-based evaluation that requires advanced skills from architects and developers. They are usually applied when the architecture is under development, but before its implementation has begun. The system implementation is one additional and fundamental element that should be used and considered during the software architecture evaluation. In this paper, we propose an approach to add information, which ideally should come from traditional evaluation methods, about scenarios and quality attributes to the source code of web-based systems using metadata. The main aim is to enable the automatic architecture analysis by producing a report with information about scenarios, quality attributes and source code assets, such as: (i) the potential tradeoff points among quality attributes, (ii) the execution time for scenarios and if it has failed or not. Up to now, the approach has been applied mainly to web-based systems, but it can be adapted to other software domains. The paper also presents the tool used to perform static and dynamic analysis, and the results of its application to an e-commerce web system and an enterprise information web system.