An automatic process for weaving functional quality attributes using a software product line approach

Proceedings of the 22nd International Systems and Software Product Line Conference - Volume 1

Cortiñas

Fuentes

et al. 2018

Self Cite

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.

Section: Discussionmentioning

confidence: 99%

Section: Applying Our Approach To the Blog Splmentioning

confidence: 99%

Integrating the common variability language with multilanguage annotations for web engineering

Proceedings of the 22nd International Systems and Software Product Line Conference - Volume 1

Cortiñas

Fuentes

et al. 2018

Self Cite

“…Specifically, each variation point (dashed line) defines a transformation (eg, object existence, object substitution, and parameter assignment) in the software architecture that will be executed by the CVL engine when a particular configuration is selected in the variability model, adapting the components of the autonomous vehicle. () For example, when the context changes because the vehicle joins a motorway, a new configuration is generated: The new context is selected in the tree, and the IDM model is automatically selected in the configuration due to the cross‐tree constraints defined in OCL. The CVL engine will resolve the variability, changing the IDM component to be the car‐following model in the autonomous vehicle.…”

Section: Reconfigurable Vehicle Controller Agentmentioning

confidence: 99%

“…4 The bottom half of Figure 1 defines a transformation (eg, object existence, object substitution, and parameter assignment) in the software architecture that will be executed by the CVL engine 37 when a particular configuration is selected in the variability model, adapting the components of the autonomous vehicle. 38,39 For example, when the context changes because the vehicle joins a motorway, a new configuration is generated: The new context is selected in the tree, Each configuration of the controller is a set of choices in the variability model (features in grey in Figure 1). In our approach, we first generate a particular configuration of the reconfigurable vehicle controller agent, which is able to detect changes in weather conditions (rain intensity) and evaluate the traffic quality based on the selected indicators of safety (time to collision, post-encroachment time) and efficiency (travel time).…”

Section: Variability Modelling Of the Autonomous Vehicle: Traffic Conmentioning

confidence: 99%

Context‐dependent reconfiguration of autonomous vehicles in mixed traffic

J Software Evolu Process

Monteil

Bouroche

et al. 2017

Self Cite

Human drivers naturally adapt their behaviour depending on the traffic conditions, such as the current weather and road type. Autonomous vehicles need to do the same, in a way that is both safe and efficient in traffic composed of both conventional and autonomous vehicles. In this paper, we demonstrate the applicability of a reconfigurable vehicle controller agent for autonomous vehicles that adapts the parameters of a used car‐following model at runtime, so as to maintain a high degree of traffic quality (efficiency and safety) under different weather conditions. We follow a dynamic software product line approach to model the variability of the car‐following model parameters, context changes and traffic quality, and generate specific configurations for each particular context. Under realistic conditions, autonomous vehicles have only a very local knowledge of other vehicles' variables. We investigate a distributed model predictive controller agent for autonomous vehicles to estimate their behavioural parameters at runtime, based on their available knowledge of the system. We show that autonomous vehicles with the proposed reconfigurable controller agent lead to behaviour similar to that achieved by human drivers, depending on the context.

“…A first step toward mitigating this problem is applying the separation of concerns principle to model the variability of security from the early stages of the software's development. Thus, security concerns are modeled separately from the base applications and later customized to the application's requirements and composed at particular points of the application model [4,5]. It has been demonstrated that this approach has many advantages [4][5][6], such as high reusability, low coupled components and high cohesive software architectures.…”

Section: Introductionmentioning

confidence: 99%

Automatic Enforcement of Security Properties

Trust, Privacy and Security in Digital Business

Pinto

Fuentes

2016

Self Cite

Ensuring the security requirements of an application is not a straightforward task. Security properties (e.g., confidentiality, anonymity) need to be satisfied in different ways in different parts of the same application. Software architects are usually required to manually define security components and their dependencies with the base application, customize them to the application's requirements, identify the points where security is incorporated, and verify that the selected places are correct. The last two steps are especially complex and errorprone. In our approach, we aim to provide a solution that helps software architects to identify the correct places to incorporate the security functionality and to verify the correctness of the composed application architecture. This is achieved by identifying a set of general structural patterns for incorporating security into the application architecture, and by providing a model-driven SPL solution to customize these patterns to each application's requirements.