Identificação de características de sistemas legados a partir da análise de conteúdo da literatura
Abstract
Legacy systems tend to consume a lot of resources and so, requires to be well managed. Deciding whether a system is becoming legacy or not is a decision that involves identifying the characteristics of such a system. This paper aims to present the mapping of features found in the literature's definitions of legacy systems. For this, a systematic process of search, extraction and analysis of the definitions of legacy systems found between the years 1995, 2000, 2005, 2010 and 2015 was performed. The results analysis reveal that in the studied period, the characteristics with the highest frequency of occurrences were, to be vital to the organization, to be a obsolete technology and to have no documentation.
References
Bennett, K. (1995). Legacy systems: Coping with success. IEEE Software, 12(1):19–23.
Juric, M. B., Rozman, I., and Hericko, M. (2000). Performance comparison of corbaand RMI. Information and Software Technology, 42(13):915–933.
Kitchenham, B. (2004). Procedures for performing systematic reviews. Technicalreport, Keele University, Keele, UK, Software Engineering Group. Moraes, R.(1999). Análise de conteúdo. Revista Educação, 22(37):7–32.
Ning, J., Engberts, A. P., and Kozaczynski, W. V. (1994). Automated support for legacycode understanding. Communications of the ACM, 37(5):50–57.
O’Byrne, P. and Wu, B. (2000). Lace frameworks and technique - identifying the legacy status of an information system from the perspectives of its causes and effects. In Proceedings International Symposium on Principles of Software Evolution.
Ramsom, J., Sommerville, I., and Warren, I. (1998). A method for assessing legacy systems for evolution. Proceedings of the Second Euromicro Conference on Software Maintenance and Reengineering, 42(13):915–933.
Sommerville, I. (2011). Engenharia de Software. Pearson Brasil, 9th edition.
Umar, A. (1997). Application (re)engineering: Building Web-based Applications and Dealing with Legacies. Prentice Hall, 1th edition.
Juric, M. B., Rozman, I., and Hericko, M. (2000). Performance comparison of corbaand RMI. Information and Software Technology, 42(13):915–933.
Kitchenham, B. (2004). Procedures for performing systematic reviews. Technicalreport, Keele University, Keele, UK, Software Engineering Group. Moraes, R.(1999). Análise de conteúdo. Revista Educação, 22(37):7–32.
Ning, J., Engberts, A. P., and Kozaczynski, W. V. (1994). Automated support for legacycode understanding. Communications of the ACM, 37(5):50–57.
O’Byrne, P. and Wu, B. (2000). Lace frameworks and technique - identifying the legacy status of an information system from the perspectives of its causes and effects. In Proceedings International Symposium on Principles of Software Evolution.
Ramsom, J., Sommerville, I., and Warren, I. (1998). A method for assessing legacy systems for evolution. Proceedings of the Second Euromicro Conference on Software Maintenance and Reengineering, 42(13):915–933.
Sommerville, I. (2011). Engenharia de Software. Pearson Brasil, 9th edition.
Umar, A. (1997). Application (re)engineering: Building Web-based Applications and Dealing with Legacies. Prentice Hall, 1th edition.
Published
2017-10-18
How to Cite
MARTINS, Daniele; CHERVENSKI, Alex; BORDIN, Andréa.
Identificação de características de sistemas legados a partir da análise de conteúdo da literatura. In: REGIONAL SCHOOL OF SOFTWARE ENGINEERING (ERES), 1. , 2017, Alegrete.
Anais [...].
Porto Alegre: Sociedade Brasileira de Computação,
2017
.
p. 81-88.
