Relevant bibliographies by topics / Software Product Line models

Academic literature on the topic 'Software Product Line models'

Author: Grafiati
Published: 4 June 2021
Last updated: 16 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software Product Line models.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Journal articles on the topic "Software Product Line models":

1

Elsawi, Ahmed Mohammed, and Shamsul Sahibuddin. "Model Driven Atchitecture in to Support of Software Product Line." International Journal of Computer and Electrical Engineering 7, no. 1 (2015): 26–46. http://dx.doi.org/10.17706/ijcee.2015.v7.871.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Ouali, Sami, Naoufel Kraïem, Zuhoor Al-Khanjari, and Youcef Baghdadi. "Model Driven Software Product Line Process for Service/Component-Based Applications." Journal of Software 10, no. 7 (July 2015): 881–92. http://dx.doi.org/10.17706//jsw.10.7.881-892.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Bagheri, Ebrahim, and Faezeh Ensan. "Dynamic decision models for staged software product line configuration." Requirements Engineering 19, no. 2 (February 9, 2013): 187–212. http://dx.doi.org/10.1007/s00766-013-0165-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Farahani, Elham Darmanaki, and Jafar Habibi. "Configuration Management Model in Evolutionary Software Product Line." International Journal of Software Engineering and Knowledge Engineering 26, no. 03 (April 2016): 433–55. http://dx.doi.org/10.1142/s0218194016500182.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
In Software Product Line (SPL), Configuration Management (CM) is a multi-dimensional problem. On the one hand, the Core Assets that constitute a configuration need to be managed, and on the other hand, each product in the product line that is built using a configuration must be managed, and furthermore, the management of all these configurations must be coordinated under a single process. Therefore, CM for product lines is more complex than for single systems. The CM of any software system involves four closely related activities: Change Management (ChM), Version Management (VM), System Building (SB) and Release Management (RM) [I. Sommerville, Software Engineering, 9th edn. (Addison-Wesley, 2010)]. The aim of this paper is to provide ChM and VM models for evolutionary-based SPL system development and maintenance. The proposed models support any level of aggregation in SPLs and have been applied to Mobile SPL as a case study.
5

Dehmouch, Ikram, Bouchra El Asri, Maryem Rhanoui, and Mina El Maallam. "Feature Models Preconfiguration Based on User Profiling." Computer and Information Science 12, no. 1 (January 22, 2019): 59. http://dx.doi.org/10.5539/cis.v12n1p59.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Feature modeling is used to express commonality and variability among a family of software products called the software product line. To offer customized products to their customers, organizations need to build packages of features taking into consideration customer needs and preferences. This paper presents a platform named SPLP (Software Product Line Profiling) which allows pre-configuring feature models through the restriction of the configuration space to meet the requirements of a specific market segment. Considering that concerns and preferences of this latter are a key criteria to achieve a tailored pre-configuration, authors propose the integration of user profiling in the SPLP platform through the definition of a user profile model describing information about the user and the products he is used to consume. This information is then exploited by the SPLP platform to perform an automated pre-configuration according to each user profile requirements and preferences.
6

Bashari, Mahdi, Ebrahim Bagheri, and Weichang Du. "Dynamic Software Product Line Engineering: A Reference Framework." International Journal of Software Engineering and Knowledge Engineering 27, no. 02 (March 2017): 191–234. http://dx.doi.org/10.1142/s0218194017500085.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Runtime adaptive systems are able to dynamically transform their internal structure, and hence their behavior, in response to internal or external changes. Such transformations provide the basis for new functionalities or improvements of the non-functional properties that match operational requirements and standards. Software Product Line Engineering (SPLE) has introduced several models and mechanisms for variability modeling and management. Dynamic software product lines (DSPL) engineering exploits the knowledge acquired in SPLE to develop systems that can be context-aware, post-deployment reconfigurable, or runtime adaptive. This paper focuses on DSPL engineering approaches for developing runtime adaptive systems and proposes a framework for classifying and comparing these approaches from two distinct perspectives: adaptation properties and adaptation realization. These two perspectives are linked together by a series of guidelines that help to select a suitable adaptation realization approach based on desired adaptation types.
7

HERADIO, RUBEN, DAVID FERNANDEZ-AMOROS, JOSE A. CERRADA, and ISMAEL ABAD. "A LITERATURE REVIEW ON FEATURE DIAGRAM PRODUCT COUNTING AND ITS USAGE IN SOFTWARE PRODUCT LINE ECONOMIC MODELS." International Journal of Software Engineering and Knowledge Engineering 23, no. 08 (October 2013): 1177–204. http://dx.doi.org/10.1142/s0218194013500368.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
In software product line engineering, feature diagrams are a popular means to represent the similarities and differences within a family of related systems. In addition, feature diagrams implicitly model valuable information that can be used in economic models to estimate the cost savings of a product line. In particular, this paper reviews existing proposals on computing the total number of products modeled with a feature diagram and, given a feature, the number of products that implement it. This paper also reviews the economic information that can be estimated when such numbers are known. Thus, this paper contributes by bringing together previously-disparate streams of work: the automated analysis of feature diagrams and economic models for product lines.
8

Castro, Thiago, Leopoldo Teixeira, Vander Alves, Sven Apel, Maxime Cordy, and Rohit Gheyi. "A Formal Framework of Software Product Line Analyses." ACM Transactions on Software Engineering and Methodology 30, no. 3 (May 2021): 1–37. http://dx.doi.org/10.1145/3442389.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
A number of product-line analysis approaches lift analyses such as type checking, model checking, and theorem proving from the level of single programs to the level of product lines. These approaches share concepts and mechanisms that suggest an unexplored potential for reuse of key analysis steps and properties, implementation, and verification efforts. Despite the availability of taxonomies synthesizing such approaches, there still remains the underlying problem of not being able to describe product-line analyses and their properties precisely and uniformly. We propose a formal framework that models product-line analyses in a compositional manner, providing an overall understanding of the space of family-based, feature-based, and product-based analysis strategies. It defines precisely how the different types of product-line analyses compose and inter-relate. To ensure soundness, we formalize the framework, providing mechanized specification and proofs of key concepts and properties of the individual analyses. The formalization provides unambiguous definitions of domain terminology and assumptions as well as solid evidence of key properties based on rigorous formal proofs. To qualitatively assess the generality of the framework, we discuss to what extent it describes five representative product-line analyses targeting the following properties: safety, performance, dataflow facts, security, and functional program properties.
9

Bagheri, Ebrahim, and Dragan Gasevic. "Assessing the maintainability of software product line feature models using structural metrics." Software Quality Journal 19, no. 3 (January 1, 2011): 579–612. http://dx.doi.org/10.1007/s11219-010-9127-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Martinez, Cristian, Silvio Gonnet, and Horacio Leone. "A Petri Net approach for representing Orthogonal Variability Models." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 9, no. 1 (June 30, 2013): 995–1003. http://dx.doi.org/10.24297/ijct.v9i1.4158.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
The software product line (SPL) paradigm is used for developing software system products from a set of reusable artifacts, known as platform. The Orthogonal Variability Modeling (OVM) is a technique for representing and managing the variability and composition of those artifacts for deriving products in the SPL. Nevertheless, OVM does not support the formal analysis of the models. For example, the detection of dead artifacts (i.e., artifcats that cannot be included in any product) is an exhaustive activity which implies the verification of relationships between artifacs, artifacts parents, and so on. In this work, we introduce a Petri nets approach for representing and analyzing OVM models. The proposed net is built from elemental topologies that represents OVM concepts and relationships. Finally, we simulate the net and study their properties in order to avoid the product feasibility problems.
More sources
You might also be interested in the extended bibliographies on the topic 'Software Product Line models' for particular source types:
Journal articles Dissertations / Theses Books

Dissertations / Theses on the topic "Software Product Line models":

1

Ramos, Alves Vander. "Implementing software product line adoption strategies." Universidade Federal de Pernambuco, 2007. https://repositorio.ufpe.br/handle/123456789/2044.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Made available in DSpace on 2014-06-12T15:54:05Z (GMT). No. of bitstreams: 2 arquivo6551_1.pdf: 2254714 bytes, checksum: 89a6702d1c801f178299f95585aac5ab (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2007
Linha de Produtos de Software (LPS) é uma aborgadem promissora para o desenvolvimento de um conjunto de produtos focados em um segmento de mercado e desenvolvidos a partir de um conjunto comum de artefatos. Possíveis benefícios incluem reuso em larga escala e significativa melhoria em produtividade. Um problema-chave associado, no entanto, é o tratamento de estratégias de implantação, em que uma organização decide iniciar uma LPS a partir do zero, fazer bootstrap de produtos existentes em uma LPS, ou evoluir uma LPS. Em particular, no nível de implementação e de modelo de features, métodos de desenvolvimento carecem de apoio adequado para extração e evolução de LPSs. Neste contexto, apresentamos um m´etodo original provendo diretrizes concretas para extração e evolução de LPSs no nível de implementação e de modelo de features, nos quais proporciona reuso e segurança. O método primeiro faz o bootstrap da LPS e então a evolui com uma abordagem reativa. O método se baseia em uma coleção de refatoramentos tanto na implementação (refatoramentos orientados a aspectos) como no modelo de features. O método foi avaliado no domínio altamente variável de jogos móveis
2

Nóbrega, Jarley Palmeira. "An integrated cost model for product line engineering." Universidade Federal de Pernambuco, 2008. https://repositorio.ufpe.br/handle/123456789/1639.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Made available in DSpace on 2014-06-12T15:51:39Z (GMT). No. of bitstreams: 2 arquivo1682_1.pdf: 1782765 bytes, checksum: f72b8949fcd20828665cc0a45ca4034d (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008
Dentro da comunidade de desenvolvimento de software, o processo de reutilizar artefatos ao invés de construí-los do zero normalmente conhecido como reuso de software tem se mostrado uma maneira efetiva de evitar os problemas associados ao estouro de orçamentos e cronogramas de projeto. Apesar do imenso potencial, a adoção de reuso em larga escala ainda não prevalece dentro das organizações. Entre os fatores que contribuem para isso, estão os obstáculos econômicos enfrentados pelas empresas, com uma clara preocupação sobre os custos para desenvolver software para e com reuso. Atualmente, as decisões relacionadas com reuso são tratadas sob um ponto de vista econômico, devido ao fato do desenvolvimento de software reutilizável ser considerado pelas organizações como um investimento. Além disso, a adoção de linhas de produto de software dentro desse contexto traz à tona alguns inibidores de reuso, como por exemplo, a aplicação dos modelos de custo para reuso de forma restrita, a falta de uma estratégia para a análise de investimentos, e o fato que poucos modelos de custo possuem uma abordagem baseada na utilização de cenários de reuso. Nesse contexto, esse trabalho apresenta um modelo integrado de custo para engenharia de linhas de produto, com o objetivo de auxiliar as organizações em seus processos de tomada de decisões na avaliação de investimentos em reuso. Os fundamentos para o modelo foram baseados em uma vasta pesquisa sobre modelos de custo para reuso e sua especialização para linhas de produto de software. O modelo apresenta a definição de funções de custo e benefícios, cenários de reuso e uma estratégia de investimento para linhas de produto. Também é apresentado um modelo de simulação baseado na técnica de Monte Carlo. Por último, um estudo de caso discute os resultados de dentro do contexto de um projeto real de desenvolvimento de software, onde o modelo foi aplicado
3

Salinas, Edward Mauricio Alferez. "Derivation and consistency checking of models in early software product line engineering." Doctoral thesis, Faculdade de Ciências e Tecnologia, 2012. http://hdl.handle.net/10362/9370.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Dissertação para obtenção do Grau de Doutor em Engenharia Informática
Software Product Line Engineering (SPLE) should offer the ability to express the derivation of product-specific assets, while checking for their consistency. The derivation of product-specific assets is possible using general-purpose programming languages in combination with techniques such as conditional compilation and code generation. On the other hand, consistency checking can be achieved through consistency rules in the form of architectural and design guidelines, programming conventions and well-formedness rules. Current approaches present four shortcomings: (1) focus on code derivation only, (2) ignore consistency problems between the variability model and other complementary specification models used in early SPLE, (3) force developers to learn new, difficult to master, languages to encode the derivation of assets, and (4) offer no tool support. This dissertation presents solutions that contribute to tackle these four shortcomings. These solutions are integrated in the approach Derivation and Consistency Checking of models in early SPLE (DCC4SPL) and its corresponding tool support. The two main components of our approach are the Variability Modelling Language for Requirements(VML4RE), a domain-specific language and derivation infrastructure, and the Variability Consistency Checker (VCC), a verification technique and tool. We validate DCC4SPL demonstrating that it is appropriate to find inconsistencies in early SPL model-based specifications and to specify the derivation of product-specific models.
European Project AMPLE, contract IST-33710; Fundação para a Ciência e Tecnologia - SFRH/BD/46194/2008.
4

Sousa, André Luís Sequeira de. "Traceability support in software product lines." Master's thesis, FCT - UNL, 2008. http://hdl.handle.net/10362/1798.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Dissertação apresentada na Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa para a obtenção do grau de Mestre em Engenharia Informática.
Traceability is becoming a necessary quality of any modern software system. The complexity in modern systems is such that, if we cannot rely on good techniques and tools it becomes an unsustainable burden, where software artifacts can hardly be linked to their initial requirements. Modern software systems are composed by a many artifacts (models, code, etc.). Any change in one of them may have repercussions on many components. The assessment of this impact usually comes at a high cost and is highly error-prone. This complexity inherent to software development increases when it comes to Software Product Line Engineering. Traceability aims to respond to this challenge, by linking all the software artifacts that are used, in order to reason about how they influence each others. We propose to specify, design and implement an extensible Traceability Framework that will allow developers to provide traceability for a product line, or the possibility to extend it for other development scenarios. This MSc thesis work is to develop an extensible framework, using Model-Driven techniques and technologies, to provide traceability support for product lines. We also wish to provide basic and advanced traceability queries, and traceability views designed for the needs of each user.
5

Rossel, Cid Pedro Osvaldo. "Software product line model for the meshing tool domain." Tesis, Universidad de Chile, 2013. http://www.repositorio.uchile.cl/handle/2250/113113.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Doctor en Ciencias, Mención Computación
Una malla es una discretización de la geometría de un cierto dominio. Las mallas pueden estar compuestas de diversos elementos: triángulos, cuadriláteros, tetraedros, etc. Una herramienta para la generación de mallas es un aplicación que permite crear, refinar, desrefinar, mejorar, suavizar, visualizar y posprocesar mallas y/o una región particular de ella, como también asignar valores físicos a los elementos de la malla (temperatura, concentración, etc.). Las herramientas para la generación de mallas son complejas y sofisticadas, y construir una herramienta nueva desde cero o mantener una existente, demanda un esfuerzo enorme. Existe una necesidad y oportunidad para usar enfoques nuevos en el desarrollo de estas herramientas, de manera de reducir tanto el tiempo como los costos de desarrollo, sin comprometer la calidad. La experiencia en el desarrollo de estas herramientas provee la motivación para la construcción de otras nuevas mediante la reutilización del trabajo realizado durante los desarrollos previos. Estas herramientas comparten varias características y sus variaciones pueden ser manejadas sistemáticamente. Esto hace que el desarrollo de estas herramientas sea una buena oportunidad para aplicar el enfoque de Línea de Productos de Software (LPS). Los procesos existentes de LPS son generales y requieren usualmente una serie de pasos y documentación innecesaria en el dominio de las herramientas para la generación de mallas. Así, esta tesis propone un modelo de proceso de LPS específico para este tipo de herramientas. Un proceso de desarrollo de LPS está centrado en la reutilización de software, e involucra principalmente dos fases: la ingeniería del dominio (ID) y la ingeniería de la aplicación (IA). El proceso presentado en este trabajo está centrado en dos etapas de la ID: el análisis del dominio (AD) y el diseño del dominio (DD). En el AD se define el modelo del dominio y el alcance de la LPS. En el DD la arquitectura de la línea de productos (ALP) es creada; esta arquitectura es válida y compartida por todos los productos en la LPS. Un modelo de características es comúnmente usado para modelar el dominio. En este trabajo, el AD también ocupa un diccionario, escenarios, acciones y metas para proveer el razonamiento utilizado para la construcción del modelo de características. Esta tesis presenta un proceso riguroso para obtener el modelo del dominio. Este modelo es formalizado mediante condiciones de consistencia y completitud. El proceso de definición del alcance es presentado a través de un diagrama de actividad. Además, el enfoque presentado en esta tesis presenta explícitamente los diferentes productos de la LPS, estableciendo relaciones entre productos y las características de la LPS, lo que permite administrar el desarrollo del producto. La etapa de DD se centra en la creación de la ALP, artefacto esencial para la construcción de productos de la LPS. Para ello, este trabajo provee un proceso deductivo y otro transformacional. En el primero, una ALP explícita es desarrollada, usando los artefactos producidos en el AD. Además, tanto la vista arquitectónica estructural como la de comportamiento son establecidas. Ambas vistas son generales y permiten la representación de cualquier producto dentro del alcance de la LPS. En el proceso transformacional, una ALP implícita es desarrollada usando reglas de transformación, las que han sido creadas usando artefactos producidos en el AD. En este proceso se produce la arquitectura para productos específicos, y la ALP es definida como la suma de todas las arquitecturas de los productos. Tanto el AD como el DD son descritos en detalle, y la aplicación del modelo de la LPS es ilustrado a través de un ejemplo bien documentado en el dominio de las herramientas para la generación de mallas, el que tiene un grado relativamente alto de complejidad. En este ejemplo, un modelo del dominio formalizado es introducido, y la arquitectura es definida tanto para el proceso deductivo como para el transformacional.
6

Mazo, Raul. "A Generic Approach for Automated Verification of Product Line Models." Phd thesis, Université Panthéon-Sorbonne - Paris I, 2011. http://tel.archives-ouvertes.fr/tel-00707351.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
This thesis explores the subject of automatic verification of product line models. This approach is based on the hypothesis that to automatically verify product line models, they should first be transformed into a language that makes them computable. In this thesis, product line models are transformed into constraint (logic) programs, then verified against a typology of verification criteria. The typology enumerates, classifies and formalizes a collection of generic verification criteria, i.e. criteria that can be applied (with or without adaptation) to any product line formalism. The typology makes the distinction between two categories of criteria: criteria that deal with the formalism in which models are represented, and the formalism-independent criteria. To identify defects in the first category, the thesis proposes a conformance checking approach directly related with verification of the abstract syntactic aspects of a model. To identify defects in the second category, the thesis proposes a domain-specific verification approach. An optimal algorithm is specified and implemented in constraint logic program for each criterion in the typology. These can be used independently -or in combination- to verify individual product line models. The thesis offers to support the verification of multiple product line models using an integration approach. Besides, this thesis proposes a series of integration strategies that can be used before applying the verification as for individual models. The product line verification approach proposed in this thesis is generic in the sense that it can be reused for any kind of product line model that instantiates the generic meta model based on which it was developed. It is general in the sense that it supports the verification of a comprehensive collection of criteria defined in the typology. This approach was implemented in a prototype tool that supports the specification, transformation, integration, configuration, analysis and verification of product line models via constraints (logic) programming. A benchmark gathering a corpus of 54 product line models was developed, then used in a series of experiments. The experiments showed that (i) the implementation of the domain-specific verification approach is fast and scalable to product line models up-to 2000 artefacts; (ii) the implementation of the conformance checking approach is fast and scalable to product line models up-to 10000 artefacts; and (iii) both approaches are correct and useful for industrial-size models.
7

Greaney, Kevin J. "Evolving a simulation model product line software architecture from heterogeneous model representations." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03sep%5FGreaney%5FPhD.pdf.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Istoan, Paul. "Methodology for the derivation of product behaviour in a Software Product Line." Phd thesis, Université Rennes 1, 2013. http://tel.archives-ouvertes.fr/tel-00925479.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
The major problem addressed in this thesis is the definition of a new SPLE methodology that covers both phases of the SPLE process and focuses on the derivation of behavioral models of SPL products. In Chapter 2 three research areas scope context of this thesis: Software Product Lines, Business Processes, and Model-Driven Engineering. Throughout Chapter 3, we propose a new SPLE methodology that focuses on the derivation of product behavior. We first describe the main flow of the methodology, and then detail the individual steps. In chapter 4 we propose a new domain specific language called CBPF created for modeling composable business process fragments. A model driven approach is followed for creating CBPF: definition of the abstract syntax, graphical concrete syntax and translational semantics. In Chapter 5 we propose several types of verifications that can be applied to business processfragments to determine their "correctness". For structural verification we definine a set of fragment consistency rules that should be valid for every business process fragment created with CBPF. To check behavioral correctness we first transform the business process fragment into an equivalent HCPN. We can then check generic properties but also define aset of fragment specific properties. In chapter 6 we exemplify the proposed SPL methodology by applying it to a case study from the crisis management system domain. We also propose a tool suite that supports our methodology. Chapter 7 describes possible improvements and extensions to the contributions of this thesis. We conclude the thesis in Chapter 8 and draw some conclusions.
9

Seidl, Christoph. "Evolution in Feature-Oriented Model-Based Software Product Line Engineering." Master's thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2012. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-81200.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Software Product Lines (SPLs) are a successful approach to software reuse in the large. Even though tools exist to create SPLs, their evolution is widely unexplored. Evolving an SPL manually is tedious and error-prone as it is hard to avoid unintended side-effects that may harm the consistency of the SPL. In this thesis, the conceptual basis of a system for the evolution of model-based SPLs is presented, which maintains consistency of models and feature mapping. As basis, a novel classification is introduced that distinguishes evolutions by their potential to harm the mapping of an SPL. Furthermore, multiple remapping operators are presented that can remedy the negative side-effects of an evolution. A set of evolutions is complemented with appropriate remapping operations for the use in SPLs. Finally, an implementation of the evolution system in the SPL tool FeatureMapper is provided to demonstrate the capabilities of the presented approach when co-evolving models and feature mapping of an SPL.
10

Verdier, Frédéric. "COMpOSER : a model-driven software product line approach for an effective management of software reuse within software product families and populations." Thesis, Montpellier, 2019. http://www.theses.fr/2019MONTS117.

Full text
APA, Harvard, Vancouver, ISO, and other styles
Abstract:
Avec la constante croissance en taille et en complexité des systèmes logiciels, l'industrie logicielle est poussée à migrer ses processus de développements manuels, réalisant chaque produit individuellement et lentement, vers des procédés systématiques et automatisés, produisant massivement des logiciels et à moindre coût. Cette migration, que nous appelons industrialisation, peut être réalisée en favorisant à la fois la réutilisation logicielle systématique et l'automatisation dans les phases de développement. Favoriser ces pratiques permet la réalisation de produits de meilleure qualité à coût réduit. Les approches existantes combinant l'Architecture Dirigée par les Modèles (MDA) et l'Ingénierie des Lignes de Produits Logiciels (SPLE) automatisent la réutilisation dans leurs processus de développement en exploitant les avantages de MDA et SPLE. Tandis que MDA permet aux développeurs de définir des artefacts hautement réutilisables et des opérations automatiques à effectuer sur ces artefacts, SPLE systématise la réutilisation en s'appuyant sur les similarités et les différences d'un ensemble de produits similaires appelé famille de produits logiciels. Cependant, ces combinaisons souffrent de deux restrictions majeures pouvant être un frein aux entreprises souhaitant industrialiser leurs processus en utilisant ces solutions. D’une part, il leur est difficile de gérer efficacement la variabilité. En effet, la complexité des opérations effectuées sur les artefacts dépend du nombre de points de variation à gérer. D'autre part, ces approches se limitent à gérer la variabilité au sein d'une famille de produits. Or, dans certains contextes comme les sociétés de services, la variabilité peut concerner un ensemble plus hétérogène de produits nommé population de produits. Bien que certains travaux proposent de gérer la variabilité au sein d'une population de produits, ces derniers, en proposant de composer des lignes de produits indépendantes, limitent la composition, et ainsi la réutilisation, d'artefacts à gros grain.Dans cette thèse, nous proposons une nouvelle approche nommée COMpOSER (CrOss-platform MOdel-driven Software product line EngineeRing) définissant une solution efficace pour composer MDA et SPLE afin d'exploiter intégralement la variabilité à la fois d'une famille mais également d'une population de produits logiciels. Pour cela, COMpOSER introduit une nouvelle caractérisation de la variabilité pour organiser des artefacts réutilisables selon trois dimensions : la dimension métier ; la dimension architecturale ; et la dimension des écosystèmes technologiques. De plus, cette caractérisation distingue la variabilité inter-domaine, responsable de l'organisation des différentes familles au sein d'une population, et la variabilité intra-domaine, organisant les artefacts dans chaque famille. Afin d'organiser correctement ces artefacts, COMpOSER définit un modèle d'artefacts réutilisables à fine granularité étant compatible avec cette caractérisation. Par ailleurs, notre approche définit des opérations partiellement automatisées systématisant la réutilisation d'artefacts lors de la production de nouveaux logiciels sans induire de difficulté de passage à l'échelle avec l'ajout de nouveaux points de variation. Grâce à notre collaboration avec un partenaire industriel, nous avons pu expérimenter COMpOSER pour aider à l'industrialisation des processus de développement de l'entreprise. Ainsi, nous avons réalisé un framework qui réifie notre approche tout en considérant les spécificités de notre contexte industriel. Cet outil traduit les principes de COMpOSER dans un langage adapté à des développeurs sans expertise en SPLE ou MDA, facilitant ainsi l'adoption de nos solutions par les équipes de développements de l'entreprise. Nous avons obtenu des résultats démontrant que notre approche améliore la réutilisation logicielle systématique comparativement à des solutions concurrentes sur des cas d'études industriels concrets
Software systems are constantly increasing in size and complexity, forcing the software industry to migrate their hand-craft development processes, slowly realizing each product, to more systematized and automated ones, mass-producing software at lower costs. This migration process, that we call industrialization, can be achieved through the integration of systematic software reuse and automation in their development processes. Their combination results in the realization of sounder products at lower costs. Existing approaches combining Model-Driven Architecture (MDA) and Software Product Line Engineering (SPLE) partially automate development processes with systematic software reuse by capitalizing on their compatible benefits. While MDA permits developers to define highly reusable assets and automatic operations to perform on them, SPLE systematizes software reuse by relying on the commonalities and variabilities of a set of related products named a software product family. However, these approaches suffer from two major restrictions that can be a brake for companies aiming to industrialize their development processes using these solutions. Firstly, they have difficulties to fully manage variability at different levels of abstraction because of the rapidly increasing complexity of operations performed on assets alongside the addition of new variation points. Then, existing combinations of MDA and SPLE are limited to the management of variability in a software product family. But, in some contexts such as IT services companies, variability can be related to more heterogeneous sets of products than families named software product populations. Although some existing works propose to manage the variability in a software product population, these approaches, by composing independent software product lines, are limited to the composition, and by extension to reuse, of coarse-grained assets.In this PhD thesis, we propose a new approach named COMpOSER (CrOss-platform MOdel-driven Software product line EngineeRing) which defines an efficient way to compose MDA and SPLE in order to fully manages variability in a software product family but also in a software product population without reducing its reuse capabilities. To do so, COMpOSER introduces a new characterization of variability to organize reusable assets in three dimensions: the business dimension; the architecture dimension; and the technological ecosystem dimension. Additionally, this characterization distinguishes inter-domain variability, organizing the different software product families of a population, and intra-domain variability, organizing assets in a single software product family. To properly organize reusable assets, COMpOSER defines a model of fine-grained core assets which is compatible with its characterization of variability. In parallel, our approach defines partially automated operations to produce new software through systematic reuse which permit to fully manage variability without inducing scaling up issues with the addition of new variation points. Thanks to our collaboration with an industrial partner, we could experiment COMpOSER by applying our propositions to help the company industrializing its development processes. As such, we implemented a framework that supports our approach while considering the specificities of our industrial context. This framework embeds the principles of COMpOSER in a format that is easier to understand to developers with little knowledge about SPLE and MDA. In this way, we have observed that the framework facilitated the adoption of our solutions by the company's development teams. Using the COMpOSER framework, we obtained results demonstrating how our approach improves systematic software reuse when compared to concurrent approaches. These results stemmed from empirical experiments performed on concrete industrial case studies
More sources

Books on the topic "Software Product Line models":

1

Arboleda, Hugo, and Jean-Claude Royer. Model-Driven and Software Product Line Engineering. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2012. http://dx.doi.org/10.1002/9781118561379.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Rashid, Awais, Jean-Claude Royer, and Andreas Rummler. Aspect-oriented, model-driven software product lines: The AMPLE way. Cambridge: Cambridge University Press, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Pohl, Klaus, Günter Böckle, and Frank van der Linden. Software Product Line Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/3-540-28901-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Kang, Kyo C. Applied software product line engineering. Boca Raton: Auerbach Publications, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Kang, Kyo C. Applied software product line engineering. Boca Raton: Auerbach Publications, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Rashid, Awais, Jean-Claude Royer, and Andreas Rummler, eds. Aspect-Oriented, Model-Driven Software Product Lines. Cambridge: Cambridge University Press, 2011. http://dx.doi.org/10.1017/cbo9781139003629.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Dobrica, Liliana. A strategy for analyzing product line software architectures. Espoo [Finland]: Technical Research Centre of Finland, 2000.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Ginsburgh, Victor. Price discrimination and product line rivalry. Toronto, Ont: York University, 1987.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Dobson, Gregory. Positioning and pricing a product line. [Tel Aviv, Israel]: Tel Aviv University, Faculty of Management, Leon Recanati Graduate School of Business Administration, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Software, Product Lines Conference (15th 2011 Munich Germany). 15th International Software Product Line Conference: Proceedings : Munich, Germany, 21-26 August 2011. Los Alamitos, Calif: IEEE Computer Society, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software Product Line models":

1

Clements, Paul. "Panel: A Competition of Software Product Line Economic Models." In Software Product Lines, 136. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11554844_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Muthig, Dirk, and Colin Atkinson. "Model-Driven Product Line Architectures." In Software Product Lines, 110–29. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-45652-x_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Czarnecki, Krzysztof, Simon Helsen, and Ulrich Eisenecker. "Staged Configuration Using Feature Models." In Software Product Lines, 266–83. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-28630-1_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Batory, Don. "Feature Models, Grammars, and Propositional Formulas." In Software Product Lines, 7–20. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11554844_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Hein, Andreas, Michael Schlick, and Renato Vinga-Martins. "Applying Feature Models in Industrial Settings." In Software Product Lines, 47–70. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-4339-8_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

von der Maßen, Thomas, and Horst Lichter. "Determining the Variation Degree of Feature Models." In Software Product Lines, 82–88. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11554844_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Mannion, Mike. "Using First-Order Logic for Product Line Model Validation." In Software Product Lines, 176–87. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-45652-x_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Oldevik, Jon, Arnor Solberg, Øystein Haugen, and Birger Møller-Pedersen. "Evaluation Framework for Model-Driven Product Line Engineering Tools." In Software Product Lines, 589–618. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/978-3-540-33253-4_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Greenfield, Jack. "Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools." In Software Product Lines, 304. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-28630-1_19.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Mannion, Mike, and Javier Camara. "Theorem Proving for Product Line Model Verification." In Software Product-Family Engineering, 211–24. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24667-1_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software Product Line models":

1

Casalánguida, Hernán, and Juan Eduardo Durán. "Automatic generation of feature models from UML requirement models." In the 16th International Software Product Line Conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2364412.2364415.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

van den Broek, Pim. "Intersection of feature models." In the 16th International Software Product Line Conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2364412.2364423.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Itzik, Nili, and Iris Reinhartz-Berger. "Generating feature models from requirements." In the 18th International Software Product Line Conference. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2647908.2655966.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Andersen, Nele, Krzysztof Czarnecki, Steven She, and Andrzej Wąsowski. "Efficient synthesis of feature models." In the 16th International Software Product Line Conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2362536.2362553.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

El-Sharkawy, Sascha, Stephan Dederichs, and Klaus Schmid. "From feature models to decision models and back again an analysis based on formal transformations." In the 16th International Software Product Line Conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2362536.2362555.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Pichler, Christian, and Christian Huemer. "Feature modeling for business document models." In the 15th International Software Product Line Conference. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2019136.2019140.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pichler, Christian, Christian Huemer, and Michael Strommer. "Evolution patterns for business document models." In the 15th International Software Product Line Conference. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2019136.2019160.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Quinton, Clément, Daniel Romero, and Laurence Duchien. "Cardinality-based feature models with constraints." In the 17th International Software Product Line Conference. New York, New York, USA: ACM Press, 2013. http://dx.doi.org/10.1145/2491627.2491638.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Cordy, James R. "Submodel pattern extraction for simulink models." In the 17th International Software Product Line Conference. New York, New York, USA: ACM Press, 2013. http://dx.doi.org/10.1145/2491627.2492153.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ryssel, Uwe, Joern Ploennigs, and Klaus Kabitzsch. "Extraction of feature models from formal contexts." In the 15th International Software Product Line Conference. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2019136.2019141.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software Product Line models":

1

McGregor, John D. Testing a Software Product Line. Fort Belvoir, VA: Defense Technical Information Center, December 2001. http://dx.doi.org/10.21236/ada401736.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Jones, Lawrence G., and Albert L. Soule. Software Process Improvement and Product Line Practice: CMMI and the Framework for Software Product Line Practice. Fort Belvoir, VA: Defense Technical Information Center, July 2002. http://dx.doi.org/10.21236/ada403868.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Bergey, John, Sholom Cohen, Lawrence Jones, and Dennis Smith. Software Product Lines: Experiences from the Sixth DoD Software Product Line Workshop. Fort Belvoir, VA: Defense Technical Information Center, March 2004. http://dx.doi.org/10.21236/ada443501.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Bergey, John K., Sholom Cohen, Patrick Donohoe, and Lawrence G. Jones. Software Product Lines: Experiences from the Eighth DoD Software Product Line Workshop. Fort Belvoir, VA: Defense Technical Information Center, December 2005. http://dx.doi.org/10.21236/ada447059.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Bergey, John K., Sholom Cohen, Patrick Donohoe, Matthew J. Fisher, Lawrence G. Jones, and Reed Little. Software Product Lines: Report of the 2009 U.S. Army Software Product Line Workshop. Fort Belvoir, VA: Defense Technical Information Center, April 2009. http://dx.doi.org/10.21236/ada501761.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bergey, John K., Gary Chastek, Sholom Cohen, Patrick Donohoe, Lawrence G. Jones, and Linda Northrop. Software Product Lines: Report of the 2010 US Army Software Product Line Workshop. Fort Belvoir, VA: Defense Technical Information Center, June 2010. http://dx.doi.org/10.21236/ada528683.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Campbell, Grady H., and Jr. A Software Product Line Vision for Defense Acquisition. Fort Belvoir, VA: Defense Technical Information Center, June 2002. http://dx.doi.org/10.21236/ada403810.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Clements, Paul C., and Linda M. Northrop. Salion, Inc.: A Software Product Line Case Study. Fort Belvoir, VA: Defense Technical Information Center, November 2002. http://dx.doi.org/10.21236/ada412311.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Clements, Paul, Sholom Cohen, Patrick Donohoe, and Linda Northrop. Control Channel Toolkit: A Software Product Line Case Study. Fort Belvoir, VA: Defense Technical Information Center, September 2001. http://dx.doi.org/10.21236/ada389097.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Cohen, Sholom, and Robert Krut. Managing Variation in Services in a Software Product Line Context. Fort Belvoir, VA: Defense Technical Information Center, May 2010. http://dx.doi.org/10.21236/ada522574.

Full text
APA, Harvard, Vancouver, ISO, and other styles

To the bibliography