Dissertations / Theses: 'Software product line scoping'

1

SILVA, Ivonei Freitas da. "A scrum-inspired process for software product lines scoping." Universidade Federal de Pernambuco, 2013. https://repositorio.ufpe.br/handle/123456789/12265.

Full text

Abstract:

Scoping in Software Product Lines (SPL) is the first step to identify products, features, and assets in a market segment. Traditional approaches for SPL scoping are heavyweight and upfront processes in scenarios with unpredictable changes and little resources. An incurred key challenge is handling systematically the iterativeness, adaptability, and feedback in the SPL scoping process. As a final consequence, the software industry can hamper investment in the SPL scoping. In this context, the Scrum framework, as the most popular agile approach to foster the iterativeness, adaptability, and feedbacks, can address that challenge. Previous studies have combined Scrum into some SPL activities with good results. This thesis provides a process, named of RiPLE-SCA, for SPL scoping inspired in the Scrum practices. This process bases on industrial evidence (a case study of a traditional SPL scoping), expert opinion on agile SPL (through a survey), and scientific literature about agile SPL (a systematic mapping). A feasibility study and a cross-case study carried out with two industrial partners indicated that the RiPLE-SCA is practicable and appropriate for an industrial setting as well as fosters iterativeness, adaptability, and feedbacks detecting early obsolete features and changes in domain, requirements, features, and technology. Submitted by João Arthur Martins (joao.arthur@ufpe.br) on 2015-03-12T18:58:41Z No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Made available in DSpace on 2015-03-12T18:58:41Z (GMT). No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2013-10-29 CNPq A atividade de escopo em linhas de produto de software é o primeiro passo para identificar produtos, características e ativos de software em um segmento de mercado. As abordagens tradicionais para escopo de linhas de produto de software são processos densos e abrangentes em cenários com mudanças imprevisíveis e com poucos recursos. Um desafio chave nesse cenário é o gerenciamento sistemático da iteratividade, adaptabilidade e do feedback no processo de escopo de linhas de produto de software. Como último efeito, a indústria de software pode restringir investimentos no processo de escopo. Neste contexto, o framework Scrum, abordagem mais popular para incentivar a iteratividade, a adaptabilidade e o feedback, pode lidar com esse desafio. Estudos anteriores têm combinado Scrum com algumas atividades de linhas de produto de software obtendo bons resultados. Esta tese define um processo, denominado de RiPLE-ASC, para o escopo da linha de produtos de software inspirado nas práticas do Scrum. Este processo basea-se nas evidências da indústria (um estudo de caso real de escopo de linhas de produto usando uma abordagem tradicional), na opinião de especialistas em linhas de produto de software ágeis (através de um survey) e na literatura científica sobre linhas de produto de software ágeis (uma mapeamento sistemático). Um estudo de viabilidade e um estudo de caso “cross-case” executados com dois parceiros industriais de nosso grupo de pesquisa indicaram que o RiPLE-ASC tem aplicação prática e adequa-se em um ambiente de produção de software industrial bem como incentiva a iteratividade, adaptabilidade e o feedback detectando cedo características obsoletas e mudanças no domínio, requisitos, características e tecnologia

APA, Harvard, Vancouver, ISO, and other styles

2

Kollu, Ravichandra Kumar. "Requirements scoping outside product lines : Systematic Literature Review and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-11766.

Full text

Abstract:

Context: Scoping is admitted as a key activity in Market Driven Software Development for handling the constant inflow of requirements. It helps in identifying the features, domains and products which help for gaining economic benefits in Software Product Line (SPL) development. Beyond SPL, managing the scope of the project is a major risk for project management. Continuously changing scope creates a congestion state to handle the requirements inflow which causes negative consequences like scope scrap and scope creep. However, for managing negative consequences caused due to requirements volatility depicts a need for work on requirements scoping outside the product line. Objectives: In this study, an exploratory work is carried to identify the literature and industrial perspectives on requirements scoping outside the product line. The main objectives are: Identifying the state of literature of requirements scoping outside product line and variability analysis. To explore the industrial practice on requirements scoping. Suggesting recommendations in improving the scoping process based on the literature and survey. Methods: Systematic Literature Review (SLR) using snowballing procedure was conducted to identify the literature available on requirements scoping outside the product line. Quality assessment using rigor and relevance was performed to find the trustworthiness of the papers obtained through SLR. The data obtained through SLR was analyzed using narrative analysis. Furthermore, an industrial survey was performed using web questionnaire to identify the industrial perspective on requirements scoping. Statistical analysis was performed for analyzing the data obtained from survey. Results: 23 relevant papers were identified through SLR. The results were categorized as definitions obtained, phenomena, challenges and methods/tools identified. From the finding of SLR, an industrial survey was conducted, which has obtained 93 responses. The challenges that were identified through literature were validated through survey and are prioritized. Moreover, the study identified additional challenges that are not discussed in the literature. Additionally, the approaches followed in organizations while scoping the requirements were identified through the survey. Conclusions: This study identified that scope creep is the most frequently occurring phenomenon that organizations are facing throughout the lifecycle of the project. In addition project delays, quality issues and project cost were identified as the most occurring scoping associated challenges. Moreover, scoping activity was identified as the continuous activity which changes significantly throughout the lifecycle. Finally, suggestions were given for improving the scoping process.

APA, Harvard, Vancouver, ISO, and other styles

3

Moraes, Marcela Balbino Santos de. "RiPLE-SC: na agile scoping process for software product lines." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2322.

Full text

Abstract:

Made available in DSpace on 2014-06-12T15:56:44Z (GMT). No. of bitstreams: 2 arquivo2982_1.pdf: 2135820 bytes, checksum: df75cf5b4604b648bc295b0acd5b0db0 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010 Fundação de Amparo à Ciência e Tecnologia do Estado de Pernambuco As constantes mudanças e a busca por novos benefícios na indústria de software possibilitam o surgimento de novas áreas de pesquisa. Neste contexto, uma tendência que tem apresentado importantes benefícios é a área de desenvolvimento ágil de linhas de produtos de software. Linhas de produtos de software é uma importante estratégia de reuso para minimizar custos e tempo de entrega das aplicações, além de maximizar a qualidade e a produtividade do desenvolvimento de software. Entretanto, desenvolver linhas de produtos requer esforços e custos iniciais para apresentar resultados significativos, uma vez que envolve planejamento sistemático, gerenciamento de pontos comuns e variáveis dos produtos e design flexível e detalhado, aspectos que aumentam sua complexidade. Por outro lado, a abordagem ágil apresenta como foco o código e tem seu desenvolvimento realizado de forma iterativa. Além disso, esta metodologia encoraja práticas e valores como comunicação face a face, pequenas iterações, planejamento e design simples e incremental. Comparando linhas de produtos de software e métodos ágeis, diferentes aspectos são identificados. No entanto, pesquisas recentes mostram similaridades entre elas, como: aumento de qualidade e produtividade no desenvolvimento de software e redução de custos e tempo de entrega das aplicações. Portanto, visando diminuir custos e esforços iniciais necessários para adoção de uma linha de produtos de software, este trabalho propõe um processo de escopo ágil para linhas de produtos de software, unindo os benefícios das duas abordagens. O processo proposto é avaliado através de um estudo de caso industrial

APA, Harvard, Vancouver, ISO, and other styles

4

Medeiros, Thiago Fernandes Lins de. "CodeScoping: A source code based tool to software product lines scoping." Universidade Federal de Pernambuco, 2011. https://repositorio.ufpe.br/handle/123456789/2827.

Full text

Abstract:

Made available in DSpace on 2014-06-12T16:01:25Z (GMT). No. of bitstreams: 2 arquivo8976_1.pdf: 2350079 bytes, checksum: 1eef40b33c036ecc8b5b613b08bff0a7 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2011 Engenharia de Linhas de Produto de Software (ELPS) emergiu rapidamente como uma importante abordagem de desenvolvimento de software durantes os últimos anos. ELPS foca-se na identificação e gerenciamento dos pontos em comum (commonalities) e dos pontos de variação (variabilities) de um conjunto de produtos de software, de forma que artefatos (core assets) possam ser desenvolvidos e (re)usados para construir diferentes produtos com custo reduzido. Além disso, melhoria de produtividade, aumento de qualidade e redução do tempo de entrega dos produtos são alguns dos benefícios proporcionados pela abordagem. Neste contexto, o processo de escopo em linhas de produto de software é responsável pela definição da viabilidade a longo prazo da linha de produtos. Seu principal objetivo é identificar e delimitar produtos, funcionalidades, subdomínios e artefatos (componentes, documentos, etc.) existentes da linha de produtos, onde o investimento em reuso trará benefícios econômicos para a empresa. Normalmente, engenheiros de linha de produtos definem o escopo com informações extraídas da documentação de produtos existentes e baseados no conhecimento de especialistas de domínio. Esta é uma tarefa que demanda muito esforço, pois muito tempo é investido na realização de workshops e entrevistas com os especialistas de domínio. Além disso, frequentemente, os especialistas de domínio não tem tempo disponível para compartilhar o conhecimento deles e a documentação dos produtos existentes é inexistente ou está desatualizada. Assim, a fim de reduzir custos e tempo para a realização do processo de escopo, esta dissertação propõe uma abordagem para auxiliar o processo de escopo baseada no código fonte dos produtos já existentes na empresa. Além disso, são apresentados os requisitos, projeto e implementação de uma ferramenta com o objetivo de guiar os analistas de escopo na identificação de similaridades e variações no código fonte dos sistemas legados. Finalmente, esta dissertação também descreve um estudo empírico que foi utilizado para a elicitação de requisitos e um experimento que foi conduzido para avaliar a viabilidade da ferramenta proposta neste trabalho

APA, Harvard, Vancouver, ISO, and other styles

5

Müller, Johannes. "Wertbasierte Portfolio-Optimierung bei Software-Produktlinien." Doctoral thesis, Universitätsbibliothek Leipzig, 2012. http://nbn-resolving.de/urn:nbn:de:bsz:15-qucosa-83047.

Full text

Abstract:

Das Software Product Line Engineering (SPLE) ist ein ganzheitlicher Ansatz zur Entwicklung und Vermarktung von Software-Produktlinien auf Basis von Software-Systemfamilien. Eine in frühen Phasen des SPLE durchzuführende Aktivität ist das Scoping, bei dem die zu realisierenden Produkte mit den zwischen ihnen bestehenden Wiederverwendungspotentialen identifiziert werden. Bei der Durchführung des Scopings steht der Produkt-Manager vor dem Problem einen Ausgleich zwischen den Bedürfnissen der Kunden und dem Aufwand der Entwicklung zu finden. Durch die bestehenden Wiederverwendungspotentiale bei Software-Systemfamilien wird die Entscheidung zusätzlich erschwert. Aufgrund der bestehenden Komplexität der Entscheidung, wird in Literatur und Praxis eine Unterstützung in Form einer statistisch-mathematischen Optimierung gefordert. Dieser Forderung nimmt sich die vorliegende Arbeit an. In ihr werden mit der Konstruktion eines Modells gewinnbeeinflussender Faktoren, einer Methode zur wertbasierten Portfolio-Optimierung und eines Prototyps zur Unterstützung der wertbasierten Portfolio-Optimierung und der anschließenden Evaluation dieser Artefakte zwei Fragen adressiert. Erstens wird geprüft, ob die Optimierung von Produkt-Portfolios bei Software-Produktlinien mit statistisch-mathematischen Verfahren unterstützt werden kann. Zweitens wird geprüft, ob die statistisch-mathematische Optimierung von Produkt-Portfolios eine akzeptierte Unterstützung von Software-Anbietern sein kann. Die Arbeit ordnet sich mit ihren Fragen in die Forschung zum Produkt-Management bei Software-Produktlinien ein und trägt die vorgenannten Artefakte bei.

APA, Harvard, Vancouver, ISO, and other styles

6

JUNIOR, CARLOS ROBERTO MARQUES. "COLLABORATIVE CONFIGURATION OF SOFTWARE PRODUCT LINE." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2011. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=18370@1.

Full text

Abstract:

COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR A configuração de produto é uma atividade chave para permitir a customização em massa. Ela corresponde a produção de um sistema computacional a partir de uma linha de produtos de software, respeitando as necessidades individuais dos clientes. Na prática, a atividade de configuração do produto pode se tornar uma tarefa complexa, principalmente porque envolve várias partes interessadas com diferentes competências para tomar decisões. Vários trabalhos proprõem decompor a atividade de configuração em estágios pré-estabelecidos, atravrés dos quais os interessados podem tomar suas decisões de forma separada e coerente. No entanto, quando há uma descentralização geográfica do conhecimento necessário em cada etapa e/ou quando os requisitos do cliente forem imprecisos e mudarem com frequência, essas soluções propostas não se aplicam. Para resolver essas questões, este trabalho proprõe uma abordagem de configuração dinâmica e colaborativa de produtos com base na metáfora de assistência pessoal. Os assistentes pessoais num ambiente cooperativo coordenam as decisões dos stakeholders e pró-ativamente executam tarefas, tais como o raciocínio sobre as implicaçõoes das decisões, integrando as decisões distribuídas e resolvendo os requisitos divergentes. Uma ferramenta protótipo, chamada Libertas, e dois cenários ilustrativos que avaliam a aplicabilidade da nossa abordagem também são apresentados. O primeiro cenário analisa o processo de configuração para configurar um sistema operacional para suportar os requisitos de negócio de uma empresa. O segundo aborda um cen´ario com uma linha de produtos de software para portais web. Product configuration is a key activity for enabling mass customization. It corresponds to tailoring a software application from a software product line, respecting individual customer requirements. In practice, the product configuration activity is challenging, mainly because it involves numerous stakeholders with different expertise making decisions. Several works claim to decompose the configuration activity into pre-arranged stages, whereby stakeholders can make their decisions in a separated way and coherent fashion. However, due to the decentralization in geography of the knowledge required in each stage and that customer requirements could be imprecise and change frequently, the proposed solutions do not apply. To address these issues, this work proposes a dynamic and collaborative product configuration approach based on the personal assistant metaphor. Personal assistants in a cooperative way coordinate stakeholders´ decisions and proactively perform tasks, such as reasoning about the ramifications of decisions, integrating distributed decisions and resolving divergent requirements. A tool prototype, called Libertas, and two case studies that evaluate the applicability of our approach are also presented. The first case study analyzes the configuration process to configure an operational system to support the business requirements of an enterprise. The second one addresses a scenario of a software product line for web portals.

APA, Harvard, Vancouver, ISO, and other styles

7

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

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

8

Santiago, Ferreira Felype. "MAKING SOFTWARE PRODUCT LINE EVOLUTION SAFER." Universidade Federal de Pernambuco, 2012. https://repositorio.ufpe.br/handle/123456789/2852.

Full text

Abstract:

Made available in DSpace on 2014-06-12T16:01:35Z (GMT). No. of bitstreams: 1 license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2012 Coordenação de Aperfeiçoamento de Pessoal de Nível Superior Desenvolvedores evoluem linhas de produtos de software (LPSs) manualmente ou usando Ferramentas típicas de refatoração de programas. No entanto, quando a evolução de uma Linha de produtos é feita para introduzir novas características, ou para melhorar o seu projeto, é importante ter a certeza de que o comportamento dos produtos existentes não é modificado. Programas típicos de refatoração de software não podem garantir isso porque o contexto de LPS vai além de código, e outros tipos de artefatos de código, e envolve artefatos adicionais, tais como modelos de feature e configuration knowledge. Além disso, em uma LPS, normalmente temos que lidar com um conjunto de possíveis artefatos de código-fonte alternativos que não constitui um programa bem formado. Como resultado, mudanças manuais e ferramentas de refatoração de software existentes podem introduzir mudanças comportamentais ou invalidar configurações de produtos existentes. Para evitar isso, propomos abordagens e implementamos ferramentas para tornar a evolução de linhas de produtos mais segura; essas ferramentas verificam se transformações em LPS são refinamentos no sentido de que preservam o comportamento dos produtos originais da LPS. Elas implementam aproximações diferentes e práticas de uma definição formal de refinamento de LPS. Avaliamos as abordagens em cenários concretos de evolução de LPS, onde o comportamento do produto existente deve ser preservado. No entanto, nossas ferramentas constataram que algumas transformações introduziram mudanças comportamentais. Além disso, avaliamos refinamentos defeituosos, e o conjunto de ferramentas detectou as mudanças de comportamento.

APA, Harvard, Vancouver, ISO, and other styles

9

Hanssen, Geir Kjetil. "From Agile Software Product Line Engineering Towards Software Ecosystems." Doctoral thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2010. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-11890.

Full text

Abstract:

Development and evolution of software products is a challenging endeavor and a significant subfield of software engineering. One of the commonly applied approaches to control and manage this process is software product line engineering (SPLE). There exist a few process frameworks where the development of lines of related software products is basically a sum of two processes: the development of reusable assets and the rapid construction of software applications using predeveloped assets. Agile software development (ASD) is another major paradigm, which also has been widely adopted by the industry over the past decade. SPLE and ASD seek to achieve the same goal i.e. rapid and efficient construction of software. However, the former emphasizes extensive up-front investment in the development of assets for later re-use in contrast to ASD, which emphasizes a reactive approach, avoiding up-front planning and development Even though these two approaches may seem to oppose each other, the industry has lately showed great interest in combining them both, aiming to cover the weaknesses of the one with the strengths of the other. In combination with the overall shift in the software industry from closed systems mindset towards open systems, the uptake of some ASD principles (for example active customer engagement, incremental and iterative development, and open information flows) in product line organizations may contribute to the emergence of more flexible software ecosystems. This thesis presents a longitudinal study of a software product line organization, which has adopted an adapted ASD methodology in an SPLE context and to a large extent has successful in gaining benefits from both approaches, developing towards more open yet controlled processes. Data have been collected over a period of approximately five years following the progression from a strictly waterfall oriented approach, via the adoption of the agile method Evo, up to the current combined agile software product line engineering approach. The following research questions have been addressed in this thesis: RQ1: How can software product line engineering and agile software development be combined? RQ2: How does a software ecosystem shape? The main contributions of this work are: C 1. Through a longitudinal study of a software product line organization we provide detailed insight into an industrial case and how they have changed over time. C 2. We have illustrated some of the details of how SPLE and ASD can be combined in practical terms. We describe the current organization, their product line and their agile software product line engineering process. C 3. We have illustrated how the incorporation of some of the central agile principles has enabled a closer cooperation with external actors. C 4. We have explained the emergence and mode of operation of a software ecosystem, and provided a conceptual model of software ecosystems based on our findings. C 5. We have proposed a theory of software ecosystems, rooted in socio-technical theory and the concept of organizational ecology.

APA, Harvard, Vancouver, ISO, and other styles

10

Addy, Edward A. "Verification and validation in software product line engineering." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1068.

Full text

Abstract:

Thesis (Ph. D.)--West Virginia University, 1999. Title from document title page. Document formatted into pages; contains vi, 75 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 35-39).

APA, Harvard, Vancouver, ISO, and other styles

11

Holmes, Christopher Kenneth. "Generative modelling with software product line architectures." Thesis, University of York, 2007. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.503324.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Parisi, Luca. "A Knowledge Flow as a Software Product Line." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2016. http://amslaurea.unibo.it/12217/.

Full text

Abstract:

Costruire un "data mining workflow" dipende almendo dal dataset e dagli obiettivi degli utenti. Questo processo è complesso a causa dell'elevato numero di algoritmi disponibili e della difficoltà nel scegliere il migliore algoritmo, opportunamente parametrizzato. Di solito, i data scientists usano tools di analisi per decidere quale algoritmo ha le migliori performance nel loro specifico dataset, confrontando le performance fra i diversi algoritmi. Lo scopo di questo progetto è mettere le basi a un sistema software che porta verso la giusta direzione la costruzione di tali workflow, per trovare il migliore a seconda del dataset degli utenti e dei loro obiettivi.

APA, Harvard, Vancouver, ISO, and other styles

13

Rahman, Asim. "Metrics for the Structural Assessment of Product Line Architecture." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3427.

Full text

Abstract:

The notion of maximizing software reuse among the family of products has gained considerable attention in the last decade. Lots of research has been done on designing and managing the commonalities and variabilities between the products. However, very few metrics have been developed to assist architects in designing product line architectures. The structure of the product line holds immense importance towards increasing the life span of the product line. Since many of the product line architecture design methodologies follow a component based approach, it seems logical to attempt to adapt the component based metrics to the product line domain. In this thesis, we attempt to derive metrics that quantify the structural quality of product line architecture. +92-42-5727639

APA, Harvard, Vancouver, ISO, and other styles

14

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

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

APA, Harvard, Vancouver, ISO, and other styles

15

Eriksson, Magnus. "An approach to software product line use case modeling." Licentiate thesis, Umeå University, Computing Science, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-676.

Full text

Abstract:

Organizations developing software intensive defense systems are today faced with a number challenges related to characteristics of both the market place and the system domain:1. Systems grow ever more complex, consisting of tightly integrated mechanical, electrical/electronic and software components.2. Systems are often developed in short series; ranging from only a few to a few hundred units.3. Systems have very long life spans, typically 30 years or longer.4. Systems are developed with high commonality between different customers; however systems are always customized for specific needs.The goal of the research presented in this thesis is to investigate methods and tools to enable efficient development and maintenance of systems in such a context. The strategy adopted in this work is to utilize the forth system characteristic, high commonality, to achieve this.One approach to software reuse, which could be a potential solution as it enables reuse of common parts but at the same time allow for variations, is known as software product line development. The basic idea of this approach is to use domain knowledge to identify common parts within a family of related products and to separate them from the differences between the products. The commonalties are then used to create a product platform that can be used as a common baseline for all products within such a product family.The main contribution of this licentiate thesis is a product line use case modeling approach tailored towards organizations developing software intensive defense systems. We describe how a common and complete use case model can be developed and maintained for a whole family of products, and how the variations within such a family are modeled using a feature model. Concrete use case models, for particular products within a family, can then be generated by selecting features from a feature model. We furthermore describe extensions to the commercial requirements management tool Telelogic DOORS and the UML modeling tool IBM-Rational Rose to support the proposed approach.The approach was applied and evaluated in an industrial case study in the target domain. Based on the collected case study data we draw the conclusion that the approach performs better than modeling according to the styles and guidelines specified by the IBM-Rational Unified Process (RUP) in the current industrial context. The results however also indicate that for the approach to be successfully applied, stronger configuration management and product planning functions than traditionally found in RUP projects are needed.

APA, Harvard, Vancouver, ISO, and other styles

16

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

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.

APA, Harvard, Vancouver, ISO, and other styles

17

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

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.

APA, Harvard, Vancouver, ISO, and other styles

18

Tzeremes, Vasilios. "End user software product line support for smart spaces." Thesis, George Mason University, 2017. http://pqdtopen.proquest.com/#viewpdf?dispub=10249280.

Full text

Abstract:

Smart spaces are physical environments equipped with pervasive technology that sense and react to human activities and changes in the environment. End User Development (EUD) skills vary significantly among end users who want to design, develop and deploy software applications for their smart spaces. Typical end user development is opportunistic, requirements are usually unplanned and undocumented, applications are simplistic in nature, design is ad-hoc, reuse is limited, and software testing is typically haphazard, leading to many quality issues. On the other hand, technical end users with advanced EUD skills and domain expertise have the ability to create sophisticated software applications for smart spaces that are well designed and tested. This research presents a systematic approach for adopting reuse in end user development for smart spaces by using Software Product Line (SPL) concepts. End User (EU) SPL Designers (who are technical end users and domain experts) design and develop EU SPLs for smart spaces whereas less technical end users derive their individual smart space applications from these SPLs. Incorporating SPL concepts in EUD for smart spaces makes it easier for novice end users to derive applications for their spaces without having to interface directly with devices, networks, programming logic, etc. End users only have to select and configure the EU SPL features needed for their space. Another benefit of this approach is that it promotes reuse. End user requirements are mapped to product line features that are realized by common, optional, and variant components available in smart spaces. Product line features and the corresponding component product line architecture can then be used to derive EU applications. Derived EU applications can then be deployed to different smart spaces, thereby avoiding end users having to create EU applications from scratch. Finally the proposed approach has the potential of improving software quality since testing will be an integral part of EU SPL process. In particular, this research has: (a) defined a systematic approach for EU SPL Designers to design and develop EU SPLs, (b) provided an EU SPL application derivation approach to enable end users to derive software applications for their spaces, (c) designed an EU SPL meta-model to capture the underlying representation of EU SPL and derived application artifacts in terms of meta-classes and relationships that supports different EUD platforms, (d) designed and implemented an EUD development environment that supports EU SPL development and application derivation, and (e) provided a testing approach and framework for systematic testing of EU SPLs and derived applications.

APA, Harvard, Vancouver, ISO, and other styles

19

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

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.

APA, Harvard, Vancouver, ISO, and other styles

20

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

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

APA, Harvard, Vancouver, ISO, and other styles

21

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

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.

APA, Harvard, Vancouver, ISO, and other styles

22

Knieke, Christoph [Verfasser]. "Managed Evolution of Automotive Software Product Line Architectures / Christoph Knieke." München : Verlag Dr. Hut, 2019. http://d-nb.info/1198542608/34.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Arriel, Juliana [Verfasser]. "Personalized recommender systems for software product line configurations / Juliana Arriel." Magdeburg : Universitätsbibliothek, 2018. http://d-nb.info/1164498398/34.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Hoxha, Armend. "Generating Members of a Software Product Line Using Combinatory Logic." Digital WPI, 2015. https://digitalcommons.wpi.edu/etd-theses/727.

Full text

Abstract:

A Product Line Family contains similar applications that differ only in the sets of sup-ported features from the family. To properly engineer these product lines, programmers design a common code base used by all members of the product line. The structure of this common code base is often an Object-Oriented (OO) framework, designed to contain the detailed domain-specific knowledge needed to implement these applications. However, these frameworks are often quite complex and implement detailed dynamic behavior with complex coordination among their classes. Extending an OO framework to realize a single product line instance is a unique exercise in OO programming. The ultimate goal is to develop a consistent approach, for managing all instances, which relies on configuration rather than programming. In this thesis, we show the novel application of Combinatory Logic to automatically syn-thesize correct product line members using higher-level code fragments specified by means of combinators. Using the same starting point of an OO framework, we show how to design a repository of combinators using FeatureIDE, an extensible framework for Feature-Oriented Software Development. We demonstrate a proof of concept using two different Java-based frameworks: a card solitaire framework and a multi-objective optimization algorithms framework. These case studies rely on LaunchPad, an Eclipse plugin developed at WPI that extends FeatureIDE. The broader impact of this work is that it enables framework designers to formally en-code the complex functional structure of an OO framework. Once this task is accomplished, then, generating product line instances becomes primarily a configuration process, which enables correct code to be generated by construction based on the combinatory logic.

APA, Harvard, Vancouver, ISO, and other styles

25

Andrade, Hugo. "Software Product Line Architectures: Reviewing the Literature and Identifying Bad Smells." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-21678.

Full text

Abstract:

The Software Product Line (SPL) paradigm has proven to be an effective way to achieve large scale reuse in different domains. It takes advantage of common aspects between different products, while also considering product specific features. The architecture plays an important role in SPL engineering, by providing means to better understand and maintain the product-derivation environment. However, it is difficult to evolve such architecture because it is not always clear where and how to refactor. The contribution of this thesis is twofold. First, the current state of the art of software Product Line Architectures (PLAs) is investigated through a systematic mapping study. It provides an overview of the field through the analysis, and categorization of evidence. The study identifies gaps, trends and provides future directions for research. Furthermore, this thesis addresses the phenomenon of architectural bad smells in the context of SPLs. A case study provides an investigation on the implications of such structural properties in a variability-based environment. Prior to the search for smells, the architecture of a sample SPL in the text editor domain is recovered from the source code. Software Product Line (SPL) paradigmet har bevisat sig vara ett effektivt sätt att uppnå storskalig återanvändning i olika domäner. Den drar nytta av gemensamma aspekter mellan olika produkter, och överväger samtidigt även produktspecifika egenskaper. Arkitekturen spelar en viktig roll i SPL tekniken, genom att tillhandahålla medel för att bättre förstå och underhålla "product-derivation" miljön. Det är dock svårt att vidareutveckla sådan arkitektur för att det inte alltid är tydligt var och hur den kan omstruktureras. Bidraget från denna avhandling är tvåfaldigt. För det första, den aktuella situationen för "software Product Line Architectures" (PLAs) undersöks genom en systematisk kartläggning. Den ger en översikt av fältet genom analys, och kategorisering av bevis. Studien identifierar luckor, trender och ger framtida riktlinjer för forskning. Vidare adresserar denna avhandling fenomenet arkitektoniska "bad smells" inom kontexten för SPLs. En fallstudie ger en utredning av implikationer av sådana strukturella egenskaper i en variabilitet-baserad miljö. Innan sökningen av "smells", är arkitekturen från en sampel SPL i textredigerar domänen återvunnen från källkoden.

APA, Harvard, Vancouver, ISO, and other styles

26

Medeiros, Flávio Mota. "SOPLE-DE: an approach to design service-oriented product line architectures." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2416.

Full text

Abstract:

Made available in DSpace on 2014-06-12T15:58:03Z (GMT). No. of bitstreams: 2 arquivo3244_1.pdf: 2061206 bytes, checksum: d9bbab1debda0a2122b877cceb8484ed (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010 Conselho Nacional de Desenvolvimento Científico e Tecnológico O reuso de software é um fator extremamente importante para empresas interessadas em aumentar sua produtividade, diminuir os custos e o tempo durante o desenvolvimento de sistemas e melhorar a qualidade de seus produtos e serviços. Nesse contexto, Linhas de Produto de Software (LPS) e Arquitetura Orientada a Serviços (SOA) são duas estratégias que estão atualmente recebendo uma grande atenção, tanto na área acadêmica quanto na indústria de software. Os conceitos de linhas de produto e arquitetura orientada a serviços compartilham alguns objetivos e características que podem ser usados em conjunto para aumentar as taxas de reuso de software. No entanto, para o resultado dessa junção ser otimizado, é necessário utilizar um processo de desenvolvimento bem definido. Caso contrário, a equipe de desenvolvimento poderá produzir software de maneira não sistemática, aumentando as chances de falha, o tempo e o custo de desenvolvimento. Com essa visão, esse trabalho apresenta uma abordagem para o projeto de arquiteturas para linhas de produto orientada a serviços, constituída de um conjunto de atividades e sub atividades com entradas e saídas especificadas, sendo cada uma delas realizada por um conjunto predefinido de papéis com responsabilidades definidas. Essa abordagem visa ajudar arquitetos de software a projetar arquitetura orientada a serviços para domínios específicos. Para garantir a qualidade da abordagem desenvolvida, uma pesquisa extensiva foi realizada para analisar o atual estado da arte de processos para o desenvolvimento orientado a serviços. Foram então considerados os pontos fracos e fortes dos processos estudados com o intuito de identificar e preencher as lacunas neles existentes. Por fim, essa abordagem foi validada e refinada por meio de um estudo acadêmico experimental preliminar

APA, Harvard, Vancouver, ISO, and other styles

27

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

28

Rodrigues, Elder de Macedo. "Plets : a product line of model-based testing tools." Pontifícia Universidade Católica do Rio Grande do Sul, 2013. http://hdl.handle.net/10923/5577.

Full text

Abstract:

Made available in DSpace on 2013-12-11T01:01:35Z (GMT). No. of bitstreams: 1 000452835-Texto+Completo-0.pdf: 8269470 bytes, checksum: ab1e0cb4a21fcf269f8e7ac4dc9418f2 (MD5) Previous issue date: 2013 Software testing is recognized as a fundamental activity for assuring software quality. Furthermore, testing is also recognized as one of the most time consuming and expensive activities of software development process. A diversity of testing tools has been developed to support this activity, including tools for Model-based Testing (MBT). MBT is a testing technique to automate the generation of testing artifacts from the system model. This technique presents several advantages, such as, lower cost and less effort to generate test cases. Therefore, in the last years a diversity of commercial, academic, and open source tools to support MBT has been developed to better explore these advantages. In spite of the diversity of tools to support MBT, most of them have been individually and independently developed from scratch based on a single architecture. Thus, they face difficulties of integration, evolution, maintenance, and reuse. In another perspective, Software Product Lines (SPL) offers possibility of systematically generating software products at lower costs, in shorter time, and with higher quality. The main contribution of this Ph. D thesis is to present a SPL for testing tools that support MBT (PLeTs) and an automated environment to support the generation of these tools (PlugSPL). Furthermore, our strategy was initially applied to generate some MBT testing tools which were applied in two examples of use performed in collaboration of an IT company. Based on the feedback from the examples of use we can infer that SPL can be considered a relevant approach to improve productivity and reuse during generation of MBT testing tools. Moreover, we also performed an experimental study carried out to evaluate the effort to use an MBT tool derived from our SPL to generate test scripts and scenarios. Thus, the results point out that the effort to generate test scripts, when compared with a Capture and Replay based tool, was reduced considerably. O teste de software é uma atividade fundamental para garantir a qualidade de software. Além disso, teste de software é uma das atividades mais caras e demoradas no processo de desenvolvimento de software. Por esta razão, diversas ferramentas de teste foram desenvolvidas para apoiar esta atividade, incluindo ferramentas para Teste Baseado em Modelos (TBM). TBM é uma técnica de teste para automatizar a geração de artefatos de teste a partir de modelos do sistema. Esta técnica apresenta diversas vantagens, tais como, menor custo e esforço para gerar casos de teste. Por este motivo, nos últimos anos, diversas ferramentas para TBM foram desenvolvidas para melhor explorar essas vantagens. Embora existam diversas ferramentas TBM, a maioria delas tem o seu desenvolvimento baseado em um esforço individual, sem a adoção de técnicas de reuso sistemático e com base em uma única arquitetura, dificultando a integração, evolução, manutenção e reutilização dessas ferramentas. Uma alternativa para mitigar estes problemas é adotar os conceitos de Linhas de Produto de Software (LPS) para desenvolver ferramentas de TBM. LPS possibilitam gerar sistematicamente produtos a custos mais baixos, em menor tempo e com maior qualidade. A principal contribuição desta tese de doutorado é apresentar uma LPS de ferramentas de teste que suportam TBM (PLeTs) e um ambiente automatizado para apoiar a geração dessas ferramentas (PlugSPL). Além disso, esta tese apresenta uma abordagem para gerar ferramentas para TBM, que foram aplicadas em dois exemplos de uso. Com base nos resultados obtidos nos exemplos de uso, podemos inferir que LPS pode ser considerada uma abordagem relevante para melhorar a produtividade e o reuso durante a geração de ferramentas de TBM. Além disso, também foi realizado um estudo experimental com o objetivo de avaliar o esforço para se utilizar uma ferramenta derivada da PLeTs para geração de scripts de teste. Os resultados apontaram que o esforço para gerar scripts de teste foi reduzido consideravelmente, quando comparado com a uma ferramenta de Capture and Replay.

APA, Harvard, Vancouver, ISO, and other styles

29

Munir, Qaiser, and Muhammad Shahid. "Software Product Line:Survey of Tools." Thesis, Linköping University, Department of Computer and Information Science, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-57888.

Full text

Abstract:

software product line is a set of software-intensive systems that share a common, managed set of features satisfying the specificneeds of a particular market segment or mission. The main attractive part of SPL is developing a set of common assets which includes requirements, design, test plans, test cases, reusable software components and other artifacts. Tools for the development of softwareproduct line are very few in number. The purpose of these tools is to support the creation, maintenance and using different versions ofproduct line artifacts. This requires a development environment that supports the management of assets and product development,processes and sharing of assets among different products.The objective of this master thesis is to investigate the available tools which support Software Product Line process and itsdevelopment phases. The work is carried out in two steps, in the first step available Software Product Line tools are explored and a list of tools is prepared, managed and a brief introduction of each tool is presented. The tools are classified into different categoriesaccording to their usage, relation between the tools is established for better organization and understanding. In the second step, two tools Pure::variant and MetaEdit+ are selected and the quality factors such as Usability, Performance, Reliability, MemoryConsumption and Capacity are evaluated.

APA, Harvard, Vancouver, ISO, and other styles

30

Quan, Nguyen. "Distributed Game Environment : A Software Product Line for Education and Research." Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-29077.

Full text

Abstract:

A software product line is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or demand. Software product lines capitalize commonality and manage variation to reduce the time, effort, cost and complexity when creating and maintaining products in a product line. Therefore reusing core assets, software product line can address problems such as cost, time-to-market, quality, complexity of developing and maintaining variants, and need to quickly respond to market’s demands. The development of a software product line is different from conventional software development and in the area of education and research of product line there is a lack of a suitable purposefully designed and developed software product line (SPL) that can be used for educational or research purposes. In this thesis we have developed a software product line for turn-based two players distributed board games environment that can be used for educational and research purposes. The software product line supports dynamic runtime update, including games, chat, and security features, via OSGi framework. Furthermore, it supports remote gameplay via local area network and dynamic runtime activity recovery. We delivered a product configuration tool that is used to derive and configure products from the core assets based on feature selection. We have also modeled the software product line’s features and documented its requirements, architecture and user guides. Furthermore, we performed functional and integration tests of the software product line to ensure that the requirements are met according to the requirements specification prescribed by the stakeholders.

APA, Harvard, Vancouver, ISO, and other styles

31

GOMES, ROBERTA CLAUDINO BARRETO PESSANHA. "A SOFTWARE PRODUCT LINE BASED ON AGENTS FOR PROJECT MANAGEMENT SYSTEMS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2009. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=15976@1.

Full text

Abstract:

O gerenciamento de projetos de software enfrenta diversos desafios que devem ser superados ao longo do desenvolvimento para garantir seu sucesso. Diversas ferramentas e abordagens foram propostas na literatura para auxiliar gerentes de projeto com tais questões. Assim, propõe-se utilizar duas tendências promissoras da engenharia de software pouco exploradas nesse contexto, que consiste em desenvolver uma linha de produto de sistemas de gerenciamento de projetos baseados em agentes. O uso de linhas de produto de software permite derivar sistemas customizados segundo o tamanho do projeto. Entre os benefícios do uso de agentes tem-se a reconfiguração dinâmica do sistema a partir da exploração de suas características, como raciocínio e adaptação. Software project management faces several challenges that must be overcome throughout the development to guarantee its success. Many tools and approaches have been proposed in the literature to help project managers with these issues. Thus, it is proposed to use two promising software engineering trends barely exploited in this context, which consists of the development of a software product line of project management systems based on agents. The use of software product lines allows the derivation of customized systems based on the project size. Among the benefits of using agents it is included the system dynamic reconfiguration from the exploitation of their characteristics, such as reasoning and adaptation.

APA, Harvard, Vancouver, ISO, and other styles

32

Nivoit, Jean-Baptiste (Jean-Baptiste Henri). "Issues in strategic management of large-scale software product line development." Thesis, Massachusetts Institute of Technology, 2013. http://hdl.handle.net/1721.1/90607.

Full text

Abstract:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2013. This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections. Cataloged from student-submitted PDF version of thesis. Includes bibliographical references (pages 159-163). This thesis reflects on the issues and challenges large software product engineering managers face. Software is hard to engineer on a small scale, but at a larger scale, engineering and management tasks are even more difficult. In the context of software product line evolution, the goal of this work is to look at current managing practice, through the lens of Systems Thinking as well as my own experience. We develop a System Dynamics model to operationalize the notions examined here and run a variety of experiments representative of real situations, from which we learn some lessons and recommend policies that engineering leaders may use to manage large-scale software development organizations. During the course of this research, we found that the model developed intuitively matched experiences in the software industry. Product line engineering and tighter deadlines force software producers to require more accurate control of the production capability of their development organization. In the context of many release cycles and multiple simultaneously active releases, we present some findings about scheduling of the workload, which the engineering manager may leverage to make decisions about the allocation of work. The research presented here from the point of view of the producers of software can help other stakeholders in the software ecosystem understand the challenges these organizations face and the reasoning behind choices made by these providers. by Jean-Baptiste Nivoit. S.M. in Engineering and Management

APA, Harvard, Vancouver, ISO, and other styles

33

Kasikci, Baris Can Cengiz. "Variability Modeling In Software Product Lines." Master's thesis, METU, 2009. http://etd.lib.metu.edu.tr/upload/12610888/index.pdf.

Full text

Abstract:

Software product lines provide enhanced means for systematic reuse when constructing systems within a particular domain. In order to achieve this, systems in a product line are expected to have a significant amount of commonality. Variability is what distinguishes these systems from one another and is spread across various product line artifacts. This thesis focuses on modeling and managing product line variability. The concept of concerns is proposed as a means of variability modeling. Another proposal is related to the use of context free grammars to represent product line variability and to guarantee that any application derived according to the variability framework thus defined will be a valid one. This approach is evaluated for an example domain, in the light of novel evaluation criteria that are also introduced in the scope of this thesis.

APA, Harvard, Vancouver, ISO, and other styles

34

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

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.

APA, Harvard, Vancouver, ISO, and other styles

35

Eyal, Salman Hamzeh. "Recovering traceability links between artifacts of software variants in the context of software product line engineering." Thesis, Montpellier 2, 2014. http://www.theses.fr/2014MON20008/document.

Full text

Abstract:

L'ingénierie des lignes de produits logiciels (Software Product Line Engineering-SPLE en Anglais) est une discipline qui met en œuvre des principes de réutilisation pour le développement efficace de familles de produits. Une famille de produits logiciels est un ensemble de logiciels similaires, ayant des fonctionnalités communes, mais néanmoins différents selon divers aspects; nous parlerons des différentes variantes d'un logiciel. L'utilisation d'une ligne de produit permet de développer les nouveaux produits d'une famille plus vite et d'augmenter la qualité de chacun d'eux. Ces avantages sont liés au fait que les éléments communs aux membres d'une même famille (besoin, architecture, code source, etc.) sont réutilisés et adaptés. Créer de toutes pièces une ligne de produits est une tâche difficile, coûteuse et longue. L'idée sous-jacente à ce travail est qu'une ligne de produits peut être créée par la réingénierie de logiciels similaires (de la même famille) existants, qui ont été préalablement développés de manière ad-hoc. Dans ce contexte, la contribution de cette thèse est triple. La première contribution est la proposition d'une approche pour l'identification des liens de traçabilité entre les caractéristiques (features) d'une application et les parties du code source qui les implémentent, et ce pour toutes les variantes d'une application. Ces liens sont utiles pour générer (dériver) de nouveaux logiciels par la sélection de leurs caractéristiques. L'approche proposée est principalement basée sur l'amélioration de la technique conventionnelle de recherche d'information (Information Retrieval –IR en Anglais) et des approches les plus récentes dans ce domaine. Cette amélioration est liée à deux facteurs. Le premier facteur est l'exploitation des informations liées aux éléments communs ou variables des caractéristiques et du code source des produits logiciels analysés. Le deuxième facteur concerne l'exploitation des similarités et des dépendances entre les éléments du code source. Les résultats que nous avons obtenus par expérimentation confirment l'efficacité de notre approche. Dans la deuxième contribution, nous appliquons nos résultats précédents (contribution no 1) à l'analyse d'impact (Change Impact Analysis –CIA en Anglais). Nous proposons un algorithme permettant à un gestionnaire de ligne de produit ou de produit de détecter quelles les caractéristiques (choix de configuration du logiciel) impactées par une modification du code. Cet algorithme améliore les résultats les plus récents dans ce domaine en permettant de mesurer à quel degré la réalisation d'une caractéristique est impactée par une modification. Dans la troisième contribution nous exploitons à nouveau ces liens de traçabilité (contribution No 1) pour proposer une approche permettant de satisfaire deux objectifs. Le premier concerne l'extraction de l'architecture de la ligne de produits. Nous proposons un ensemble d'algorithmes pour identifier les points de variabilité architecturale à travers l'identification des points de variabilité au niveau des caractéristiques. Le deuxième objectif concerne l'identification des liens de traçabilité entre les caractéristiques et les éléments de l'architecture de la ligne de produits. Les résultats de l'expérimentation montre que l'efficacité de notre approche dépend de l'ensemble des configurations de caractéristiques utilisé (disponibles via les variantes de produits analysés) Software Product Line Engineering (SPLE) is a software engineering discipline providing methods to promote systematic software reuse for developing short time-to-market and quality products in a cost-efficient way. SPLE leverages what Software Product Line (SPL) members have in common and manages what varies among them. The idea behind SPLE is to builds core assets consisting of all reusable software artifacts (such as requirements, architecture, components, etc.) that can be leveraged to develop SPL's products in a prescribed way. Creating these core assets is driven by features provided by SPL products.Unfortunately, building SPL core assets from scratch is a costly task and requires a long time which leads to increasing time-to-market and up-front investment. To reduce these costs, existing similar product variants developed by ad-hoc reuse should be re-engineered to build SPLs. In this context, our thesis proposes three contributions. Firstly, we proposed an approach to recover traceability links between features and their implementing source code in a collection of product variants. This helps to understand source code of product variants and facilitate new product derivation from SPL's core assets. The proposed approach is based on Information Retrieval (IR) for recovering such traceability links. In our experimental evaluation, we showed that our approach outperforms the conventional application of IR as well as the most recent and relevant work on the subject. Secondly, we proposed an approach, based on traceability links recovered in the first contribution, to study feature-level Change Impact Analysis (CIA) for changes made to source code of features of product variants. This approach helps to conduct change management from a SPL's manager point of view. This allows him to decide which change strategy should be executed, as there is often more than one change that can solve the same problem. In our experimental evaluation, we proved the effectiveness of our approach in terms of the most used metrics on the subject. Finally, based on traceability recovered in the first contribution, we proposed an approach to contribute for building Software Product Line Architecture (SPLA) and linking its elements with features. Our focus is to identify mandatory components and variation points of components. Therefore, we proposed a set of algorithms to identify this commonality and variability across a given collection of product variants. According to the experimental evaluation, the efficiency of these algorithms mainly depends on the available product configurations

APA, Harvard, Vancouver, ISO, and other styles

36

Gómez, Llana Abel. "MODEL DRIVEN SOFTWARE PRODUCT LINE ENGINEERING: SYSTEM VARIABILITY VIEW AND PROCESS IMPLICATIONS." Doctoral thesis, Universitat Politècnica de València, 2012. http://hdl.handle.net/10251/15075.

Full text

Abstract:

La Ingeniería de Líneas de Productos Software -Software Product Line Engineerings (SPLEs) en inglés- es una técnica de desarrollo de software que busca aplicar los principios de la fabricación industrial para la obtención de aplicaciones informáticas: esto es, una Línea de productos Software -Software Product Line (SPL)- se emplea para producir una familia de productos con características comunes, cuyos miembros, sin embargo, pueden tener características diferenciales. Identificar a priori estas características comunes y diferenciales permite maximizar la reutilización, reduciendo el tiempo y el coste del desarrollo. Describir estas relaciones con la suficiente expresividad se vuelve un aspecto fundamental para conseguir el éxito. La Ingeniería Dirigida por Modelos -Model Driven Engineering (MDE) en inglés- se ha revelado en los últimos años como un paradigma que permite tratar con artefactos software con un alto nivel de abstracción de forma efectiva. Gracias a ello, las SPLs puede aprovecharse en granmedida de los estándares y herramientas que han surgido dentro de la comunidad de MDE. No obstante, aún no se ha conseguido una buena integración entre SPLE y MDE, y como consecuencia, los mecanismos para la gestión de la variabilidad no son suficientemente expresivos. De esta manera, no es posible integrar la variabilidad de forma eficiente en procesos complejos de desarrollo de software donde las diferentes vistas de un sistema, las transformaciones de modelos y la generación de código juegan un papel fundamental. Esta tesis presenta MULTIPLE, un marco de trabajo y una herramienta que persiguen integrar de forma precisa y eficiente los mecanismos de gestión de variabilidad propios de las SPLs dentro de los procesos de MDE. MULTIPLE proporciona lenguajes específicos de dominio para especificar diferentes vistas de los sistemas software. Entre ellas se hace especial hincapié en la vista de variabilidad ya que es determinante para la especificación de SPLs. Gómez Llana, A. (2012). MODEL DRIVEN SOFTWARE PRODUCT LINE ENGINEERING: SYSTEM VARIABILITY VIEW AND PROCESS IMPLICATIONS [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/15075 Palancia

APA, Harvard, Vancouver, ISO, and other styles

37

Haupt, Michael, Stefan Marr, and Robert Hirschfeld. "CSOM/PL : a virtual machine product line." Universität Potsdam, 2011. http://opus.kobv.de/ubp/volltexte/2011/5233/.

Full text

Abstract:

CSOM/PL is a software product line (SPL) derived from applying multi-dimensional separation of concerns (MDSOC) techniques to the domain of high-level language virtual machine (VM) implementations. For CSOM/PL, we modularised CSOM, a Smalltalk VM implemented in C, using VMADL (virtual machine architecture description language). Several features of the original CSOM were encapsulated in VMADL modules and composed in various combinations. In an evaluation of our approach, we show that applying MDSOC and SPL principles to a domain as complex as that of VMs is not only feasible but beneficial, as it improves understandability, maintainability, and configurability of VM implementations without harming performance. CSOM/PL ist eine Softwareproduktfamilie (software product line, SPL), die erstellt wurde, indem Techniken der mehrdimensionalen Belangtrennung (multi-dimensional separation of concerns, MDSOC) auf die Domäne der virtuellen Maschinen (VM) für höhere Programmiersprachen angewendet wurden. Dazu wurde CSOM, eine in C implementierte Smalltalk-VM, mittels VMADL (virtual machine architecture description language) in Module zerlegt. Etliche Eigenschaften von CSOM wurden in VMADL-Module gekapselt und auf unterschiedliche Weisen komponiert. Die Auswertung des Ansatzes zeigt, dass die Anwendung von MDSOC- und SPL-Prinzipien auf die komplexe VM-Domäne nicht nur machbar ist, sondern darüber hinaus auch Vorteile mit sich bringt, da die Verständlichkeit, Wartbarkeit und Konfigurierbarkeit von VM-Implementierungen ohne Beeinträchtigung der Ausführungsgeschwindigkeit verbessert werden.

APA, Harvard, Vancouver, ISO, and other styles

38

Pham, Thi-Kim-Dung. "Development of Correct-by-Construction Software using Product Lines." Thesis, Paris, CNAM, 2017. http://www.theses.fr/2017CNAM1138/document.

Full text

Abstract:

Nous avons commencé la thèse par la littérature d'enquête sur les approches SPLE et CbyC dans l'état de l'art. Sur la base de l'aperçu et des connaissances obtenues, nous avons analysé les problèmes existants et suggéré des moyens de les résoudre pour notre objectif principal. Nous avons proposé dans le chapitre 2 une méthodologie pour développer des lignes de produits afin que les produits générés soient corrects par construction. Notre intention principale est qu'un utilisateur n'a pas besoin de connaître le processus de génération de produit mais peut recevoir un produit final correct en sélectionnant une configuration de fonctionnalité. En utilisant la méthodologie, les produits finaux sont générés automatiquement et leur exactitude est garantie. À la suite de cette proposition, nous sommes passés au chapitre 3 pour définir la langue de FFML qui est utilisé pour l'écriture de modules. Le mécanisme de réutilisation et de modification, défini pour la langue et appliqué à toutes sortes d'artefacts (spécification, code et preuve de précision) réduit l'effort de programmation. Au chapitre 4, nous nous sommes concentrés sur la définition des mécanismes de composition pour la composition des modules FFML et les intégrons à l'outil FFML Product Generator. L'évaluation de notre méthodologie est réalisée par le développement de deux lignes de produits logiciels, le compte bancaire SPL et le SPL de poker, ce dernier étant un peu plus complexe que le premier. Dans l'évaluation, nous avons souligné les avantages et la limitation de notre méthodologie We began the thesis by survey literature on SPLE and CbyC approaches in the State of the Art. Based on the overview and the insights obtained, we have analyzed the existing problems and suggested ways to solve them for our main goal. We have proposed in Chapter 2 a methodology to develop product lines such that the generated products are correct-by-construction. Our main intention is that a user does not need to know the product generation process but can receive a correct final product from selecting a configuration of features. Using the methodology, the final products are generated automatically and their correctness is guaranteed. Following this proposal, we have moved in Chapter 3 to define the FFML language that is used for writing modules. The reuse and modification mechanism, defined for the language and applied to all kinds of artifacts (specification, code and correctness proof), reduce the programming effort. In Chapter 4, we have focused on defining the composition mechanisms for composing FFML modules and embedded them into the FFML Product Generator tool. The evaluation of our methodology is performed through the development of two software product lines, the Bank Account SPL and the Poker SPL, the latter being a bit more complex than the former. In the evaluation, we have highlighted the advantages and the limitation of our methodology

APA, Harvard, Vancouver, ISO, and other styles

39

Gylterud, Snorre. "Practices of Agile Software Product-Line Engineering : A qualitative assessment of empirical studies." Thesis, Norwegian University of Science and Technology, Department of Computer and Information Science, 2009. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9996.

Full text

Abstract:

This thesis elaborated on the how Software Product-Line Engineering is combined with Agile Software Development to improve Software Engineering, through investigating published case studies and performing interviews in several companies. This combination are often described as Agile Software Product-Line Engineering and our study aimed to describe what agility is for software product lines and find out more on how this approach could be realized. Agile Software Product-Line Engineering could reap benefits from the best of the two software engineering approaches combining long term strategic efforts with short term agility. By following a specified research method that combines qualitative research methods we were able to ensure validity in our analysis and generalize the findings of this study. We used both semi-structured interviews and textual analysis techniques. The companies under study seem to combine Software Product-Line Engineering and Agile Software Development with success, reducing initial investment and exploiting reuse, and we found several practices that are interesting for further study. Based on these practices we present our view of a top-down approach to Agile Software Product-Line Engineering starting with several characteristics and a proposal for a definition of the field. Further, a framework for implementing the approach based on our research is presented, before we describe our thoughts on how the practice areas of Software Product-Line Engineering can be combined with Agile Software Development practices. We think that this thesis could be used as a guideline for further study and implementation of Agile Software Product-Lines. We believe that the data we cover is comprehensive based on the small existing research field and covers the general ideas of both the fields included in the combination.

APA, Harvard, Vancouver, ISO, and other styles

40

Gurses, Ozgur. "Non-functional Variability Management By Complementary Quality Modeling In A Software Product Line." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12612571/index.pdf.

Full text

Abstract:

Software product lines provide the opportunity to improve productivity, quality and time-to-market of software-based systems by means of systematic reuse. So as to accomplish systematic software reuse, elicitation of commonality knowledge is to be upheld by the analysis and management of variability knowledge inherent in domain requirements. Considerable effort is devoted to the management of functional variability, often neglecting the impact of quality concerns originating from non-functional requirements. In this thesis, a hybrid approach concentrating on the modeling of quantitative as well as qualitative concerns on quality has been proposed. This approach basically aims to support the domain design process by modeling non-functional variability. It further aims to support application design process by providing trade-off selection ability among quality concerns to control functional features that belong to the same domain. This approach is implemented and evaluated on an example domain to reveal its benefits on non-functional variability.

APA, Harvard, Vancouver, ISO, and other styles

41

Pham, Thi-Kim-Dung. "Development of Correct-by-Construction Software using Product Lines." Electronic Thesis or Diss., Paris, CNAM, 2017. http://www.theses.fr/2017CNAM1138.

Full text

Abstract:

Nous avons commencé la thèse par la littérature d'enquête sur les approches SPLE et CbyC dans l'état de l'art. Sur la base de l'aperçu et des connaissances obtenues, nous avons analysé les problèmes existants et suggéré des moyens de les résoudre pour notre objectif principal. Nous avons proposé dans le chapitre 2 une méthodologie pour développer des lignes de produits afin que les produits générés soient corrects par construction. Notre intention principale est qu'un utilisateur n'a pas besoin de connaître le processus de génération de produit mais peut recevoir un produit final correct en sélectionnant une configuration de fonctionnalité. En utilisant la méthodologie, les produits finaux sont générés automatiquement et leur exactitude est garantie. À la suite de cette proposition, nous sommes passés au chapitre 3 pour définir la langue de FFML qui est utilisé pour l'écriture de modules. Le mécanisme de réutilisation et de modification, défini pour la langue et appliqué à toutes sortes d'artefacts (spécification, code et preuve de précision) réduit l'effort de programmation. Au chapitre 4, nous nous sommes concentrés sur la définition des mécanismes de composition pour la composition des modules FFML et les intégrons à l'outil FFML Product Generator. L'évaluation de notre méthodologie est réalisée par le développement de deux lignes de produits logiciels, le compte bancaire SPL et le SPL de poker, ce dernier étant un peu plus complexe que le premier. Dans l'évaluation, nous avons souligné les avantages et la limitation de notre méthodologie We began the thesis by survey literature on SPLE and CbyC approaches in the State of the Art. Based on the overview and the insights obtained, we have analyzed the existing problems and suggested ways to solve them for our main goal. We have proposed in Chapter 2 a methodology to develop product lines such that the generated products are correct-by-construction. Our main intention is that a user does not need to know the product generation process but can receive a correct final product from selecting a configuration of features. Using the methodology, the final products are generated automatically and their correctness is guaranteed. Following this proposal, we have moved in Chapter 3 to define the FFML language that is used for writing modules. The reuse and modification mechanism, defined for the language and applied to all kinds of artifacts (specification, code and correctness proof), reduce the programming effort. In Chapter 4, we have focused on defining the composition mechanisms for composing FFML modules and embedded them into the FFML Product Generator tool. The evaluation of our methodology is performed through the development of two software product lines, the Bank Account SPL and the Poker SPL, the latter being a bit more complex than the former. In the evaluation, we have highlighted the advantages and the limitation of our methodology

APA, Harvard, Vancouver, ISO, and other styles

42

Oster, Sebastian [Verfasser], Andy [Akademischer Betreuer] Schürr, and Ursula [Akademischer Betreuer] Goltz. "Feature Model-based Software Product Line Testing / Sebastian Oster. Betreuer: Andy Schürr ; Ursula Goltz." Darmstadt : Universitäts- und Landesbibliothek Darmstadt, 2012. http://d-nb.info/1106113845/34.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Nieke, Michael Verfasser], Ina [Akademischer Betreuer] [Schaefer, and Bernhard [Akademischer Betreuer] Rumpe. "Consistent Feature-Model Driven Software Product Line Evolution / Michael Nieke ; Ina Schaefer, Bernhard Rumpe." Braunschweig : Technische Universität Braunschweig, 2021. http://d-nb.info/1229615598/34.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

McEntee, Simon. "The application of intelligent software for on-line product quality monitoring in manufacturing processes." Thesis, Glasgow Caledonian University, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.295005.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Orhan, Umut. "A Knowledge Based Product Line For Semantic Modeling Of Web Service Families." Master's thesis, METU, 2009. http://etd.lib.metu.edu.tr/upload/12610305/index.pdf.

Full text

Abstract:

Some mechanisms to enable an effective transition from domain models to web service descriptions are developed. The introduced domain modeling support provides verification and correction on the customization part. An automated mapping mechanism from the domain model to web service ontologies is also developed. The proposed approach is based on Feature-Oriented Domain Analysis (FODA), Semantic Web technologies and ebXML Business Process Specification Schema (ebBP). Major contributions of this work are the conceptualizations of a feature model for web services and a novel approach for knowledge-based elicitation of domain-specific outcomes in order to allow designing and deploying services better aligned with dynamically changing business goals, stakeholders&#039 concerns and end-users&#039 viewpoints. The main idea behind enabling a knowledge-based approach is to pursue automation and intelligence on reflecting business requirements into service descriptions via model transformations and automated reasoning. The proposed reference variability model encloses the domain-specific knowledge and is formalized by using Web Ontology Language (OWL). Adding formal semantics to feature models allows us to perform automated analysis over them such as the verification of model customizations through exploiting rule-based automated reasoners. This research was motivated due to the needs for achieving productivity gains, maintainability and better alignment of business requirements with technical capabilities in engineering service-oriented applications and systems.

APA, Harvard, Vancouver, ISO, and other styles

46

Björklund, Marcus, and Jonas Hjelmar. "Adopting Software Product Lines : Guidelines based on the Maturity of Organizations." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5196.

Full text

Abstract:

Software Product Lines (SPL) is a relatively new way of working in software development. A SPL is an enforced architecture and a collection of components common for more than one product within a domain. Development using SPL utilizes tools and techniques for creating software systems from a common set of core assets in order to satisfy a certain market. In this study we investigate how to proceed when transitioning to a SPL development approach by evaluating proposed and used adoption approaches, methods and frameworks. We performed a systematic literature review using three main sources; Compendex/Inspec, CiteSeerX and Google Scholar. The results are analyzed using a qualitative analysis technique called Recursive Abstraction where the results are iteratively summarized to extract the essence of the data. A manageable collection of frameworks, methods and approaches are summarized as a starting point for a reader who wants to dig deeper into the subject. A set of guidelines is suggested for companies who are considering a transition to SPL development. We also investigate the link between SPL and organization maturity, with a focus on the benefits of combining a SPL initiative with a CMMI initiative. We conclude that the transition process should not be taken lightly; in most cases it should be made in incremental steps. There is a fairly standard approach to adopt SPL and there are a few frameworks that are commonly accepted. However, we also conclude that most research areas of SPL development lacks in validation. Concerning the link between SPL and CMMI we identify some PA's that are more important when considering SPL development and a few others that may be harder to execute. We conclude that SPL benefits from process maturity and discipline as SPL development is process controlled and a lack in process discipline may cause corrosion of the SPL. A CMMI maturity level of Defined processes should be considered a prerequisite for a complete SPL practice. We could not find any indication that the organization maturity would benefit from SPL practices alone. Neither could we identify any drawbacks of having both an CMMI initiative and SPL transition initiative within the same organization.

APA, Harvard, Vancouver, ISO, and other styles

47

ALMEIDA, Rodrigo Bonifácio de. "Modeling software product line variability in use case scenarios: an approach based on crosscutting mechanisms." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/1805.

Full text

Abstract:

Made available in DSpace on 2014-06-12T15:52:31Z (GMT). No. of bitstreams: 2 arquivo3380_1.pdf: 3662532 bytes, checksum: 7a5c0cdcff383bfae82e49476b58f158 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010 Associação para Promoção da Excelência do Software Brasileiro A Gerência de Variações é um desafio para a adoção de Linhas de Produtos de Software, uma vez que os desenvolvedores precisam de meios para especificar e implementar variações que ocorrem em diferentes tipos de artefatos (como requisitos, projeto e arquitetura, código fonte e casos de testes). Esta tese apresenta uma nova abordagem para gerenciar variações em cenários de casos de uso. Tal abordagem, Modeling Scenario Variabilities as Crosscutting Mechanisms (MSVCM), objetiva melhorar a separação de preocupações entre a representação de variações e as especificações de cenários, possibilitando aos engenheiros do domínio e da aplicação compreender evoluir ambas as preocupações de forma independente. MSVCM alcança tal objetivo graças ao uso extensivo de mecanismos composicionais para a derivação de produtos, idéia motivada pelo fato de que artefatos como modelos de features, configuração de produtos e modelos de conhecimento da configuração se entrecortam em relação aos membros da linha de produtos. Após a avaliação da abordagem proposta, por meio de alguns estudos de casos, identificou-se que MSVCM reduz o espalhamento de features e melhora a coesão das especificações de cenários. Estes resultados sugerem que a evolução das especificações usando a técnica proposta nesta tese requer alterações mais localizadas, quando comparada com outras abordagens existentes. Por outro lado, os resultados de três experimentos controlados apresentaram evidências de que MSVCM apenas reduz o tempo necessário para evoluir as especificações de uma LPS quando os participantes possuem grande familiaridade com a técnica proposta e com o processo de evoluir especificações de linhas de produtos.

APA, Harvard, Vancouver, ISO, and other styles

48

de, Albuquerque Ribeiro Rafael. "Modeling software product line variability in use case scenarios: an approach based on crosscutting mechanisms." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/1814.

Full text

Abstract:

Made available in DSpace on 2014-06-12T15:52:34Z (GMT). No. of bitstreams: 2 arquivo3521_1.pdf: 3662532 bytes, checksum: 7a5c0cdcff383bfae82e49476b58f158 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010 Conselho Nacional de Desenvolvimento Científico e Tecnológico A Gerência de Variações é um desafio para a adoção de Linhas de Produtos de Software, uma vez que os desenvolvedores precisam de meios para especificar e implementar variações que ocorrem em diferentes tipos de artefatos (como requisitos, projeto e arquitetura, código fonte e casos de testes). Esta tese apresenta uma nova abordagem para gerenciar variações em cenários de casos de uso. Tal abordagem, Modeling Scenario Variabilities as Crosscutting Mechanisms (MSVCM), objetiva melhorar a separação de preocupações entre a representação de variações e as especificações de cenários, possibilitando aos engenheiros do domínio e da aplicação compreender evoluir ambas as preocupações de forma independente. MSVCM alcança tal objetivo graças ao uso extensivo de mecanismos composicionais para a derivação de produtos, idéia motivada pelo fato de que artefatos como modelos de features, configuração de produtos e modelos de conhecimento da configuração se entrecortam em relação aos membros da linha de produtos. Após a avaliação da abordagem proposta, por meio de alguns estudos de casos, identificou-se que MSVCM reduz o espalhamento de features e melhora a coesão das especificações de cenários. Estes resultados sugerem que a evolução das especificações usando a técnica proposta nesta tese requer alterações mais localizadas, quando comparada com outras abordagens existentes. Por outro lado, os resultados de três experimentos controlados apresentaram evidências de que MSVCM apenas reduz o tempo necessário para evoluir as especificações de uma LPS quando os participantes possuem grande familiaridade com a técnica proposta e com o processo de evoluir especificações de linhas de produtos

APA, Harvard, Vancouver, ISO, and other styles

49

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

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.

APA, Harvard, Vancouver, ISO, and other styles

50

Di, Cola Simone. "A component-based approach to modelling software product families with explicit variation points." Thesis, University of Manchester, 2017. https://www.research.manchester.ac.uk/portal/en/theses/a-componentbased-approach-to-modelling-software-product-families-with-explicit-variation-points(b649eda2-8cac-46a5-888e-ee0926080ecb).html.

Full text

Abstract:

In software product line engineering, the construction of an architecture for a product family is still an outstanding engineering challenge. In current practice, a framework is used for configuring individual products by combining solution space artefacts into products with specified features according to a feature model. No architectures are created. In contrast, an architecture for a product family would define the architectures for all the products in the family, allowing engineers to reason at a higher level of abstraction. In this thesis, we present a component model that can be used to define architectures for product families, by incorporating explicit variation points.

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Software product line scoping'

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