Assessing product line derivation operators applied to Java source code

2015 ◽  
Author(s):  
João Bosco Ferreira Filho ◽  
Simon Allier ◽  
Olivier Barais ◽  
Mathieu Acher ◽  
Benoit Baudry
Keyword(s):  
Source Code ◽  
Product Line

scholarly journals Resolving Code Smells in Software Product Line using Refactoring and Reverse Engineering

2020 ◽  
Author(s):  
Sami Ouali
Keyword(s):  
Reverse Engineering ◽  
Source Code ◽  
Software Product Line ◽  
Product Line ◽  
Production Costs ◽  
Code Smells ◽  
Product Lines ◽  
Software Products ◽  
Software Product ◽  
External Behavior

Software Product Lines (SPL) are recognized as a successful approach to reuse in software development. Its purpose is to reduce production costs. This approach allows products to be different with respect of particular characteristics and constraints in order to cover different markets. Software Product Line engineering is the production process in product lines. It exploits the commonalities between software products, but also to preserve the ability to vary the functionality between these products. Sometimes, an inappropriate implementation of SPL during this process can conduct to code smells or code anomalies. Code smells are considered as problems in source code which can have an impact on the quality of the derived products of an SPL. The same problem can be present in many derived products from an SPL due to reuse. A possible solution to this problem can be the refactoring which can improve the internal structure of source code without altering external behavior. This paper proposes an approach for building SPL from source code. Its purpose is to reduce code smells in the obtained SPL using refactoring source code. Another part of the approach consists on obtained SPL’s design based on reverse engineering.

scholarly journals Automated Features Extraction from Software Requirements Specification (SRS) Documents as The Basis of Software Product Line (SPL) Engineering

2020 ◽  
Vol 5 (3) ◽  
pp. 279
Author(s):  
M Syauqi Haris ◽  
Tri Astoto Kurniawan ◽  
Fatwa Ramdani
Keyword(s):  
Feature Extraction ◽  
Source Code ◽  
Software Product Line ◽  
Features Extraction ◽  
Product Line ◽  
Requirements Specification ◽  
Software Requirements ◽  
Pos Tagging ◽  
Software Product ◽  
Software Requirements Specification

Extractive Software Product Line Engineering (SPLE) puts features on the foremost aspect in domain analysis that needs to be extracted from the existing system's artifact. Feature in SPLE, which is closely related to system functionality, has been previously studied to be extracted from source code, models, and various text documents that exist along the software development process. Source code, with its concise and normative standard, has become the most focus target for feature extraction source on many kinds of research. However, in the software engineering principle, the Software Requirements Specification (SRS) document is the basis or main reference for system functionality conformance. Meanwhile, previous researches of feature extraction from text document are conducted on a list of functional requirement sentences that have been previously prepared, not literally SRS as a whole document. So, this research proposes direct processing on the SRS document that uses requirement boilerplates for requirement sentence statement. The proposed method uses Natural Language Processing (NLP) approach on the SRS document. Sequence Part-of-Speech (POS) tagging technique is used for automatic requirement sentence identification and extraction. The features are acquired afterward from extracted requirement sentences automatically using the word dependency parsing technique. Besides, mostly the previous researches about feature extraction were using non-public available SRS document that remains classified or not accessible, so this work uses selected SRS from publicly available SRS dataset to add reproducible research value. This research proves that requirement sentence extraction directly from the SRS document is viable with precision value from 64% to 100% and recall value from 64% to 89%. While features extraction from extracted requirement sentences has success rate from 65% to 88%.

scholarly journals Towards a Technological Ecosystem to Provide Information Dashboards as a Service: A Dynamic Proposal for Supplying Dashboards Adapted to Specific Scenarios

2021 ◽  
Vol 11 (7) ◽  
pp. 3249
Author(s):  
Andrea Vázquez-Ingelmo ◽  
Francisco José García-Peñalvo ◽  
Roberto Therón
Keyword(s):  
Data Analysis ◽  
Student Performance ◽  
New Technologies ◽  
Source Code ◽  
Software Product Line ◽  
Product Line ◽  
Knowledge Generation ◽  
Complex Task ◽  
Educational Context ◽  
Software Product

Data are crucial to improve decision-making and obtain greater benefits in any type of activity. However, the large amount of information generated by new technologies has made data analysis and knowledge generation a complex task. Numerous tools have emerged to facilitate this generation of knowledge, such as dashboards. Although dashboards are useful tools, their effectiveness can be affected by poor design or by not taking into account the context in which they are placed. Therefore, it is necessary to design and create custom dashboards according to the audience and data domain. This paper presents an application of the software product line paradigm and the integration of this approach into a web service to allow users to request source code for customized information dashboards. The main goal is to introduce the idea of creating a holistic ecosystem of different services to craft and integrate information visualizations in a variety of contexts. One of the contexts that can be especially favored by this approach is the educational context, where learning analytics, data analysis of student performance, and didactic tools are becoming very relevant. Three different use cases of this approach are presented to illustrate the benefits of the developed generative service.

scholarly journals Generating Software Product Line Model by Resolving Code Smells in the Products’ Source Code

2021 ◽  
Vol 12 (1) ◽  
pp. 1-10
Author(s):  
Sami Ouali
Keyword(s):  
Source Code ◽  
Software Product Line ◽  
Product Line ◽  
Production Costs ◽  
Feature Model ◽  
Software Systems ◽  
Code Smells ◽  
Product Lines ◽  
Bottom Up ◽  
Software Product

Software Product Lines (SPLs) refer to some software engineering methods, tools and techniques for creating a collection of similar software systems from a shared set of software assets using a common means of production. This concept is recognized as a successful approach to reuse in software development. Its purpose is to reduce production costs by reusing existing features and managing the variability between the different products with respect of particular constraints. Software Product Line engineering is the production process in product lines and the development of a family of systems by reusing core assets. It exploits the commonalities between software products and preserves the ability to vary the functionalities and features between these products. The adopted strategy for building SPL can be a top-down or bottom-up. Depending from the selected strategy, it is possible to face an inappropriate implementation in the SPL Model or the derived products during this process. The code can contain code smells or code anomalies. Code smells are considered as problems in source code which can have an impact on the quality of the derived products of an SPL. The same problem can be present in many derived products from an SPL due to reuse or in the obtained product line when the bottom-up strategy is selected. A possible solution to this problem can be the refactoring which can improve the internal structure of source code without altering external behavior. This paper proposes an approach for building SPL from source code using the bottom-up strategy. Its purpose is to reduce code smells in the obtained SPL using refactoring source code. This approach proposes a possible solution using reverse engineering to obtain the feature model of the SPL.

scholarly journals F2MoC: A Preliminary Product Line DSL for Mobile Robots

2012 ◽  
Author(s):  
Rafael S. Durelli ◽  
Vinicius H. S. Durelli
Keyword(s):  
Mobile Robots ◽  
Source Code ◽  
Product Line ◽  
Feature Model ◽  
Level Model ◽  
High Level

SPL and MDD have been drawing increased attention from the software community. In the literature it is possible to find a set of articles that apply MDD techniques to assist the development of a SPL. Objectives: To show how to create a DSL based on a feature model. Methods: A SPL and MDD techniques were used to create a DSL. Results: A DSL was developed in order to assist the development of the mobile robots. Conclusions: Advantages can be gained from using the DSL: (i) an easier instantiation of SPL members; (ii) it is possible for the engineers to focus on an high level model (i.e., features model), obviating the need of dealing with platform-specific issues; (iii) source code is generated automatically from this high level model.

scholarly journals Automatic Documentation of [Mined] Feature Implementations from Source Code Elements and Use-Case Diagrams with the REVPLINE Approach

2014 ◽  
Vol 24 (10) ◽  
pp. 1413-1438 ◽  
Author(s):  
R. Al-Msie'deen ◽  
M. Huchard ◽  
A.-D. Seriai ◽  
C. Urtado ◽  
S. Vauttier
Keyword(s):  
Source Code ◽  
Automatic Documentation ◽  
Product Line ◽  
Feature Model ◽  
Use Case ◽  
Mobile Media ◽  
Complementary Approach ◽  
Software Product ◽  
Information Retrieval Methods ◽  
Form Feature

Companies often develop a set of software variants that share some features and differ in others to meet specific requirements. To exploit the existing software variants as a Software Product Line (SPL), a Feature Model of this SPL must be built as a first step. To do so, it is necessary to define and document the optional and mandatory features that compose the variants. In our previous work, we mined a set of feature implementations as identified sets of source code elements. In this paper, we propose a complementary approach, which aims to document the mined feature implementations by giving them names and descriptions, based on the source code elements that form feature implementations and the use-case diagrams that specify software variants. The novelty of our approach is its use of commonality and variability across software variants, at feature implementation and use-case levels, to run Information Retrieval methods in an efficient way. Experiments on several real case studies (Mobile media and ArgoUML-SPL) validate our approach and show promising results.

Sign in / Sign up

Export Citation Format

Share Document