Integrating the common variability language with multilanguage annotations for web engineering

Web applications development involves managing a high diversity of files and resources like code, pages or style sheets, implemented in different languages. To deal with the automatic generation of custom-made configurations of web applications, industry usually adopts annotation-based approaches even though the majority of studies encourage the use of composition-based approaches to implement Software Product Lines. Recent work tries to combine both approaches to get the complementary benefits. However, technological companies are reticent to adopt new development paradigms such as feature-oriented programming or aspect-oriented programming. Moreover, it is extremely difficult, or even impossible, to apply these programming models to web applications, mainly because of their multilingual nature, since their development involves multiple types of source code (Java, Groovy, JavaScript), templates (HTML, Markdown, XML), style sheet files (CSS and its variants, such as SCSS), and other files (JSON, YML, shell scripts). We propose to use the Common Variability Language as a composition-based approach and integrate annotations to manage fine grained variability of a Software Product Line for web applications. In this paper, we (i) show that existing composition and annotation-based approaches, including some well-known combinations, are not appropriate to model and implement the variability of web applications; and (ii) present a combined approach that effectively integrates annotations into a composition-based approach for web applications. We implement our approach and show its applicability with an industrial real-world system.Universidad de Málaga. Campus de Excelencia Internacional Andalucía Tech

Combining Multiple Granularity Variability in a Software Product Line Approach for Web Engineering

[Abstract] Context: Web engineering involves managing a high diversity of artifacts implemented in different languages and with different levels of granularity. Technological companies usually implement variable artifacts of Software Product Lines (SPLs) using annotations, being reluctant to adopt hybrid, often complex, approaches combining composition and annotations despite their benefits. Objective: This paper proposes a combined approach to support fine and coarse-grained variability for web artifacts. The proposal allows web developers to continue using annotations to handle fine-grained variability for those artifacts whose variability is very difficult to implement with a composition-based approach, but obtaining the advantages of the composition-based approach for the coarse-grained variable artifacts. Methods: A combined approach based on feature modeling that integrates annotations into a generic composition-based approach. We propose the definition of compositional and annotative variation points with custom-defined semantics, which is resolved by a scaffolding-based derivation engine. The approach is evaluated on a real-world web-based SPL by applying a set of variability metrics, as well as discussing its quality criteria in comparison with annotations, compositional, and combined existing approaches. Results: Our approach effectively handles both fine and coarse-grained variability. The mapping between the feature model and the web artifacts promotes the traceability of the features and the uniformity of the variation points regardless of the granularity of the web artifacts. Conclusions: Using well-known techniques of SPLs from an architectural point of view, such as feature modeling, can improve the design and maintenance of variable web artifacts without the need of introducing complex approaches for implementing the underlying variability.The work of the authors from the Universidad de Málaga is supported by the projects Magic P12-TIC1814 (post-doctoral research grant), MEDEA RTI2018-099213-B-I00 (co-financed by FEDER funds), Rhea P18-FR-1081 (MCI/AEI/FEDER, UE), LEIA UMA18-FEDERIA-157, TASOVA MCIU-AEI TIN2017-90644-REDT and, European Union’s H2020 research and innovation program under grant agreement DAEMON 101017109. The work of the authors from the Universidade da Coruña has been funded by MCIN/AEI/10.13039/501100011033, NextGenerationEU/PRTR, FLATCITY-POC: PDC2021-121239-C31 ; MCIN/AEI/10.13039/501100011033 EXTRACompact: PID2020-114635RB-I00 ; GAIN/Xunta de Galicia/ERDF CEDCOVID: COV20/00604 ; Xunta de Galicia/FEDER-UE GRC: ED431C 2021/53 ; MICIU/FEDER-UE BIZDEVOPSGLOBAL: RTI-2018-098309-B-C32 ; MCIN/AEI/10.13039/501100011033 MAGIST: PID2019-105221RB-C41Junta de Andalucía; P12-TIC-1814Universidad de Málaga; UMA18-FEDERIA-157Xunta de Galicia; COV20/00604Xunta de Galicia; ED431C 2021/53Junta de Andalucía; P18-FR-108

Intranet of the future: functional study, comparison of products and practical implementation

Future intranet: functional study, comparison of products and practical implementation 1. Introduction The project has fulfilled three goals: 1) To perform a study of the functionalities which have to be covered in a modern intranet (web 2.0, unified communication, collaboration, etc) 2) To perform a comparison of tools of the market which can be used to implement intranets (commercial and open source products) 3) To test three of these tools (Oracle WebCenter, Liferay Portal and Microsoft SharePoint) and develop a prototype with Oracle WebCenter. In addition, it includes a research about the evolution of the Intranets among the time, as well as a work to discover the current state of this kind of platforms over the entire world. In this introductory research it is also convenient to include other topics which are not strictly technical involving the use of this Intranet. To be more concrete, there is an analysis of the importance of the human role and management of the Intranet, the process of deploying a new Intranet in an organization and methods to evaluate the performance of this new system.   2. Functional study The approach taken to fulfil this goal is to develop a theoretical model describing the relationship between the Intranet and its users, and a complete set of functionalities which could be covered in the Intranet of the future. These functionalities are categorized in groups. The project describes these groups and the functionalities included on them. 3. Comparison of products The project will describe and compare several technologies which can be used to develop an Intranet that we have previously modelled. The purpose here is to discover the strong points and weaknesses of each technology if it was used to develop the Intranet we desire. After having done such a review, the project focuses on three technologies and performs an extensive evaluation of them. Finally, an extensive comparison between these three technologies is done, highlighting where they offer better solutions and performance compared to the other possibilities. 4. Practical implementation The project focuses on three technologies: Oracle WebCenter, Liferay Portal and Microsoft SharePoint. Then, a prototype which covers a set of functionalities of the modelled Intranet has been built with Oracle WebCenter

Lightweight Multilingual Software Analysis

Developer preferences, language capabilities and the persistence of older languages contribute to the trend that large software codebases are often multilingual, that is, written in more than one computer language. While developers can leverage monolingual software development tools to build software components, companies are faced with the problem of managing the resultant large, multilingual codebases to address issues with security, efficiency, and quality metrics. The key challenge is to address the opaque nature of the language interoperability interface: one language calling procedures in a second (which may call a third, or even back to the first), resulting in a potentially tangled, inefficient and insecure codebase. An architecture is proposed for lightweight static analysis of large multilingual codebases: the MLSA architecture. Its modular and table-oriented structure addresses the open-ended nature of multiple languages and language interoperability APIs. We focus here as an application on the construction of call-graphs that capture both inter-language and intra-language calls. The algorithms for extracting multilingual call-graphs from codebases are presented, and several examples of multilingual software engineering analysis are discussed. The state of the implementation and testing of MLSA is presented, and the implications for future work are discussed.Comment: 15 page

Contributions of architecture Dew Computing to the Internet of Things: comparisons between pilot implementations of both architectures

Dew computing ó la computación de rocío o lágrima ha despertado gran interés en la academia, debido a la separación de los procesos de computación distribuida; donde se encuentran las capas de cloud Computing (computación en la nube), Fog Computing (computación de niebla), Edge Computing (computación de borde) y por último Dew Computing. Estas capas están mencionadas de orden descendente (de mayor a menor) siendo Dew Computing la más cercana al usuario final. Esto se realiza para una mayor comprensión entre las tecnologías y procesos que en ellas se realizan permitiendo su diferenciación. La arquitectura de Internet of Things (IoT) es un paradigma tecnológico que se está formando dentro del ecosistema de computación distribuida, por ende, se requiere resaltar la capa de Dew Computing y su aporte al modelo tecnológico. Es por esto, que se realiza un estado del arte de las arquitecturas Dew Computing e IoT que permitan su comparación con el fin de saber su aporte de forma independiente y en dado caso, cómo podrían integrarse. Se realiza una prueba piloto entre las arquitecturas y una integración de las misma para encontrar los aportes que un modelo del entrega al otro y por último, se plantean posibles escenarios de aplicación que evidencien los beneficios y déficit de la implementación de cada arquitectura en diferentes ámbitos sociales.INTRODUCCIÓN 1. PROBLEMA, PREGUNTA E HIPÓTESIS DE INVESTIGACIÓN 11 2. JUSTIFICACIÓN 11 3. OBJETIVOS DEL PROYECTO 13 3.1 OBJETIVO GENERAL 13 3.2 OBJETIVOS ESPECÍFICOS 13 4. MARCO REFERENCIAL 14 4.1 MARCO CONCEPTUAL 14 4.1.1 Internet of Things 15 4.1.2 Cloud Computing 15 4.1.3 Fog Computing 16 4.1.4 Edge Computing 17 4.1.5 Dew Computing 20 4.2 MARCO TEÓRICO 21 4.3 ESTADO DEL ARTE 22 4.3.1 Revisión sistemática de la literatura 22 4.3.2 Análisis estado del arte 28 4.4 MARCO CONTEXTUAL Y ANTECEDENTES 28 4.5 NORMAS Y ESTÁNDARES 29 4.5.1 Normatividad colombiana 29 4.5.2 Estándares y documentos de referencia 30 4.6 EMPRESAS TECNOLÓGICAS 31 4.6.1 Microsoft Azure IoT Edge 31 4.6.2 Amazon IoT GreenGrass 32 5. DESCRIPCIÓN DEL PROCESO INVESTIGATIVO 34 5.1 ENFOQUE Y TIPO DE INVESTIGACIÓN 34 5.2 FASES Y ACTIVIDADES 34 5.2.1 Elaboración del estado del arte de Dew computing 35 5.2.2 Análisis comparativo entre frameworks para Dew Computing 35 5.2.3 Dispositivo para pruebas 36 5.2.4 Pruebas de ambas arquitecturas 40 5.2.5 Análisis de pruebas 45 6. RESULTADOS 48 6.1 REVISIÓN COMPARATIVA DE DEW COMPUTING E IOT 48 6.2 VENTAJAS Y DESVENTAJAS DE DEW COMPUTING CON IOT. 52 6.2.1 Física 53 6.2.2 Economía 54 6.2.3 Ubicación 54 6.3 OPORTUNIDADES QUE BRINDA DEW COMPUTING 55 6.3.1 Manejo de la energía 55 6.3.2 Procesamiento 55 6.3.3 Almacenamiento 55 6.3.4 Protocolos de comunicación 55 6.3.5 Lenguajes de programación 55 6.3.6 Seguridad de los datos 56 6.3.7 Visualización de los datos 56 7. CONCLUSIONES Y RECOMENDACIONES 57 8. REFERENCIAS 58MaestríaDew Computing or the dew or tear computation has aroused considerable interest in the academy, due to the separation of the processes of distributed computing; where are the layers of Cloud Computing (cloud computing), Fog Computing (fog computing), Edge Computing (edge computing) and finally Dew Computing. These layers are mentioned in descending order (from highest to lowest) with Dew Computing being the closest to the end user. This is done for a better understanding of the technologies and processes that are carried out in them, allowing their differentiation

Intranet of the future: functional study, comparison of products and practical implementation

Future intranet: functional study, comparison of products and practical implementation 1. Introduction The project has fulfilled three goals: 1) To perform a study of the functionalities which have to be covered in a modern intranet (web 2.0, unified communication, collaboration, etc) 2) To perform a comparison of tools of the market which can be used to implement intranets (commercial and open source products) 3) To test three of these tools (Oracle WebCenter, Liferay Portal and Microsoft SharePoint) and develop a prototype with Oracle WebCenter. In addition, it includes a research about the evolution of the Intranets among the time, as well as a work to discover the current state of this kind of platforms over the entire world. In this introductory research it is also convenient to include other topics which are not strictly technical involving the use of this Intranet. To be more concrete, there is an analysis of the importance of the human role and management of the Intranet, the process of deploying a new Intranet in an organization and methods to evaluate the performance of this new system.   2. Functional study The approach taken to fulfil this goal is to develop a theoretical model describing the relationship between the Intranet and its users, and a complete set of functionalities which could be covered in the Intranet of the future. These functionalities are categorized in groups. The project describes these groups and the functionalities included on them. 3. Comparison of products The project will describe and compare several technologies which can be used to develop an Intranet that we have previously modelled. The purpose here is to discover the strong points and weaknesses of each technology if it was used to develop the Intranet we desire. After having done such a review, the project focuses on three technologies and performs an extensive evaluation of them. Finally, an extensive comparison between these three technologies is done, highlighting where they offer better solutions and performance compared to the other possibilities. 4. Practical implementation The project focuses on three technologies: Oracle WebCenter, Liferay Portal and Microsoft SharePoint. Then, a prototype which covers a set of functionalities of the modelled Intranet has been built with Oracle WebCenter

Software solutions for web information systems in digital humanities: review, analysis and comparative study

Research in the humanities increasingly depends on how information is structured and managed and how, on the basis of that information, new knowledge is produced. Additionally, participatory approaches, which often rely on web information systems as their supportive infrastructure, have made an impact on the most recent historiographical trends, in particular in the methodological framework of digital humanities. The aim of this paper was to produce, from an operational and implementation perspective, a review of software solutions frequently used to develop web information systems for research projects in humanities and cultural heritage, in order to provide an understanding of the various possibilities available and their positives and limitations, also based on different users’ requirements. An individual and comparative analysis of sixteen different application frameworks commonly used in these fields, either generic or developed for a specific research domain, has been carried out, considering their main functionalities, strengths, and weaknesses. The achieved results facilitate critical and reasoned decision-making among several available options, guiding the makers of those systems, both researcher(s) and developers(s), and providing them also with a common ground of terms and use cases to facilitate their necessary dialogue

Mobile e-commerce: study and model generation, implementation issues and analysis

Not availabl

The case of Ferbritas Cadastre Information System

The processes of mobilization of land for infrastructures of public and private domain are developed according to proper legal frameworks and systematically confronted with the impoverished national situation as regards the cadastral identification and regularization, which leads to big inefficiencies, sometimes with very negative impact to the overall effectiveness. This project report describes Ferbritas Cadastre Information System (FBSIC) project and tools, which in conjunction with other applications, allow managing the entire life-cycle of Land Acquisition and Cadastre, including support to field activities with the integration of information collected in the field, the development of multi-criteria analysis information, monitoring all information in the exploration stage, and the automated generation of outputs. The benefits are evident at the level of operational efficiency, including tools that enable process integration and standardization of procedures, facilitate analysis and quality control and maximize performance in the acquisition, maintenance and management of registration information and expropriation (expropriation projects). Therefore, the implemented system achieves levels of robustness, comprehensiveness, openness, scalability and reliability suitable for a structural platform. The resultant solution, FBSIC, is a fit-for-purpose cadastre information system rooted in the field of railway infrastructures. FBSIC integrating nature of allows: to accomplish present needs and scale to meet future services; to collect, maintain, manage and share all information in one common platform, and transform it into knowledge; to relate with other platforms; to increase accuracy and productivity of business processes related with land property management