3 research outputs found
An Architecture to infer Business Rules from Event Condition Action Rules implemented in the Persistence Layer
The business rules that govern the behaviour of a business process can be hardcoded in different ways in a
software application. The modernization or improvement of these applications to a process-oriented
perspective implies typically the modification of the business rules. Frequently, legacy systems are not
well-documented, and almost always, the documentation they have is not updated. As a consequence
many times is necessary the analysis of source code and databases structures to be transformed into a
business language more understandable by the business experts involved in the modernization process.
Database triggers are one of the artefacts in which business rules are hardcoded. We focus on this kind of
artefacts, having in mind to avoid the manual analysis of the triggers by a database expert, and bringing it
closer to business experts. To get this aim we need to discover business rules that are hardcoded in
triggers, and translate it into vocabularies that are commonly used by business experts. In this paper we
propose an ADM-based architecture to discover business rules and rewrite then into a language that can
be understood by the business experts.Ministerio de Ciencia y Tecnolog铆a TIN2009-13714Ministerio de Ciencia y Tecnolog铆a TIN2010-20057-C03-02Ministerio de Ciencia y Tecnolog铆a TIN2010-21744-C02-
Recommended from our members
Optimizing scoped and immortal memory management in real-time java
This thesis was submitted for the degree of Doctor of Philosophy and awarded by Brunel University.The Real-Time Specification for Java (RTSJ) introduces a new memory management model which avoids interfering with the garbage collection process and achieves better deterministic behaviour. In addition to the heap memory, two types of memory areas are provided - immortal and scoped. The research presented in this Thesis aims to optimize the use of the scoped and immortal memory model in RTSJ applications. Firstly, it provides an empirical study of the impact of scoped memory on execution time and memory consumption with different data objects allocated in scoped memory areas. It highlights different characteristics for the scoped memory model related to one of the RTSJ implementations (SUN RTS 2.2). Secondly, a new RTSJ case study which integrates scoped and immortal memory techniques to apply different memory models is presented. A simulation tool for a real-time Java application is developed which is the first in the literature that shows scoped memory and immortal memory consumption of an RTSJ application over a period of time. The simulation tool helps developers to choose the most appropriate scoped memory model by monitoring memory consumption and application execution time. The simulation demonstrates that a developer is able to compare and choose the most appropriate scoped memory design model that achieves the least memory footprint. Results showed that the memory design model with a higher number of scopes achieved the least memory footprint. However, the number of scopes per se does not always indicate a satisfactory memory footprint; choosing the right objects/threads to be allocated into scopes is an important factor to be considered. Recommendations and guidelines for developing RTSJ applications which use a scoped memory model are also provided. Finally, monitoring scoped and immortal memory at runtime may help in catching possible memory leaks. The case study with the simulation tool developed showed a space overhead incurred by immortal memory. In this research, dynamic code slicing is also employed as a debugging technique to explore constant increases in immortal memory. Two programming design patterns are presented for decreasing immortal memory overheads generated by specific data structures. Experimental results showed a significant decrease in immortal memory consumption at runtime
Una propuesta basada en el paradigma dirigido por modelos para la extracci贸n de procesos del software desde sistemas heredados utilizando la perspectiva temporal
Falta palabras claveBusiness Process Management (BPM) es un factor estrat茅gico en el sector de las tecnolog铆as de la informaci贸n (TI), as铆 como en otros sectores productivos. Las TI utilizan sistemas heredados (legacy systems) para gestionar su negocio, donde sus bases de datos (legacy databases) almacenan estados hist贸ricos de la ejecuci贸n de todo tipo de procesos, raz贸n por la cual pueden considerarse como una fuente para extraer perspectivas o dimensiones de estos procesos: i) el tiempo, ii) los recursos, iii) la informaci贸n y iv) los casos.
Algunos est谩ndares para representar procesos del software como UML AD, BPMN, SPEM e Iso/Iec 24744 est谩n sustentados por robustos Meta-modelos. El paradigma Model Driven Engineering (MDE) es cada vez m谩s aceptado al ofrecer modelos y Meta-modelos de diversos niveles de abstracci贸n as铆 como mecanismos para realizar transformaciones entre ellos. MDE puede emplearse para tanto para extraer modelos mediante ingenier铆a inversa como para generar modelos desde una especificaci贸n de alto nivel.
Esta tesis define una propuesta general basada en MDE para hacer ingenier铆a inversa de legacy databases extrayendo la perspectiva temporal de procesos de TI. Se ha analizado la definici贸n de dimensiones BPM sobre distintas categor铆as de legacy systems de uso frecuente en TI, concluyendo que casi toda TI organiza su actividad bajo proyectos que tiene que planificar y controlar. Un estudio sistem谩tico de la literatura realizado sobre la especificaci贸n de la dimensi贸n temporal de los procesos nos ha llevado a aportar una taxonom铆a de reglas que cubre la tipolog铆a que aparecen en las TI y tambi茅n en otros sectores. Esta taxonom铆a nos ha permitido evaluar carencias de lenguajes de procesos de uso frecuentemente en TI y proponer Meta-modelos UML y OCL que permiten formalizar dichas reglas para resolver estas debilidades, adem谩s de facilitar la extracci贸n de procesos desde legacy databases. MS Project (como legacy system) y BPMN (como est谩ndar de modelaci贸n e intercambio de procesos serializados) son usados frecuentemente en el sector TI, raz贸n por la que consideramos estos sistemas como piloto de la soluci贸n. La arquitectura general se especializa con este caso piloto, definiendo: i) un Meta-modelo de tareas para MS Project, ii) la extensi贸n del Meta-modelo de BPMN con la dimensi贸n temporal y iii) transformaciones MDE que extraen autom谩ticamente procesos BPMN desde proyectos definidos en MS Project.
La soluci贸n se ha contrastado en el proyecto de transferencia tecnol贸gica AQUA-WS entre el grupo PAIDI TIC021 IWT2 y EMASESA, verificando la utilidad de los resultados obtenidos, que podr铆an extrapolarse a otros casos y sectores productivos. Por otro lado, como trabajo futuro, se podr铆a: i) incorporar otras perspectivas BPM como: recursos y casos; ii) generar log de eventos para utilizarse en el campo de la miner铆a de procesos