Java Component Refactoring Based on Communication Integrity Violations | Request PDF
To mitigate software architectural erosion, new languages and development methods have been proposed to make explicit the architectural decisions in the source code for the benefit of the programmers. Component Based Soft- ware Engineering (CBSE) is a trend which claims to improve software modularis...
- Autores:
-
Arboleda Jimenez, Hugo Fernando
Royer, Jean-Claude
- Tipo de recurso:
- http://purl.org/coar/resource_type/c_c94f
- Fecha de publicación:
- 2010
- Institución:
- Universidad ICESI
- Repositorio:
- Repositorio ICESI
- Idioma:
- eng
- OAI Identifier:
- oai:repository.icesi.edu.co:10906/83086
- Acceso en línea:
- https://www.researchgate.net/publication/255907094_Java_Component_Refactoring_Based_on_Communication_Integrity_Violations
http://repository.icesi.edu.co/biblioteca_digital/handle/10906/83086
- Palabra clave:
- Arquitectura de software
Ingeniería de software
Ingeniería de sistemas y comunicaciones
Programación cliente servidor
Systems engineering
- Rights
- openAccess
- License
- https://creativecommons.org/licenses/by-nc-nd/4.0/
Summary: | To mitigate software architectural erosion, new languages and development methods have been proposed to make explicit the architectural decisions in the source code for the benefit of the programmers. Component Based Soft- ware Engineering (CBSE) is a trend which claims to improve software modularisation and to embed architectural concerns. Refactoring legacy code with components in mind needs tools to asses the compliance of the source code under analysis with component programming principles. The communication integrity property is one of the major principles to implement component based software architectures. In this paper we present a set of rules to prevent violation of the communication integrity property in legacy code and these rules are used to distinguish component types from data types. Furthermore, we provide refactoring actions in order to fix detected violations and thus to restructure Java legacy code with a pure and strict Java component model in mind. |
---|