Relevant bibliographies by topics / Software product line organisations

Academic literature on the topic 'Software product line organisations'

Author: Grafiati
Published: 10 December 2022
Last updated: 28 January 2023

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

Select a source type:

Contents

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

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 organisations"

1

Novrialdi, Adrika, Daya Adianto, Aulia Rosyida, Priambudi Lintang Bagaskara, and Ade Azurat. "Towards Erlang-based ABS Microservices Framework for Software Product Line Development." Jurnal Ilmu Komputer dan Informasi 15, no. 2 (July 2, 2022): 105–18. http://dx.doi.org/10.21609/jiki.v15i2.1065.

Full text
Abstract:
The current widely used software system can be categorised as a large or very large decentralised control system with various requirements and continuous interchangeable elements. This characteristic leads to a need to control the variability to manage such systems. Software Product Line Engineering (SPLE) is one of the approaches that can manage the variability by developing sets of products. However, there is a need for support tools for development with software product line engineering. One language that supports the SPLE process is Abstract Behavioral Specification (ABS). Some SPLE research has used ABS to create frameworks that support the SPLE process. ABS Microservices is one research that utilises ABS to create a web framework that supports the SPLE process. This framework uses ABS to generate Java-based applications. The research interest in the web application is driven by the fact that it is one of the software types widely used by organisations and serves as the primary support of their business. Microservices are highly interoperable, thus enabling researchers to integrate different technology from other research. However, there is a need for renewal to the ABS Microservices framework. There is a need for more variants of SPLE-enabled frameworks that use more programming language as a specific programming language has its strength and weakness. Deprecation of the Java backend of the ABS opens a new exploration of another web framework that uses other ABS backend languages. We present the ABS microservices web framework based on Erlang OTP. We choose Erlang because it promises more efficient resource usage and the Erlang backend is one of the ABS backends with the most available features. This research aims to create an entry point for ABS Microservices to support more language. This research shows that the Erlang variant of ABS Microservices has less resource usage than the Java variant. Hence, this promises more options to develop product lines using ABS Microservices.
APA, Harvard, Vancouver, ISO, and other styles
2

Khalifeh, Amin, Peter Farrell, Mohammad Alrousan, Shaima Alwardat, and Masar Faisal. "Incorporating sustainability into software projects: a conceptual framework." International Journal of Managing Projects in Business 13, no. 6 (July 10, 2020): 1339–61. http://dx.doi.org/10.1108/ijmpb-12-2019-0289.

Full text
Abstract:
PurposeThe paper aims to present a conceptual framework that helps in incorporating sustainability into software projects, highlights the importance of project sustainability and provides an extensive review of recent relevant contributions across various fields.Design/methodology/approachThe authors carried out a systematic bibliographic search on relevant published materials to analyse links between the two disciplines (sustainability and software projects). Furthermore, content analysis was applied to the final selected publications to identify and classify relevant triple bottom line (TBL) aspects to develop the framework.FindingsThe inclusion of TBL-related aspects is the most efficient and effective method used to incorporate sustainability into projects. Most of the relevant contributions in the software literature have focussed on either project product or project process or on one or two dimensions of sustainability rather than the three dimensions of the TBL theory. This study contributes by proposing a conceptual framework that encompasses TBL-related aspects for incorporating sustainability into processes and products of software projects.Research limitations/implicationsValidating the proposed framework empirically could be an interesting research issue. In addition, future works may focus on different types of industries, such as information systems, telecommunications and service sectors, which have seldom been studied in the literature.Practical implicationsSoftware companies – or other relevant organisations – may use the proposed framework as a measurement tool to evaluate the environmental and social impacts of their current products and project management practices. Consequently, these organisations may pay more attention to incorporating sustainability into their project management practices.Originality/valueThe proposed framework may contribute towards a more sustainable orientation by providing a unique combination of TBL-related aspects that gives academics and practitioners a better understanding of how software projects can be managed sustainably.
APA, Harvard, Vancouver, ISO, and other styles
3

Varela-Vaca , Ángel Jesús, Rafael M. Gasca, Rafael Ceballos, María Teresa Gómez-López, and Pedro Bernáldez Torres. "CyberSPL: A Framework for the Verification of Cybersecurity Policy Compliance of System Configurations Using Software Product Lines." Applied Sciences 9, no. 24 (December 8, 2019): 5364. http://dx.doi.org/10.3390/app9245364.

Full text
Abstract:
Cybersecurity attacks affect the compliance of cybersecurity policies of the organisations. Such disadvantages may be due to the absence of security configurations or the use of default configuration values of software products and systems. The complexity in the configuration of products and systems is a known challenge in the software industry since it includes a wide range of parameters to be taken into account. In other contexts, the configuration problems are solved using Software Product Lines. This is the reason why in this article the framework Cybersecurity Software Product Line (CyberSPL) is proposed. CyberSPL is based on a methodology to design product lines to verify cybersecurity policies according to the possible configurations. The patterns to configure the systems related to the cybersecurity aspects are grouped by defining various feature models. The automated analysis of these models allows us to diagnose possible problems in the security configurations, reducing or avoiding them. As support for this proposal, a multi-user and multi-platform solution has been implemented, enabling setting a catalogue of public or private feature models. Moreover, analysis and reasoning mechanisms have been integrated to obtain all the configurations of a model, to detect if a configuration is valid or not, including the root cause of problems for a given configuration. For validating the proposal, a real scenario is proposed where a catalogue of four different feature models is presented. In this scenario, the models have been analysed, different configurations have been validated, and several configurations with problems have been diagnosed.
APA, Harvard, Vancouver, ISO, and other styles
4

TROTT, P., and A. HOECHT. "ENTERPRISE RESOURCE PLANNING (ERP) AND ITS IMPACT ON THE INNOVATIVE CAPABILITY OF THE FIRM." International Journal of Innovation Management 08, no. 04 (December 2004): 381–98. http://dx.doi.org/10.1142/s1363919604001118.

Full text
Abstract:
Enterprise Resource Planning (ERP) business software has become one of the most successful products in the world. Microsoft, ICI, UBS and Procter & Gamble are a few of the firms that have claimed it has changed the way they work (Gartner, 2002). Indeed, substantial claims are made about the software's capabilities. A complete system could take several years and several hundred million dollars to deploy. SAP, Oracle, Baan and PeopleSoft are the market leaders and SAP has over 20,000 R/3 products installed worldwide; Oracle has installed databases in nearly every one of the world's top 500 companies. This paper surveys the literature and identifies that there is increasing evidence that firms fail to obtain the benefits of these investments within the anticipated timeframes (Pollock et al., 2003). Moreover, and more worrying for senior managers is the extent to which these fully integrated systems using on-line transactional processing are affecting the firm's innovative ability. We argue in this paper that there is a fundamental clash of underlying principles between ERP systems requirements and the success factors of innovative organisations that lie at the heart of the innovation dilemma caused by the introduction of ERP systems into organisations.
APA, Harvard, Vancouver, ISO, and other styles
5

MUNTEANU, Valentin Partenie, and Paul DRAGOS. "A THEORETICAL VIEW ABOUT AGILE MANAGEMENT IN BANK SECTOR." ANNALS OF THE UNIVERSITY OF ORADEA. ECONOMIC SCIENCES 30, no. 2 (December 2021): 344–52. http://dx.doi.org/10.47535/1991auoes30(2)036.

Full text
Abstract:
The adoption of Agile methodologies is one of the biggest topics in large organisations and many IT departments nowadays. Banks must introduce new flexible approaches to keep up with the changes in the market, especially regarding the new digital technologies. Large enterprises in all information system programs have implemented Agile approaches because of the widespread benefits. Unlike traditional development model, agile guidelines encourage businesses to follow a straightforward and data-oriented procedure and continually test and learn, rather than producing a final product before testing. This research aims to explore the benefits of Agile approaches in the banking industry and the problems with implementing such methods in product development processes. This study also leads to speedy marketing by offering a minimum viable product (MVP) that satisfies consumers’ needs and can be easily adapted. Although various studies explored the implementation of agile principles in multiple contexts, this research is based primarily on the banking software industry. The banking sector must transform itself, to become more digital. However, digital processes are not as simple as in other sectors because banks operate on regulated markets, making it even more challenging to adopt Agile methods. In conjunction with the Agile approaches, this study also illustrates the current management practices. This research is mostly theoretical and qualitative, attempting to complete an existing gap by thoroughly reviewing the existing literature on Agile methodologies for software development and reviewing the standards for banks’ software development life cycles. Managing the regulatory climate in which banks work is an essential challenge in optimizing agility. This paper’s findings contribute to the field by offering an insight into how Agile approaches can be implemented on the banking setting by analysing the existing literature, with a focus on financial software development.
APA, Harvard, Vancouver, ISO, and other styles
6

Kara, Sami, Suphunnika Ibbotson, and Berman Kayis. "Sustainable product development in practice: an international survey." Journal of Manufacturing Technology Management 25, no. 6 (July 1, 2014): 848–72. http://dx.doi.org/10.1108/jmtm-09-2012-0082.

Full text
Abstract:
Purpose – Improved environmental performance of products and services have lately become one of the main strategic and operational goals of manufacturers. This is due to influences from various stakeholders including government, consumers, societies and the business partners. Evidently, different manufacturers differently implement their environmental practices for sustainable product development depending on various driving factors such as customer awareness, legislation, economic benefits and competitive strategies, etc. In theory, manufacturers can efficiently undertake sustainable product development by implementing life cycle thinking into their system. This way, they can monitor the environment hot spots throughout a product life cycle and be able to minimise the environmental impact effectively. Therefore, several researchers have focused on developing tools and strategies to support the manufacturers in implementing sustainable manufacturing and product development studies. However, in reality, each manufacturer may operate their manufacturing system differently to accommodate different demands and constraints induced by firm characteristics and its regional location. Their attempts to implement the sustainable tools and strategies to their companies would also be different. Thus far, a number of studies have studied the implementation for a specific company. No studies have examined the relationship between their decisions and implementation for different characteristics of firms and different manufacturing locations. Therefore, the purpose of this paper is to comprehensively investigate the practices of manufacturers towards sustainable product development. Design/methodology/approach – A detailed statistical analysis was conducted on the survey data gathered from 330 manufacturing organisations in 13 countries. The research questions mainly cover implementation approaches, decision tools and techniques used and main driving forces at the strategic and operational levels concerning environmental practices in sustainable product development. This is to bridge the gaps between the research outputs and implementations in practice for the developed sustainable strategies and tools. Results highlighted interesting relationships of the implementations across different geographical regions (locations) as well as types and sizes of manufacturers. They can be used to shed some light for future research direction, the dominant driving forces of consumers and regulations importance towards the manufacturer practices to improve not only the environmental performance but also their social responsibility. In total, 12 null hypotheses were formulated to test the relationships as well as the correlations between the manufacturing characteristics and the research questions which cover several driving forces in implementing the environmental strategies. Findings – The results of this large-scale global research highlighted that different geographical/manufacturing regions are driven mainly by legislation, competition and consumer pressures whilst manufacturers of different sizes utilise various decision tools. Design tools such as LCA, DFE and ECQFD methods are likely to be utilised in the medium-and high-complexity product development by OEM and ETM manufacturers. Environmental responsibility plays an important role and also enhanced by other driving forces such as the economic benefits, the long-term survival in the market and the company image. Research limitations/implications – Future work may include some or all of the following; such as respondents of this survey may be re-contacted and comparative data can be gathered from these manufacturers to capture the changes over the years. Further investigation of the sustainable supply chain management approaches, influences of dynamic driving forces and the environmental practices towards cleaner production practices such as improving energy efficiency, minimising waste, recycling scraps and reusing product as well as the product recovery practices for used products would be beneficial to gather and evaluate. This would support to address the current trends and emerging practices. Practical implications – Results highlighted interesting relationships and thus provide some answers on strategies adopted by many manufacturers for the sustainability approaches and implementations across different geographical regions (locations) as well as types and sizes of manufacturers. The wave of change towards sustainability is clearly on enterprises, industries, communities and governments for thinking about solutions to increase the awareness in environmental sustainability thus reduce carbon footprint. In some areas there is clear progress but for many, this process is just beginning. Social implications – There is an overwhelming amount of information, methods and opinions, and proliferation of initiatives. It is in this climate that not only manufacturers but society must provide a practical and effective way to develop and disseminate the skills and knowledge required to fuel an environmentally sustainable economy. To achieve this, results of global surveys like this paper may support manufacturers who need to work with communities and stay well connected to their stakeholders. This may lead to developing training packages that accurately reflect industry needs and provide leadership in communities and workforce development. Originality/value – There is generally an understanding of the sustainable product development and the use and role of tools and techniques to improve environmental performance of manufacturers at micro-level (within companies based on selected product, process, environmental tools and manufacturing characteristics). Whereas, a large-scale research like this paper, to present the status of sustainable product and process development approaches used by manufacturers located around the globe, of different sizes, types within existing operational and corporate strategies and eco-design initiatives have not been detailed.
APA, Harvard, Vancouver, ISO, and other styles
7

Korn, Janos. "Crisis in systems thinking." Kybernetes 49, no. 7 (July 19, 2019): 1915–34. http://dx.doi.org/10.1108/k-01-2019-0026.

Full text
Abstract:
Purpose The current field of systems thinking consists of a variety of views, methods and a number of organisations involved with these views which suggests a state of confusion and fragmentation of the field which fundamentally is supposed to be a uniform view of structures or systems. This can be interpreted as a “crisis situation”. A resolution of the crisis in the form of a “new science of systems” is proposed. Assuming this new science becomes part of the field of systems thinking, a debate of the elements of the field is suggested with a view to consider its current state and future developments. “Crisis - resolution - debate” is the central theme of the paper. Design/methodology/approach The field of current systems thinking is described in terms of views, methods and organisations and is seen as the “problematic issue”. A “new science of systems” strongly rooted in natural language as its primary symbolism and consisting of three general principles of systems and linguistic modelling is outlined to be considered as the resolution of the crisis. A set of criteria is discussed for use of judging the quality of models and element of the field of systems thinking including the “new science of systems”. To demonstrate a preliminary use of these criteria, the same example is worked out using both, the “soft systems methodology” and “linguistic modelling” for comparison. Findings The universal view of parts of the world as structures or systems is inconsistent with the multiple methods basically pursuing the same purpose: modelling aspects of systems which prevail in current systems thinking. To try to resolve this anomaly an equally universally applicable approach, the “new science of systems” is proposed which can also serve as an aid to problem solving, in particular to an integrated systems and product design. This approach is to be part of the suggested debate of the field of systems thinking. In general, there is no alternative to the structural view. Research limitations/implications The “new science of systems”, if found acceptable, can offer research opportunities in new applications of accepted branches of knowledge like logic, linguistics, mathematics of ordered pairs, uncertainties and in the philosophy of science. New teaching schemes can be developed at classroom level combined with engineering as creator of novelties with linguistics as the symbolism to supplement mathematics. Further considerations can be given to current methodologies of systems thinking as part of a debate with a view of future developments in exploring pioneering ideas. New software is needed for working out the dynamics of scenarios. Practical implications The debate, if it takes place, should result in new developments in the field of systems thinking such as concepts accepted as fundamental in the discipline of systems. Applications of the “new science of systems” to larger scale scenarios and organisations guided by the universal scheme in Figure 1 and linguistic modelling with software are needed for development of schemes for problem solving schemes “utilising” or “producing” products. Social implications The “new science of systems” is rooted in accepted branches of knowledge; it is highly teachable at school and university levels and should lead to use by professionals and in everyday life activities once found acceptable. The use of the scheme in Figure 1 should help in clarifying confusing scenarios and to aid problem solving. Originality/value The suggestion of a debate is an original idea. The “new science of systems” consists of three general principles of systems implemented by linguistic modelling of static and dynamic states. Mathematics of uncertainty and topics from conventional science at the object level supplement the “new science” which together form the “scientific enterprise”. The notions of cognitive value and informative content of models are introduced for evaluating their cognitive worth.
APA, Harvard, Vancouver, ISO, and other styles
8

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

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

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
10

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

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

Dissertations / Theses on the topic "Software product line organisations"

1

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
2

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
3

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
4

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
5

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
6

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
7

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
8

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
9

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
10

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
More sources

Books on the topic "Software product line organisations"

1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Designing software product lines with UML: From use cases to pattern-based software architectures. Boston: Addison-Wesley, 2005.

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

Ireland) Software Product Lines Conference (12th 2008 Limerick. SPLC 2008: 12th International Software Product Line Conference : proceedings : 8-12 September 2008, Limerick, Ireland. Los Alamitos, Calif: IEEE Computer Society, 2008.

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. Los Alamitos, Calif: IEEE Computer Society, 2006.

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

Book chapters on the topic "Software product line organisations"

1

Böckle, Günter. "Organisation." In Software Product Line Engineering, 375–92. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/3-540-28901-1_19.

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

van der Linden, Frank, Klaus Schmid, and Eelco Rommes. "Organisation." In Software Product Lines in Action, 59–78. Berlin, Heidelberg: Springer Berlin Heidelberg, 2007. http://dx.doi.org/10.1007/978-3-540-71437-8_5.

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

Chastek, Gary, and Patrick Donohoe. "Product Line Analysis." In Software Product Lines, 310. Berlin, Heidelberg: 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
4

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

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

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

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

Fritsch, Claudia, and Ralf Hahn. "Product Line Potential Analysis." In Software Product Lines, 228–37. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-28630-1_14.

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

Clements, Paul. "Product-Line Engineering." In Software Architectures for Product Families, 253–54. Berlin, Heidelberg: Springer Berlin Heidelberg, 2000. http://dx.doi.org/10.1007/978-3-540-44542-5_27.

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

Bosch, Jan. "Software Product Line Engineering." In Systems and Software Variability Management, 3–24. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-36583-6_1.

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

Khalid, Lina. "Software Product Line (SPL)." In Software Architecture for Business, 95–106. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-13632-1_6.

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

Bayer, Joachim, Sebastien Gerard, Øystein Haugen, Jason Mansell, Birger Møller-Pedersen, Jon Oldevik, Patrick Tessier, Jean-Philippe Thibault, and Tanya Widen. "Consolidated Product Line Variability Modeling." In Software Product Lines, 195–241. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/978-3-540-33253-4_6.

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

Conference papers on the topic "Software product line organisations"

1

Krsek, Martin, Jay van Zyl, Robert Redpath, Ben Clohesy, and Nick Dean. "Experiences of Large Banks: Hurdles and Enablers to the Adoption of Software Product Line Practices in Large Corporate Organisations." In 2008 12th International Software Product Line Conference (SPLC). IEEE, 2008. http://dx.doi.org/10.1109/splc.2008.43.

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

Chew, Khai Min, and Wah Pheng Lee. "A Proposed RAMI 4.0 Product Life Cycle Framework using the Manufacturing Chain Management Platform." In International Conference on Digital Transformation and Applications (ICDXA 2021). Tunku Abdul Rahman University College, 2021. http://dx.doi.org/10.56453/icdxa.2021.1002.

Full text
Abstract:
The RAMI4.0 model consists of three axes; the Layers axis, the Hierarchy axis, and the Life Cycle Value Stream axis. This model unifies the various aspects of I4.0 to allow data generated from manufacturing and business activities to be shared effectively. The Manufacturing Chain Management software aims to provide a platform where all three axes and their associated data are tightly integrated and can be used to provide I4.0 connectivity as well as insights into the manufacturing supply chain. A data framework is proposed whereby the data from these activities can be collected and used to make more insightful decisions about an organisations value chain, value stream, and the life cycle of their product portfolio. The MCM platform is aimed at SMEs, which generally has lesser financial ability to invest into I4.0 technologies. Hence, the MCM platform is designed to be flexible and scalable whilst maintaining compliance with international I4.0 standards. Keywords: RAMI4.0, product life cycle, value chain analysis, value stream mapping, manufacturing chain management
APA, Harvard, Vancouver, ISO, and other styles
3

Horcas, Jose-Miguel, Mónica Pinto, and Lidia Fuentes. "Software Product Line Engineering." In SPLC 2019: 23rd International Systems and Software Product Line Conference. New York, NY, USA: ACM, 2019. http://dx.doi.org/10.1145/3336294.3336304.

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

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. New York, NY, USA: ACM, 2022. http://dx.doi.org/10.1145/3546932.3547012.

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

Estublier, Jacky, Idrissa A. Dieng, and Thomas Leveque. "Software product line evolution." In the 2010 ICSE Workshop. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1808937.1808942.

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

Zhang, Xiaorui. "Synthesize software product line." In the 32nd ACM/IEEE International Conference. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1810295.1810383.

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

Savolainen, Juha, and Mike Mannion. "Aligning product line business and technical strategies (mapping product line requirements to a product line architecture)." In the 16th International Software Product Line Conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2364412.2364461.

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

Mannion, Mike, and Juha Savolainen. "Mapping product line requirements to a product line architecture." In SPLC '14: 18th International Software Product Line Conference. New York, NY, USA: ACM, 2014. http://dx.doi.org/10.1145/2648511.2648559.

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

Martinez, Omar Cristian, Silvio Gonnet, Horacio Leone, and Nicolas Diaz. "Product feasibility verification in software product line." In 2012 XXXVIII Conferencia Latinoamericana En Informatica (CLEI). IEEE, 2012. http://dx.doi.org/10.1109/clei.2012.6427224.

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

Chacón-Luna, Ana Eva, Antonio Manuel Gutiérrez Fernández, José A. Galindo, and David Benavides. "Empirical software product line engineering." In SPLC '21: 25th ACM International Systems and Software Product Line Conference. New York, NY, USA: ACM, 2021. http://dx.doi.org/10.1145/3461001.3473062.

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

Reports on the topic "Software product line organisations"

1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software product line organisations' for particular source types:
Journal articles Dissertations / Theses Books
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