A formal framework for software product lines

Andrés, César; Camacho, Carlos; Llana, Luis

doi:10.1016/j.infsof.2013.05.005

Cited by 11 publications

(29 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Formal models allow for detecting errors in the early stages of the production process. Some of the existing approaches use algebras and semantics [5,6,7,8], while others use propositional or first order logic [9,10,11,12,13].…”

Section: Introductionmentioning

confidence: 99%

“…Thus, it is necessary to provide the original FODA graphical representation with formal semantics base, where automated analysis can be performed [15]. This issue is solved by using SPLA [8], a formal framework to represent FODA diagrams using process algebras. SPLA can only be applied not only to FODA, but also to represent other feature-related problems and variability models.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Cost-related interface for software product lines

Camacho

Llana

Núñez

2016

Journal of Logical and Algebraic Methods in Programming

Self Cite

View full text Add to dashboard Cite

Software Product Lines modeling improves software development processes by automating system debugging and analysis. The objective of this paper focuses on extending the formal framework SPLA to represent features such as cost objects and comparisons between products in terms of production costs. We illustrate this extension with a practical example by modeling the creation of valid run-lists for Chef, a widely used configuration management tool. Also, we execute our formal specification in a distributed system using SCOOP and we provide strategies to optimize the effort required to compute a SPLA term.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Cost-related interface for software product lines

Camacho

Llana

Núñez

2016

Journal of Logical and Algebraic Methods in Programming

Self Cite

View full text Add to dashboard Cite

show abstract

“…A software product line (SPL) [20]- [25] [41] [42] is a set of software intensive systems that share a common and managed set of features satisfying the specific needs of a particular market segment developed from a common set of core assets in a prescribed way [21] [23]. SPL engineering aims at: effective utilization of software assets, reducing the time required to deliver a product, improving quality, and decreasing the cost of software products.…”

Section: Literature Reviewmentioning

confidence: 99%

“…Furthermore, as the requirement of SECO to support adaptation capabilities of systems is increasing in importance [20] it is recommended such adaptive features be included within software product lines (SPL) [21] [22] [23] [24]. The SPL concept is appealing to organizations dealing with software development that aims to provide a comprehensive model for an organization building applications based on a common architecture and core assets [20] [21].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Semantic Metadata Enrichment Software Ecosystem (SMESE) Based on a Multi-Platform Metadata Model for Digital Libraries

Brisebois¹,

Abran²,

Nadembéga³

2017

JSEA

View full text Add to dashboard Cite

Software industry has evolved to multi-product and multi-platform development based on a mix of proprietary and open source components. Such integration has occurred in software ecosystems through a software product line engineering (SPLE) process. However, metadata are underused in the SPLE and interoperability challenge. The proposed method is first, a semantic metadata enrichment software ecosystem (SMESE) to support multi-platform metadata driven applications, and second, based on mapping ontologies SMESE aggregates and enriches metadata to create a semantic master metadata catalogue (SMMC). The proposed SPLE process uses a component-based software development approach for integrating distributed content management enterprise applications, such as digital libraries. To perform interoperability between existing metadata models (such as Dublin Core, UNIMARC, MARC21, RDF/RDA and BIBFRAME), SMESE implements an ontology mapping model. SMESE consists of nine sub-systems: 1) Metadata initiatives & concordance rules; 2) Harvesting of web metadata & data; 3) Harvesting of authority metadata & data; 4) Rule-based semantic metadata external enrichment; 5) Rule-based semantic metadata internal enrichment; 6) Semantic metadata external & internal enrichment synchronization; 7) User interest-based gateway; 8) Semantic master catalogue. To conclude, this paper proposes a decision support process, called SPLE decision support process (SPLE-DSP) which is then used by SMESE to support dynamic reconfiguration. SPLE-DSP consists of a dynamic and optimized metadata-based reconfiguration model. SPLE-DSP takes into account runtime metadata-based variability functionalities, context-awareness and self-adaptation. It also presents the design and implementation of a working prototype of SMESE applied to a semantic digital library.

show abstract

Chaos as a Software Product Line—A platform for improving open hybrid‐cloud systems resiliency

et al. 2022

Self Cite

View full text Add to dashboard Cite

Nowadays, cloud-native software architectures have a significant relevance due to the speed and agility they provide. These properties lead relevant organizations in different industries, like video streaming (Netflix), car-sharing (Uber, Cabify), banking (BBVA, HSBC), and governmental agencies (NASA, FBI, CERN, ESA) to heavily rely on cloud-native software to run their business-critical applications. Additionally, including fault injection actions in the production infrastructure allows companies to have consistent environments, to improve applications dependability against unexpected failures, to provide better user experience, and to improve the overall system quality. Thus, cloud computing technologies allow development teams to rapidly create complex systems and to continuously deploy them, at a global scale. This work describes Pystol, a novel fault injection platform-represented as aSoftware Product Line-to analyze the effects caused by a wide spectrum of adverse conditions. Pystol is designed to be executed on top of cloud-native environments, either in private or public clouds. The proposed architecture shows a way for representing feature models based on Unified Model Language (in short, UML) component diagrams. Furthermore, we present a thorough empirical study carried out in real-world environments, providing promising results.

show abstract

A formal framework for software product lines

Cited by 11 publications

References 16 publications

Cost-related interface for software product lines

Cost-related interface for software product lines

A Semantic Metadata Enrichment Software Ecosystem (SMESE) Based on a Multi-Platform Metadata Model for Digital Libraries

Chaos as a Software Product Line—A platform for improving open hybrid‐cloud systems resiliency

Contact Info

Product

Resources

About