![]() ![]() With this purpose, we introduce a novel DSVL called SLAMMER that contains generalisations of some,of the more,used types of internal product,measurements,and redesigns. In this paper we present our approach,for the visual specification of measurements,and redesigns for Domain,Specific Visual Languages (DSVLs). However, developing such helper tools for the wide variety of (frequently domain,specific) visual notations used by software engineers is a hard and repetitive task that does not take advantage from previous developments, thus being frequently forgotten. Besides, we also present a tool that can be used in a MOM to support the measurement processĪbstract Ensuring model quality is a key success factor in many computer science areas, and becomes crucial in recent software engineering paradigms,like the one proposed,by model-driven software development.,Tool support for measurements,and redesigns becomes essential to help developers improve the quality of their models. We detail the specification of two concern metrics: Concern Diffusion over Operations (CDO) and Concern Diffusion over Components (CDC). Therefore, we present our approach of how to use SMM for specifying concern metrics in a modularity-oriented modernization in the ADM context, i.e., using KDM and SMM. However, there are no studies that investigate how SMM can be used to specify concern metrics in MOMs. In a MOM, it is important to measure to what extent the concerns are spread across the system using concern metrics. A central task in any modernization process is to measure, characterizing quantitatively, the legacy and the modernized version to check if problems were solved/assuaged. ![]() ADM also delivers a metamodel called Structured Metrics Metamodel (SMM) whose goal is to standardize the specification of metrics, measurement processes, and results of the measurements. Knowledge Discovery Metamodel (KDM) is the main one, and it is used for representing all aspects of an existing system to be modernized. ![]() Architecture-driven modernization (ADM) is a model-based alternative for that-it is a kind of reengineering that employs standard metamodels along the process. An alternative is to conduct a modularity-oriented modernization (MOM), whose goal is to restructure concerns for making them more modular. We present how our proposal was applied in these projects and compare the results with those of the previously followed process.īad modularized concerns are a known deficiency of legacy systems, making their maintenance increasingly harder and expensive. Our work results from joint projects with industry partners with software modernization needs in different technologies: Oracle Forms, Java EE, and Ruby on Rails. These views display in a single canvas architectural elements whose look and feel maps software metrics. In this paper, we present a Technology-independent approach which is flexible enough to allow developers to define metric-centered architectural views by using annotations. The main disadvantages of such tools are: i) they are dependent on the language/technology on top of which the application is built and ii) they offer pre-defined views that are too difficult to adapt to meet particular software comprehension needs. The goal of many commercial and academic tools is to build software architectural views from the code. The high cost of this process is due to the effort invested on software comprehension since, in most of cases, there is no up-to-date abstraction or documentation to ease this task but the source code. Abstract The maintenance of applications is a crucial activity in the software industry. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |