A Case Study of Distributed and Evolving Applications Using Separation of Concerns

Keywords: Distributed applications, separation of concerns. Abstract: Researchers and practitioners have noted that the most difficult task is not development software in the first place but rather changing it afterwards because the software’s requirements change, the software needs to execute more efficiently, etc. For instance, changing the architecture of an application from a stand-alone application, to a distributed one is still an issue. Generally speaking, we should encapsulate distribution logic in components through the borders of aspects oriented techniques (separation of concerns) in which we define an aspect as a software artefact that addresses a concern. Although, theses aspects can be offered by the same object that changes its behaviour during lifetime. We investigate through a case study the following ideas. Firstly, what we need like modifications to transform local application to distributed one, using a number of target platforms (RMI, EJBs, etc.)? Secondly, we analyze aspects oriented development techniques to detect what is the best technique that corresponds for changes requested to integrate a new requirements such as distribution.