A Model-Driven Architecture Approach to the Efficient Identification of Services on Service-oriented Enterprise Architecture

Service-Oriented Enterprise Architecture requires the efficient development of loosely-coupled and interoperable sets of services. Existing design approaches do not always take full advantage of the value and importance of the engineering invested in existing legacy systems. This paper proposes an approach to define the key services from such legacy systems effectively. The approach focuses on identifying these services based on a Model-Driven Architecture approach supported by guidelines over a wide range of possible service types

The Public Healthcare System in the Transition Countries the Case Study of Serbia

The public healthcare system of Serbia, from the beginning of the past century, when more or less the unperceivable demolition of socialism, was faced with great problems. During the time, they became almost unsolvable due to servitude to old ideas and approaches to goals, organization and managing the state and public sector, political work and everday public and business managing. The application of ruling ideology, performed during the nineties of the last century and the restoration of capitalism expressed itself as unproductive, because everything else remained the same – methods of work, approach, values and standpoint. Its basic feature is institutional non-regulation being the consequence of unclear, foggy and manipulated transition. There are multiple reflexion to the public healtcare system. First the space for the wild privatisation of one part of the public healthcare system was open as well as for the development of irregular partnership between the public and private sector in the production of public goods and services. Second, the creation of a complex, to distribution oriented coalition was initiated that, within the framework of historical heritage, very skillfully using its political and any other influence intended to retain such a situation and stop necessary structural changes in the public healthcare system and the regular development of the private sector as well. Third, within of the framework of foggy and damped transition, arose the miracuous mixture of quasipublic, quasi-market and administrative mechanisms of regulation that nonsensenses necessity for the existence of the public healthcare system. Conseqently, Serbia needs the total reingeneering as a radical, qualitative and on inovations based methodology which, on the basis of development vision, should determine the direction of institutional changes and various reformatory operations in order to construct a radically new public healthcare system – oriented to prevention and preservation of health capacity (of the whole national population) on the basis of development of the relevant system of life and work while the medical treatmant of the mayor part of maladies, especially of those needing sofisticated and costly technologies, should be awarded to the private sector on the basis of personal participation. The key of implementation is in the new definition of the contents of paradigm “equity”. Paradigm that the public health insurance should provide the best healthcare for everybody is false and financially untenable even for much more wealtheir societies. On the other side, equity means necessity to provide the health care in the framework of public, transparent and precise minimum standards for everbody (meaning that nobody will die because he is not insured, because he has not money for cure or, simply, as often happens in Serbia, because he do not know relevant people).Public healthcare system, Unclear, foggy and manipulated transition, Institutional non-regulated environment, Total reingeenering, “Equity”

JSClassFinder: A Tool to Detect Class-like Structures in JavaScript

With the increasing usage of JavaScript in web applications, there is a great demand to write JavaScript code that is reliable and maintainable. To achieve these goals, classes can be emulated in the current JavaScript standard version. In this paper, we propose a reengineering tool to identify such class-like structures and to create an object-oriented model based on JavaScript source code. The tool has a parser that loads the AST (Abstract Syntax Tree) of a JavaScript application to model its structure. It is also integrated with the Moose platform to provide powerful visualization, e.g., UML diagram and Distribution Maps, and well-known metric values for software analysis. We also provide some examples with real JavaScript applications to evaluate the tool.Comment: VI Brazilian Conference on Software: Theory and Practice (Tools Track), p. 1-8, 201

Assessing architectural evolution: A case study

This is the post-print version of the Article. The official published can be accessed from the link below - Copyright @ 2011 SpringerThis paper proposes to use a historical perspective on generic laws, principles, and guidelines, like Lehman’s software evolution laws and Martin’s design principles, in order to achieve a multi-faceted process and structural assessment of a system’s architectural evolution. We present a simple structural model with associated historical metrics and visualizations that could form part of an architect’s dashboard. We perform such an assessment for the Eclipse SDK, as a case study of a large, complex, and long-lived system for which sustained effective architectural evolution is paramount. The twofold aim of checking generic principles on a well-know system is, on the one hand, to see whether there are certain lessons that could be learned for best practice of architectural evolution, and on the other hand to get more insights about the applicability of such principles. We find that while the Eclipse SDK does follow several of the laws and principles, there are some deviations, and we discuss areas of architectural improvement and limitations of the assessment approach

Search based software engineering: Trends, techniques and applications

© ACM, 2012. This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version is available from the link below.In the past five years there has been a dramatic increase in work on Search-Based Software Engineering (SBSE), an approach to Software Engineering (SE) in which Search-Based Optimization (SBO) algorithms are used to address problems in SE. SBSE has been applied to problems throughout the SE lifecycle, from requirements and project planning to maintenance and reengineering. The approach is attractive because it offers a suite of adaptive automated and semiautomated solutions in situations typified by large complex problem spaces with multiple competing and conflicting objectives. This article provides a review and classification of literature on SBSE. The work identifies research trends and relationships between the techniques applied and the applications to which they have been applied and highlights gaps in the literature and avenues for further research.EPSRC and E

Software Product Line Reengineering: A Case Study on the Geographic Domain

The growing adoption of software product lines (SPL) represents perhaps a paradigm shift in software development aiming at improving cost, quality, time to market, and developer productivity. While the underlying concepts are straightforward enough building a family of related products or systems by planned and careful reuse of a base of generalized software development assets the problems can be in the details, as successful product line practice involves domain understanding, technology selection, and so forth. Today, there is an important increment on reporting experiences and lessons about SPL development by capturing aspects that have been gathered during daily practice. Following this line, in this paper we start from our experiences of developing a software product line on the Marine Ecology domain highlighting our reasons for reengineering a previous SPL. Then, we explain step-bystep reengineering activities in terms of motivation, solutions, and lessons learned, which summarize strengths and limitations of the applied practices. Differently from other cases, here we take advantage of using domain standards as well as open source implementations within the geographic domain.Facultad de Informátic

Software Product Line Reengineering: A Case Study on the Geographic Domain

The growing adoption of software product lines (SPL) represents perhaps a paradigm shift in software development aiming at improving cost, quality, time to market, and developer productivity. While the underlying concepts are straightforward enough building a family of related products or systems by planned and careful reuse of a base of generalized software development assets the problems can be in the details, as successful product line practice involves domain understanding, technology selection, and so forth. Today, there is an important increment on reporting experiences and lessons about SPL development by capturing aspects that have been gathered during daily practice. Following this line, in this paper we start from our experiences of developing a software product line on the Marine Ecology domain highlighting our reasons for reengineering a previous SPL. Then, we explain step-bystep reengineering activities in terms of motivation, solutions, and lessons learned, which summarize strengths and limitations of the applied practices. Differently from other cases, here we take advantage of using domain standards as well as open source implementations within the geographic domain.Facultad de Informátic

A Retrospective View of Software Maintenance and Reengineering Research.

As a summary of past, current, and future trends in software maintenance and reengineering research, we give in this editorial a retrospective look from the past 14 years to now. We provide insight on how software maintenance has evolved and on the most important research topics presented in the series of the European Conference on Software Maintenance and Reengineering