Avoiding architectural degeneration: An evaluation process for software architecture

Proceedings - International Software Metrics Symposium

Volumn 2002-January, Issue , 2002, Pages 77-86

  Lindvall, M ^a   Tesoriero, R ^a,b   Costa, P ^a  

^a Fraunhofer Center Maryland for Experimental Software Engineering   (United States)

^b WASHINGTON COLLEGE   (United States)

Author keywords

Client server systems; Computer architecture; Ear; Electrical capacitance tomography; Identity based encryption; Java; Read only memory; Software architecture; Software systems

Indexed keywords

CLIENT SERVER COMPUTER SYSTEMS; COMPUTER SOFTWARE; ELECTRIC IMPEDANCE TOMOGRAPHY; HUMAN RESOURCE MANAGEMENT; ROM; SOFTWARE ARCHITECTURE;

CLIENT-SERVER SYSTEMS; EAR; ELECTRICAL CAPACITANCE TOMOGRAPHY; IDENTITY BASED ENCRYPTION; JAVA; SOFTWARE SYSTEMS;

COMPUTER ARCHITECTURE;

EID: 84948446291     PISSN: 15301435     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/METRIC.2002.1011327     Document Type: Conference Paper

References (16)

1. Abowd, G., Bass, L., Clements, P., Kazman, R., Northrop, L., Zaremski, A., "Recommended best industrial practice for software architecture evaluation," Software Engineering Institute, CMU/SEI-96-TR-025, 1996.
2. Avritzer, A., and Weyuker, E.J., "Investigating metrics for architectural assessment", 5th. International Symposium on Software Metrics, pp 4-10, 1998.
3. Basili, Victor R., Caldiera, Gianluigi and Rombach, Dieter H. The Experience Factory, Encyclopedia of Software Engineering - 2 Volume Set, pp 469-476, Copyright by John Wiley & Sons, Inc., 1994.
4. Basili, V. R., Caldiera, G. and Rombach, H. D., "The Goal Question Metric Paradigm", Encyclopedia of Software Engineering - 2 Volume Set, pp 528-532, Copyright by John Wiley & Sons, Inc., 1994.
5. Bengtsson, P., and Bosch, J., "Architecture Level Prediction of Software Maintenance", in Proceedings of 3rd EuroMicro Conference on Maintenance and Reengineering, 1999.
6. Chidamber, Shyam R. and Kemerer, Chris F., "Towards a Metrics Suite for Object-Oriented Design", Transactions on Software Engineering 20(6), pp: 476-493, 1994.
7. Eick, S. G., Graves, T. L., Karr, A. F., Marron, J. S., and Mockus, A., "Does Code Decay? Assessing the Evidence from Change Management Data", IEEE Transactions on Software Engineering 27(1), pp:1-12, 2001.
8. Haney, F. M., "Module Connection Analysis - A Tool for Scheduling Software Debugging Activites", AFIPS Joint Computer Conference, 173-179, 1972.
9. Gamma, E., Helm, R., Johnson, R. and Vlissides J. Design Patterns Elements of Reusable Object-Oriented Software. Addison Wesley, 1994
10. Kazman, R., Abowd, G., Bass, L., Clements, P., "Scenario-Based Analysis of Software Architecture", IEEE Software, pp: 47-55 November 1996.
11. Lehman, M. M. and Belady, L. Program evolution. Process of software change. Academic Press, 1985.
12. Lindvall, M., "An empirical study of requirements-driven impact analysis in object-oriented systems evolution," PhD thesis, 1997.
13. Murphy, G., Notkin, D., and Sullivan K., "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, pp: 18-28, 1995
14. Seaman, C. B., Mendonca, M., Basili, V., and Kim, Y-M., "An experience management system for a software consulting organization," Software Engineering Workshop, NASA/Goddard Software Engineering Laboratory, Greenbelt, MD, December 1999.
15. Soloway, E., "I can't tell what in the code implements what in the specs", The Second International Conference on Human-Computer Interaction, pp. 317-328, 1987.
16. Yau, S. and Collofello, J. S., "Some stability measurements for software maintenance", Transactions on Software Engineering, 6(6), 1980.