An empirically-based process for software architecture evaluation

Empirical Software Engineering

Volumn 8, Issue 1, 2003, Pages 83-108

  Lindvall, Mikael ^a   Tvedt, Roseanne Tesoriero ^b   Costa, Patricia ^a  

^a Fraunhofer USA Inc   (United States)

^b WASHINGTON COLLEGE   (United States)

Author keywords

Architectural evaluation; Empirical study; Metrics

Indexed keywords

CLIENT SERVER COMPUTER SYSTEMS; COMPUTER ARCHITECTURE; COMPUTER SOFTWARE MAINTENANCE; COMPUTER SOFTWARE REUSABILITY; COMPUTER SOFTWARE SELECTION AND EVALUATION; DATA COMMUNICATION SYSTEMS; JAVA PROGRAMMING LANGUAGE;

ARCHITECTURAL EVALUATION; SOFTWARE SYSTEMS;

SOFTWARE ENGINEERING;

EID: 0037368172     PISSN: 13823256     EISSN: None     Source Type: Journal    
DOI: 10.1023/A:1021772917036     Document Type: Article

References (25)

1. Abowd, G., Bass, L., Clements, P., Kazman, R., Northrop, L., and Zaremski, A. 1996. Recommended best industrial practice for software architecture evaluation. Software Engineering Institute, CMU/SEI-96-TR-025.
2. Antoniol, G., Fiutem, R., and Cristoforetti, L. Using metrics to identify design patterns in object-oriented software. Proceedings of the Fifth International Symposium on Software Metrics-METRICS'98, 23-34.
3. Avritzer, A., and Weyuker, E. J. 1998. Investigating metrics for architectural assessment. 5th International Symposium on Software Metrics 4-10.
4. Basili, V. R., Caldiera, G., and Rombach, D. H. 1994a. The experience factory. Encyclopedia of Software Engineering, 2 volume set, pp. 469-476.
5. Basili, V. R., Caldiera, G., and Rombach, D. H. 1994b. The goal question metric approach. Encyclopedia of Software Engineering, 2 volume set, Wiley.
6. Bengtsson, P., and Bosch, J. 1999 Architecture level prediction of software maintenance. Proceedings of 3rd Euro Micro Conference on Maintenance and Reengineering, 139-147.
7. Chidamber, S. R., and Kemerer, C. F. 1994. Towards a metrics suite for object-oriented design. Transactions on Software Engineering, 476-493.
8. de Bruijn, H., and van Vliet, H. 2001. Scenario-based generation and evaluation of software architectures. Lecture Notes in Computer Science 2186: 128-139.
9. Eick, S. G., Graves, T. L., Karr, A. F., Marron, J. S., and Mockus, A. 2001. Does code decay? Assessing the evidence from change management data. IEEE Transactions on Software Engineering 27:1-12.
10. Fiutem, R., and Antoniol, G. 1998. Identifying design-code inconsistencies in object-oriented software: a case study. Proceedings of International Conference on Software Maintenance, 94-102.
11. Gamma, E., Helm, R., Johnson, R., and Vlissides, J. 1994. Design patterns elements of reusable object-oriented software. Reading, MA: Addison Wesley.
12. Haney, F. M. 1972. Module connection analysis - A tool for scheduling software debugging activities. AFIPS Joint Computer Conference, 173-179.
13. Kazman, R., Abowd, G., Bass, L., and Clements, P. 1996. Scenario-based analysis of software architecture. IEEE Software, 47-55.
14. Lassing, N., Bengtsson, P., van Vliet, H., and Bosch, J. 2002. Experiences with ALMA: architecture-level modifiability architecture analysis. Journal of Systems and Software 61: 47-57.
15. Lehmann, M. M., and Belady, L. 1985. Program evolution. Process of Software Change. London: Academic Press.
16. Lindvall, M. 1997. An empirical study of requirements-driven impact analysis in object-oriented systems evolution. PhD thesis No. 480, Linköping Studies in Science and Technology.
17. Meyer, S., Duby, C. K., and Reiss, S. P. 1993. Constraining the structure and style of object-oriented programs. Brown University Computer Science Technical Report CS-93-12. First workshop on principles and practice of constraint programming.
18. Murphy, G., Notkin, D., and Sullivan, K. 1995. Software reflexion models: bridging the gap between source and high-level models. Proceedings of SIGSOFT'95 Third ACM SIGSOFT Symposium on the Foundations of Software Engineering, 18-28.
19. Schwanke, R. W. 1991. An intelligent tool for reengineering software modularity. Proceedings of the 13th International Conference on Software Engineering, 83-92.
20. Seaman, C., de Mendonca Neto, M. G., Basili, V. R., and Kim, Y.-M. 1999. An experience management system for a software consulting organization. 24th NASA SEL Software Engineering Workshop (SEW'24).
21. Sefika, M., Sane, A., and Campbell, R. H. 1996. Monitoring compliance of a software system with its high level design models. in 18th International Conference on Software Engineering (ICSE) 387-397. Los Alamitos, CA: IEEE Computer Society Press.
22. Shereshevsky, M., Ammari, H., Gradetsky, N., Mili, A., and Ammar, H. H. 2001. Information theoretic metrics for software architectures. International Computer Software and Applications Conference (COMPSAC 2001), IEEE Computer Society.
23. Soloway, E. 1987. I can't tell what in the code implements what in the specs. In The Second International Conference on Human-Computer Interaction, 317-328.
24. Yacoub, S. M., and Ammar, H. 2002. A methodology for architectural-level reliability risk analysis. IEEE Transactions on Software Engineering 28: 529-547.
25. Yau, S., and Collofello, J. 1980. Some stability measurements for software maintenance. IEEE Transactions on Software Engineering 6.