Leticia Montalvillo

Leticia Montalvillo

Auto-generated profile, based on publicly available information

Leticia Montalvillo

Ikerlan Technology Research Centre

Research Focus & Metrics

Academic Career Length

16Years (2011-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
23 November 2022 in IEEE Access
Verified
Journal Article
Open access
DSDenis Stefanescu
Denis Stefanescu
LMLeticia Montalvillo
Leticia Montalvillo
PGPatxi Galan-Garcia
Patxi Galan-Garcia
Juan José UnzillaJuan José Unzilla
Juan José Unzilla
AUAitor Urbieta
Aitor Urbieta
The Internet of Things (IoT) has become an essential part of our society. IoT devices are used in our houses, hospitals, cars, industry, etc., making our lives easier. Nonetheless, there are a number of serious concerns about security, privacy and performance issues in IoT. It has been proven that the aforementioned issues are strictly related to the high degree of centralisation of current IoT architecture. Thus, there is an increasing interest in adopting blockchain in IoT. However, blockchain adoption is not straightforward due to the power, storage and computational limitations of IoT. Consequently, the concept of lightweight blockchain is getting more and more attention from researchers and engineers. In this paper, we conduct a systematic literature review on the lightweight blockchain concept for IoT following the PRISMA methodology. We systematically analyse “lightweight blockchain for IoT” proposals in order to better understand the limitations of blockchain for IoT, the characteristics of the current work on this topic and further research opportunities. Specifically, we analyse the definition of lightweight blockchain that other authors give, the characteristics of the reviewed proposals, their “lightweight” aspects and their evaluation. Finally, we discuss the results of the review along with further research opportunities. Consequently, this work is mostly focused on understanding the technical and performance-related aspects of blockchain for IoT as a prelude to more specific analysis such as security (i.e., attacks, vulnerabilities, etc.).

1 December 2016 in Journal of Systems and Software
Verified
Journal Article
Closed access
LMLeticia Montalvillo
Leticia Montalvillo
ODOscar Díaz
Oscar Díaz

20 July 2015
Verified
Conference Paper
Open access
LMLeticia Montalvillo
Leticia Montalvillo
ODOscar Díaz
Oscar Díaz
SPLs distinguish between domain engineering (DE) and application engineering (AE). Though each realm has its own lifecycle, they might need to be regularly synchronized to avoid SPL erosion during evolution. This introduces two sync paths: update propagation (from DE to AE) and feedback propagation (from AE to DE). This work looks at how to support sync paths in Version Control Systems (VCSs) using traditional VCS constructs (i.e. merge, branch, fork and pull). In this way, synchronization mismatches can be resolved à la VCS, i.e. highlighting difference between distinct versions of the same artifact. However, this results in a conceptual gap between how propagations are conceived (i.e. update, feedback) and how propagation are realized (i.e. merge, branch, etc). To close this gap, we propose to enhance existing VCSs with SPL sync paths as first-class operations. As a proof-of-concept, we use Web Augmentation techniques to extend GitHub's Web pages with this extra functionality. Through a single click, product engineers can now (1) generate product repositories, (2) update propagating newer feature versions, or (3), feedback propagating product customizations amenable to be upgraded as core assets.

1 August 2011
Verified
Conference Paper
Closed access
RLRoberto E. Lopez-Herrejon
Roberto E. Lopez-Herrejon
LMLeticia Montalvillo-Mendizabal
Leticia Montalvillo-Mendizabal
AEAlexander Egyed
Alexander Egyed
More and more frequently successful software systems need to evolve into families of systems, known as Software Product Lines (SPLs), to be able to cater to the different functionality requirements demanded by different customers while at the same time aiming to exploit as much common functionality as possible. As a first step, this evolution demands a clear understanding of how the functional requirements map into the features of the original system. Using this knowledge, features can be refactored so that they are reused for building the new systems of the evolved SPL. In this paper we present our experience in refactoring features based on the requirements specifications of a small and a medium size systems. Our work identified eight refactoring patterns that describe how to extract the elements of features which were subsequently implemented using Feature Oriented Software Development (FOSD) a novel modularization paradigm whose driving goal is to effectively modularize features for the development of variable systems. We argue that the identification of refactoring patterns are a stepping stone towards automating Feature-Oriented Refactoring, and present some open issues that should be addressed to that avail.

17 September 2025 in Computer Science Review
Verified
Journal Article
Open access
AKAnhelina Kovach
Anhelina Kovach
LMLeticia Montalvillo
Leticia Montalvillo
JLJorge Lanza
Jorge Lanza
PSPablo Sotres
Pablo Sotres
AUAitor Urbieta
Aitor Urbieta

18 March 2022 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
ODOscar Díaz
Oscar Díaz
LMLeticia Montalvillo
Leticia Montalvillo
RMRaul Medeiros
Raul Medeiros
MAMaider Azanza
Maider Azanza
TFThomas Fogdal
Thomas Fogdal
Software Product Lines (SPLs) aim at systematically reusing software assets, and deriving products (a.k.a., variants) out of those assets. However, it is not always possible to handle SPL evolution directly through these reusable assets. Time-to-market pressure, expedited bug fixes, or product specifics lead to the evolution to first happen at the product level, and to be later merged back into the SPL platform where the core assets reside. This is referred to as product-based evolution. In this scenario, deciding when and what should go into the next SPL release is far from trivial. Distinct questions arise. How much effort are developers spending on product customization? Which are the most customized core assets? To which extent is the core asset code being reused for a given product? We refer to this endeavor as Customization Analysis, i.e., understanding the functional increments in adjusting products from the last SPL platform release. The scale of the SPLs’ code-base calls for customization analysis to be conducted through Visual Analytics tools. This work addresses the design principles for such tools through a joint effort between academia and industry, specifically, Danfoss Drives, a company division in charge of the P400 SPL. Accordingly, we adopt an Action Design Research approach where answers are sought by interacting with the practitioners in the studied situations. We contribute by providing informed goals for customization analysis as well as an intervention in terms of a visual analytics tool. We conclude by discussing to what extent this experience can be generalized to product-based evolving SPL organizations other than Danfoss Drives.