Academic literature on the topic 'Software product line scoping'

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software product line scoping.'

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

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

Journal articles on the topic "Software product line scoping"

1

John, Isabel. "Using Documentation for Product Line Scoping." IEEE Software 27, no. 3 (2010): 42–47. http://dx.doi.org/10.1109/ms.2010.34.

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

Marchezan, Luciano, Elder Rodrigues, Wesley Klewerton Guez Assunção, Maicon Bernardino, Fábio Paulo Basso, and João Carbonell. "Software product line scoping: A systematic literature review." Journal of Systems and Software 186 (April 2022): 111189. http://dx.doi.org/10.1016/j.jss.2021.111189.

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

LEE, JIHYUN, SUNGWON KANG, and DANHYUNG LEE. "A COMPARISON OF SOFTWARE PRODUCT LINE SCOPING APPROACHES." International Journal of Software Engineering and Knowledge Engineering 20, no. 05 (2010): 637–63. http://dx.doi.org/10.1142/s021819401000489x.

Full text
Abstract:
During the past decade a number of methods and techniques for software product line scoping have been developed. Although their basic goal is the same, when it comes to details it is often hard to see what they have in common, where they differ and what their strengths and weaknesses are. This makes it difficult for the user to decide when and how to use them because these methods and techniques sometimes describe the same concepts and activities with different terminologies and, more often than not, by that the activities and tasks defined in them do not exactly match with each other and their inputs/outcomes are not clearly defined. In this paper, we compare and analyze the mainstream approaches to software product line scoping, deduce their essential components and develop them into a unified approach that can be easily referred to and utilized by the user companies planning to launch product lines.
APA, Harvard, Vancouver, ISO, and other styles
4

Karimpour, Reza, and Guenther Ruhe. "Evolutionary robust optimization for software product line scoping: An explorative study." Computer Languages, Systems & Structures 47 (January 2017): 189–210. http://dx.doi.org/10.1016/j.cl.2016.07.007.

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

da Silva, Ivonei Freitas, Paulo Anselmo da Mota Silveira Neto, Pádraig O’Leary, Eduardo Santana de Almeida, and Silvio Romero de Lemos Meira. "Software product line scoping and requirements engineering in a small and medium-sized enterprise: An industrial case study." Journal of Systems and Software 88 (February 2014): 189–206. http://dx.doi.org/10.1016/j.jss.2013.10.040.

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

Faisal, Sadaf, Devine Samoth, Yusra Aslam, et al. "Key Features of Smart Medication Adherence Products: Updated Scoping Review." JMIR Aging 6 (December 19, 2023): e50990. http://dx.doi.org/10.2196/50990.

Full text
Abstract:
Background Older adults often face challenges in self-managing their medication owing to physical and cognitive limitations, complex medication regimens, and packaging of medications. Emerging smart medication dispensing and adherence products (SMAPs) offer the options of automated dispensing, tracking medication intake in real time, and reminders and notifications. A 2021 review identified 51 SMAPs owing to the rapid influx of digital technology; an update to this review is required. Objective This review aims to identify new products and summarize and compare the key features of SMAPs. Methods Gray and published literature and videos were searched using Google, YouTube, PubMed, Embase, and Scopus. The first 10 pages of Google and the first 100 results of YouTube were screened using 4 and 5 keyword searches, respectively. SMAPs were included if they were able to store and allowed for the dispensation of medications, tracked real-time medication intake data, and could automatically analyze data. Products were excluded if they were stand-alone software applications, not marketed in English, not for in-home use, or only used in clinical trials. In total, 5 researchers independently screened and extracted the data. Results This review identified 114 SMAPs, including 80 (70.2%) marketed and 34 (29.8%) prototypes, grouped into 15 types. Among the marketed products, 68% (54/80) were available for consumer purchase. Of these products, 26% (14/54) were available worldwide and 78% (42/54) were available in North America. There was variability in the hardware, software, data collection and management features, and cost of the products. Examples of hardware features include battery life, medication storage capacity, availability of types and number of alarms, locking features, and additional technology required for use of the product, whereas software features included reminder and notification capabilities and availability of manufacturer support. Data capture methods included the availability of sensors to record the use of the product and data-syncing capabilities with cloud storage with short-range communications. Data were accessible to users via mobile apps or web-based portals. Some SMAPs provided data security assurance with secure log-ins (use of personal identification numbers or facial recognition), whereas other SMAPs provided data through registered email addresses. Although some SMAPs were available at set prices or free of cost to end users, the cost of other products varied based on availability, shipping fees, and subscription fees. Conclusions An expanding market for SMAPs with features specific to at-home patient use is emerging. Health care professionals can use these features to select and suggest products that meet their patients’ unique requirements.
APA, Harvard, Vancouver, ISO, and other styles
7

Pohl, Klaus, and Andreas Metzger. "Software product line testing." Communications of the ACM 49, no. 12 (2006): 78–81. http://dx.doi.org/10.1145/1183236.1183271.

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

Fukaya, Naohiko. "SPL (Software Product Line)." Journal of The Institute of Image Information and Television Engineers 65, no. 7 (2011): 930–32. http://dx.doi.org/10.3169/itej.65.930.

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

Schmid, Klaus, and Eduardo Santana de Almeida. "Product Line Engineering." IEEE Software 30, no. 4 (2013): 24–30. http://dx.doi.org/10.1109/ms.2013.83.

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

Northrop, L. M. "SEI's software product line tenets." IEEE Software 19, no. 4 (2002): 32–40. http://dx.doi.org/10.1109/ms.2002.1020285.

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

Dissertations / Theses on the topic "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.<br>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)<br>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<br>CNPq<br>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<br>Fundação de Amparo à Ciência e Tecnologia do Estado de Pernambuco<br>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<br>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<br>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.<br>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<br>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<br>Coordenação de Aperfeiçoamento de Pessoal de Nível Superior<br>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.<br>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
More sources

Books on the topic "Software product line scoping"

1

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

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

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

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

C, Kang Kyo, Sugumaran Vijayan 1960-, and Park Sooyong, eds. Applied software product-line engineering. Auerbach Publications, 2010.

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

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

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

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

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

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

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

OliveiraJr, Edson, ed. UML-Based Software Product Line Engineering with SMarty. Springer International Publishing, 2023. http://dx.doi.org/10.1007/978-3-031-18556-4.

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

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

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

Bosch, Jan. Design and use of software architectures: Adopting and evolving a product-line approach. Addison-Wesley, 2000.

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

Software, Product Lines Conference (10th 2006 Baltimore Md ). SPLC 2006: 10th International Software Product Line Conference : proceedings : 21-24 August, 2006, Baltimore, Maryland. IEEE Computer Society, 2006.

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

Book chapters on the topic "Software product line scoping"

1

John, Isabel, and Karina Villela. "Evolutionary Product Line Scoping." In Software Product Lines: Going Beyond. Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-15579-6_57.

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

Schmid, Klaus, and Cristina Gacek. "Implementation Issues in Product Line Scoping." In Software Reuse: Advances in Software Reusability. Springer Berlin Heidelberg, 2000. http://dx.doi.org/10.1007/978-3-540-44995-9_11.

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

Schmid, Klaus. "Scoping Software Product Lines." In Software Product Lines. Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-4339-8_27.

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

Lee, Kwangchun, and Dan Hyung Lee. "A Market-Driven Product Line Scoping." In Software Engineering Research,Management and Applications 2011. Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-23202-2_3.

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

Kishi, Tomoji, Natsuko Noda, and Takuya Katayama. "A Method for Product Line Scoping Based on a Decision-Making Framework." In Software Product Lines. Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-45652-x_22.

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

Schmid, Klaus, and Isabel John. "Tutorial on Practical Product Line Scoping and Modeling." In Software Reuse: Methods, Techniques, and Tools. Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-46020-9_32.

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

Schmid, Klaus, and Michael Schank. "PuLSE-BEAT — A Decision Support Tool for Scoping Product Lines." In Software Architectures for Product Families. Springer Berlin Heidelberg, 2000. http://dx.doi.org/10.1007/978-3-540-44542-5_8.

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

Chastek, Gary, and Patrick Donohoe. "Product Line Analysis." In Software Product Lines. Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-28630-1_23.

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

Pronk, B. J. "Medical Product Line Architectures." In Software Architecture. Springer US, 1999. http://dx.doi.org/10.1007/978-0-387-35563-4_20.

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

Niehaus, Elisabeth, Klaus Pohl, and Günter Böckle. "Product Management." In Software Product Line Engineering. Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/3-540-28901-1_9.

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

Conference papers on the topic "Software product line scoping"

1

Marchezan, Luciano, Elder Rodrigues, Wesley K. G. Assunção, Maicon Bernardino, Fábio Paulo Basso, and João Carbonell. "Software product line scoping." In SPLC '22: 26th ACM International Systems and Software Product Line Conference. ACM, 2022. http://dx.doi.org/10.1145/3546932.3547012.

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

Dalgarno, Andrew Mark. "Product Line Scoping in Practice." In 2008 12th International Software Product Line Conference (SPLC). IEEE, 2008. http://dx.doi.org/10.1109/splc.2008.54.

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

da Silva, Ivonei Freitas. "An agile approach for software product lines scoping." In the 16th International Software Product Line Conference. ACM Press, 2012. http://dx.doi.org/10.1145/2364412.2364450.

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

Ojeda, Marta Cecilia Camacho, Mayor del Cauca, Francisco Álvarez Rodriguez, and César A. Collazos. "Identifying collaborative aspects during software product lines scoping." In the 23rd International Systems and Software Product Line Conference. ACM Press, 2019. http://dx.doi.org/10.1145/3307630.3342420.

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

Nobauer, Markus, Norbert Seyff, Iris Groher, and Deepak Dhungana. "A Lightweight Approach for Product Line Scoping." In 2012 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA). IEEE, 2012. http://dx.doi.org/10.1109/seaa.2012.81.

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

Ianzen, Andressa, Rafaela Mantovani Fontana, Marco Antonio Paludo, Andreia Malucelli, and Sheila Reinehr. "Scoping Automation in Software Product Lines." In 17th International Conference on Enterprise Information Systems. SCITEPRESS - Science and and Technology Publications, 2015. http://dx.doi.org/10.5220/0005372400820091.

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

Klein, John, and John D. McGregor. "System-of-systems platform scoping." In 2013 4th International Workshop on Product LinE Approaches in Software Engineering (PLEASE). IEEE, 2013. http://dx.doi.org/10.1109/please.2013.6608653.

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

Ojeda, Marta Cecilia Camacho, Julio Ariel Hurtado Alegria, Francisco Javier Alvarez Rodriguez, and Pablo Hernando Ruiz Melenje. "A Collaborative Method for a Tangible Software Product Line Scoping." In 2018 ICAI Workshops (ICAIW). IEEE, 2018. http://dx.doi.org/10.1109/icaiw.2018.8554999.

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

Shin Young Park and Soo Dong Kim. "A systematic method for scoping core assets in product line engineering." In 12th Asia-Pacific Software Engineering Conference (APSEC'05). IEEE, 2005. http://dx.doi.org/10.1109/apsec.2005.18.

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

Hu, Jie, Ye Yang, Qing Wang, Guenther Ruhe, and Haitao Wang. "Value-based portfolio scoping: An industrial case study." In 2012 3rd International Workshop on Product LinE Approaches in Software Engineering (PLEASE). IEEE, 2012. http://dx.doi.org/10.1109/please.2012.6229770.

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

Reports on the topic "Software product line scoping"

1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Full text
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography