COORDINSPECTOR: a tool for extracting coordination data from legacy code

More and more current software systems rely on non trivial coordination logic for combining autonomous services typically running on different platforms and often owned by different organizations. Often, however, coordination data is deeply entangled in the code and, therefore, difficult to isolate and analyse separately. COORDINSPECTOR is a software tool which combines slicing and program analysis techniques to isolate all coordination elements from the source code of an existing application. Such a reverse engineering process provides a clear view of the actually invoked services as well as of the orchestration patterns which bind them together. The tool analyses Common Intermediate Language (CIL) code, the native language of Microsoft .Net Framework. Therefore, the scope of application of COORDINSPECTOR is quite large: potentially any piece of code developed in any of the programming languages which compiles to the .Net Framework. The tool generates graphical representations of the coordination layer together and identifies the underlying business process orchestrations, rendering them as Orc specifications

Discovering coordination patterns

A large and growing amount of software systems rely on non-trivial coordination logic for making use of third party services or components. Therefore, it is of outmost importance to understand and capture rigorously this continuously growing layer of coordination as this will make easier not only the veri cation of such systems with respect to their original speci cations, but also maintenance, further development, testing, deployment and integration. This paper introduces a method based on several program analysis techniques (namely, dependence graphs, program slicing, and graph pattern analysis) to extract coordination logic from legacy systems source code. This process is driven by a series of pre-de ned coordination patterns and captured by a special purpose graph structure from which coordination speci cations can be generated in a number of di erent formalisms

Slicing for architectural analysis

Current software development often relies on non-trivial coordination logic for combining autonomous services, eventually running on different platforms. As a rule, however, such a coordination layer is strongly woven within the application at source code level. Therefore, its precise identification becomes a major methodological (and technical) problem and a challenge to any program understanding or refactoring process. The approach introduced in this paper resorts to slicing techniques to extract coordination data from source code. Such data are captured in a specific dependency graph structure from which a coordination model can be recovered either in the form of an Orc specification or as a collection of code fragments corresponding to the identification of typical coordination patterns in the system. Tool support is also discussed

Extracting and verifying coordination models from source code

Current software development relies increasingly on non-trivial coordination logic for com- bining autonomous services often running on di erent platforms. As a rule, however, in typical non-trivial software systems, such a coordination layer is strongly weaved within the application at source code level. Therefore, its precise identi cation becomes a major methodological (and technical) problem which cannot be overestimated along any program understanding or refactoring process. Open access to source code, as granted in OSS certi cation, provides an opportunity for the devel- opment of methods and technologies to extract, from source code, the relevant coordination information. This paper is a step in this direction, combining a number of program analysis techniques to automatically recover coordination information from legacy code. Such information is then expressed as a model in Orc, a general purpose orchestration language

Anotação sintética, numa perspectiva de Direito Público, ao Acórdão n.º 63/2006, em Plenário, do Tribunal Constitucional (português), de 24 de Janeiro de 2006 - qual proibição constitucional de impostos retroactivos? A tese de Oliveira Salazar.

The present article aims to analyze the Judgment no. º 63/2006 of the Constitutional Court, of January 24, 2006, verifying the characteristics of the case, under reference abstract and concrete, of the constitutional principle of the prohibition of retroactive tax. It also examines the core aspects of the temporal validity of the legal and tax rules, brevitatis causa of legal and fiscal standards. Thus, it scrutinizes the call application of tax rules (and / or tax) within the application in time, consisting brief notes on the legal tradition-Lusitanian, from the standpoint of doctrine, from 1976 to 1985 including, recalling the Thesis Salazar on non-retroactivity of tax law. § O presente artigo pretende analisar o Acórdão do Tribunal Constitucional n.º 63/2006, de 24 de Janeiro de 2006, verificando de forma sintética as características do caso concreto, sob referência abstracta e concreta, do princípio constitucional da proibição de imposto retroativos, analisando ainda os aspectos nucleares da eficácia temporal das normas jurídico-tributárias, brevitatis causa, das normas jurídico-fiscais. Para tanto, se averigua a chamada aplicação das normas fiscais (e/ou tributárias) no seio da aplicação no tempo, constando breves notas sobre a tradição jurídico-lusitana, do ponto de vista da doutrina, a partir de 1976, designadamente até 1985, recordando a Tese de Salzar sobre a não retroatividade da lei fiscal.