Log in

Relevant bibliographies by topics / Software product line organisations / Journal articles

Journal articles on the topic 'Software product line organisations'

To see the other types of publications on this topic, follow the link: 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:

Consult the top 50 journal articles for your research 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.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

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

11

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Badiehneshin, Abbas. "Indicator Based Software Product Line." International Journal of Engineering Trends and Technology 57, no. 1 (March 25, 2018): 11–17. http://dx.doi.org/10.14445/22315381/ijett-v57p203.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Dikel, D., D. Kane, S. Ornburn, W. Loftus, and J. Wilson. "Applying software product-line architecture." Computer 30, no. 8 (1997): 49–55. http://dx.doi.org/10.1109/2.607064.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Kim, Haeng-Kon, and Lee-Kyeong Son. "Product Line Development Process for Mobile Software based on Product Line." KIPS Transactions:PartD 12D, no. 3 (June 1, 2005): 395–408. http://dx.doi.org/10.3745/kipstd.2005.12d.3.395.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Chugh, Mitali, Nitin Chanderwal, Rajesh Upadhyay, and Devendra Kumar Punia. "Effect of knowledge management on software product experience with mediating effect of perceived software process improvement: An empirical study for Indian software industry." Journal of Information Science 46, no. 2 (March 6, 2019): 258–72. http://dx.doi.org/10.1177/0165551519833610.

Full text

Abstract:

The software development industry is characterised by swift innovation and competition. To survive, software engineering (SE) organisations need to develop high-quality software products in a timely fashion and at low cost. Knowledge-based approaches to software development are extremely supportive to acquiring new knowledge and leveraging existing knowledge from software projects; this enables constant improvement of software development practices. In this empirical study of Indian SE organisations, we study the impact of managing knowledge for perceived software process improvement (PSPI) and its effect on software product quality. Information technology (IT) in knowledge management (KM) is an important facilitator for any SE organisation desiring to exploit evolving technologies for management of their knowledge assets and for carrying out various KM processes of knowledge capture, storage, retrieval and sharing. Surveys collected from Indian SE organisations were analysed to propose a model using a structured equation modelling (SEM) technique. Our findings reveal that the relation between KM and quality of software product is positively mediated by PSPI. These findings reinforce an arena that is of growing importance to researchers and practitioners and which has seen only a limited number of empirical studies to date in the context of Indian SE organisations.

APA, Harvard, Vancouver, ISO, and other styles

16

Etxeberria, Leire, Goiuria Sagardui, and Lorea Belategi. "Quality aware software product line engineering." Journal of the Brazilian Computer Society 14, no. 1 (March 2008): 57–69. http://dx.doi.org/10.1590/s0104-65002008000100006.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Ouali, Sami, Naoufel Kraiem, and Henda Ben Ghezala. "Framework for Evolving Software Product Line." International Journal of Software Engineering & Applications 2, no. 2 (April 30, 2011): 34–51. http://dx.doi.org/10.5121/ijsea.2011.2204.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Eriksson, Magnus, Jürgen Börstler, and Kjell Borg. "Software product line modeling made practical." Communications of the ACM 49, no. 12 (December 2006): 49–54. http://dx.doi.org/10.1145/1183236.1183265.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Fernando Capretz, Luiz, Faheem Ahmed, Shereef Al‐Maati, and Zaher Al Aghbari. "COTS‐based software product line development." International Journal of Web Information Systems 4, no. 2 (June 20, 2008): 165–80. http://dx.doi.org/10.1108/17440080810882351.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Etxeberria, Leire, Goiuria Sagardui, and Lorea Belategi. "Quality aware software product line engineering." Journal of the Brazilian Computer Society 14, no. 1 (March 2008): 57–69. http://dx.doi.org/10.1007/bf03192552.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Chen, Yu, Gerald C. Gannod, and James S. Collofello. "A software product line process simulator." Software Process: Improvement and Practice 11, no. 4 (2006): 385–409. http://dx.doi.org/10.1002/spip.281.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Faust, D., and C. Verhoef. "Software product line migration and deployment." Software: Practice and Experience 33, no. 10 (2003): 933–55. http://dx.doi.org/10.1002/spe.530.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Cherian, Joseph, Karen J. Crooker, Peter Knight, James B. McPhaul, and Michael T. Manion. "Which Market Entry and Product Line Strategies Ought Organisations to Adopt for Emerging Economies?" Organizations and Markets in Emerging Economies 1, no. 1 (May 31, 2010): 82–99. http://dx.doi.org/10.15388/omee.2010.1.1.14307.

Full text

Abstract:

Emerging economies offer tremendous potential for organisations seeking to expand globally and to attain the associated rewards. However, organisations differ in their entrepreneurial tendencies to enter new markets and to introduce new products in emerging economies. Organisations also differ in their abilities to manage their development programs, that is, their execution of different types of projects that lead to success in emerging markets. Finally, organisations differ in which overall measures of program performance are consistent with their strategic objectives. This study provides a literature foundation and conceptual framework designed to understand which market entry and product line strategies and performance measures are appropriate for organisations pursuing strategic success in emerging markets. This study sets forward grounded propositions that different strategic types will vary in their market entry and product line strategies, in the project composition of their development programs, and in the orientations of performance measures used to evaluate their development programs. Prospectors, according to type, will enter emerging economies by introducing new product lines to new customer types, and by emphasizing new-to-the-world products. They will evaluate their development programs with Growth-oriented performance measures. Defenders will more typically occupy secure niches within emerging economies by emphasizing product improvement and cost reduction projects for current types of customers. They will evaluate their development programs with Efficiency-oriented performance measures. Analyzers will either target new customer types with proven products, or serve an existing market niche with new product lines. They will evaluate their development program performance with Strategy-oriented measures.

APA, Harvard, Vancouver, ISO, and other styles

24

Afzal, Muhammad Fezan, and Khalid Mahmood. "Review on product derivation approaches in the software product line." Scandic Journal Of Advanced Research And Reviews 2, no. 2 (May 10, 2022): 042–56. http://dx.doi.org/10.55966/sjarr.2022.2.2.0033.

Full text

Abstract:

: Product derivation is one of the most important challenges in the software product line. Obtaining the individual product from the shared software is a costly and time-consuming job. Various approaches have been proposed for product derivation in the software product line in previous times. This paper will review approaches concerning the product derivation in the software product line. This paper will provide a state-of-the-art literature review on product derivation in software line approaches. Moreover, this will be more useful in order to obtain a novel valid feather combination approach for product derivation in software product line.

APA, Harvard, Vancouver, ISO, and other styles

25

Pandit, Madhukar. "Integrated Extruder Plant Automation with Learning Control." Key Engineering Materials 424 (December 2009): 273–80. http://dx.doi.org/10.4028/www.scientific.net/kem.424.273.

Full text

Abstract:

Integrated automation in a manufacturing plant demands control of manufacturing and material and product flow processes. Efficient data archiving and retrieval, quality control and process automation facilities are essential components which should be deployed to form one coherent system. As managers of extruder plants running look for ways and means for meeting market requirements, the demand for such integrated automation systems is rising. Integrated Process automation involves: - Overall production and process control - Data acquisition, archiving evaluation with feed-back to production planning and process control - Decentral control in local control loops for achieving isothermal extrusion - On-line visualisation of process variables for tighter man-machine interaction Providing the facility for prescribing the ranges of relevant process variables viz. billet temperature, die temperature, profile temperature at die exit, rate of cooling of the profile and extrusion speed is part of the integrated automation system. At the heart of the system are processes for mastering the core task of management of the thermal processes in the extruder by employing sensors and control techniques. Goal is to minimise the time to extrude a billet and simultaneously keep the process variables within prescribed limits. Automation in extrusion plants is made possible by progress in sensor technology and enhanced possibilities of data processing and organisation, advanced control methods which require simple models and facilities of integration of hardware and software employing state-of-the-art networking and protocols. Crucial is the non-contact temperature measurement of the billet and the profile at die exit. Since about two decades there has been a continuous progress in temperature measurement technology based on multi-spectral radiation pyrometers. They perform well for a large number of alloys and surface finishes and are reliable for industrial use. Disturbances can be suppressed using adequate signal processing

APA, Harvard, Vancouver, ISO, and other styles

26

Hobday, Mike, and Tim Brady. "Rational Versus Soft Management in Complex Software: Lessons from Flight Simulation." International Journal of Innovation Management 02, no. 01 (March 1998): 1–43. http://dx.doi.org/10.1142/s136391969800002x.

Full text

Abstract:

This paper compares actual (A-type) software processes at work in flight simulation, one example of a software-intensive complex product system, with ideal, rational (B-type) processes as contained in company manuals, tools and procedures. The aim is to identify the causes and consequences of divergencies between A- and B-type processes in a complex product, and to draw implications for theory and practice. The paper also develops a simple partial model to show what A-type processes actually "look like" in practice. The evidence indicates that in response to industrial turbulence, uncertainty, technical complexity and difficulties in capturing user requirements, software engineers and project managers fall back heavily on A-type informal systems and "soft" management becomes essential to project success. Success under such circumstances, B-type rational systems are inadequate to the task at hand and soft factors such as goodwill, negotiation skills, rule breaking and informal communications become essential to project success. These findings contrast with most approaches to software engineering which try to impose highly rational processes and tend to ignore soft issues. The paper also indicates potential benefits of the rational approach, sometimes overlooked by contemporary organisational scholars, by arguing that it is the manner in which B-type processes are developed and implemented which leads to divergencies and difficulties, rather than the processes themselves which are an essential part of orderly progress. While the findings may not be relevant to more simple products and tasks, other complex product systems may well face similar divergencies and project management challenges.

APA, Harvard, Vancouver, ISO, and other styles

27

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Coallier, François, and Roger Champagne. "A Product Line engineering practices model." Science of Computer Programming 57, no. 1 (July 2005): 73–87. http://dx.doi.org/10.1016/j.scico.2004.10.006.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Yehia Hassan, Ayat. "A SURVEY ON SOFTWARE PRODUCT-LINE TESTING." International Journal of Advanced Research 9, no. 01 (January 31, 2021): 90–96. http://dx.doi.org/10.21474/ijar01/12280.

Full text

Abstract:

SPL (Software Product Line) is known as a set of software systems that share a mutual set of features. It is a powerful concept to achieve more efficient software system development. One of the necessary steps in software development processes is Testing. It consumes typically more than 50% of the whole development costs. Testing SPLs is challenging due to the exponential number of products in the number of features. Several approaches have been proposed to reduce the number of products to be tested. However, the testing aspect of SPL is still underdeveloped. This study aims at surveying the latest research on SPL testing to identify useful approaches and needs for future research. seven papers are classified concerning the following: the used Approach, the algorithms, and the type of testing that the research focuses on. The survey found that more validation and evaluation research is required to produce a more robust foundation for SPL testing. Finally, directions for future software product line testing recommendations.

APA, Harvard, Vancouver, ISO, and other styles

30

Ripon, Shamim, Sk Jahir Hossain, and Touhid Bhuiyan. "Managing and Analysing Software Product Line Requirements." International Journal of Software Engineering & Applications 4, no. 5 (September 30, 2013): 63–75. http://dx.doi.org/10.5121/ijsea.2013.4505.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Krueger, Charles W. "New methods in software product line practice." Communications of the ACM 49, no. 12 (December 2006): 37–40. http://dx.doi.org/10.1145/1183236.1183262.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Schaefer, Ina, and Reiner Hahnle. "Formal Methods in Software Product Line Engineering." Computer 44, no. 2 (February 2011): 82–85. http://dx.doi.org/10.1109/mc.2011.47.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Costa, Gabriella Castro B., Regina Braga, José Maria N. David, Fernanda Campos, and Wagner Arbex. "PL-Science: A Scientific Software Product Line." Procedia Computer Science 18 (2013): 759–68. http://dx.doi.org/10.1016/j.procs.2013.05.240.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Borba, Paulo, Leopoldo Teixeira, and Rohit Gheyi. "A theory of software product line refinement." Theoretical Computer Science 455 (October 2012): 2–30. http://dx.doi.org/10.1016/j.tcs.2012.01.031.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Fajar, Ahmad Nurul, Ditdit Nugeraha Utama, and Gunawan Wang. "Intelligent Software Product Line For Supply Chain." Journal of Physics: Conference Series 1090 (September 2018): 012043. http://dx.doi.org/10.1088/1742-6596/1090/1/012043.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Tan, Lei, Yuqing Lin, and Huilin Ye. "Quality-Oriented Software Product Line Architecture Design." Journal of Software Engineering and Applications 05, no. 07 (2012): 472–76. http://dx.doi.org/10.4236/jsea.2012.57054.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Niemelä, Eila, and Tuomas Ihme. "Product line software engineering of embedded systems." ACM SIGSOFT Software Engineering Notes 26, no. 3 (May 2001): 118–25. http://dx.doi.org/10.1145/379377.375271.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Insfran, Emilio, Gary Chastek, Patrick Donohoe, and Julio César Sampaio do Prado Leite. "Requirements engineering in software product line engineering." Requirements Engineering 19, no. 4 (November 6, 2013): 331–32. http://dx.doi.org/10.1007/s00766-013-0189-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Hanssen, Geir K. "Agile software product line engineering: enabling factors." Software: Practice and Experience 41, no. 8 (April 26, 2011): 883–97. http://dx.doi.org/10.1002/spe.1064.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Kumar, Satendra, Mohit Mittal, and Vinod Kumar Yadav. "Cost-effective product prioritisation technique for software product line testing." International Journal of Engineering Systems Modelling and Simulation 12, no. 2/3 (2021): 83. http://dx.doi.org/10.1504/ijesms.2021.115518.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Yadav, Vinod Kumar, Satendra Kumar, and Mohit Mittal. "Cost-effective product prioritisation technique for software product line testing." International Journal of Engineering Systems Modelling and Simulation 1, no. 1 (2021): 1. http://dx.doi.org/10.1504/ijesms.2021.10035529.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Ferreira, Thiago N., Jackson A. Prado Lima, Andrei Strickler, Josiel N. Kuk, Silvia R. Vergilio, and Aurora Pozo. "Hyper-Heuristic Based Product Selection for Software Product Line Testing." IEEE Computational Intelligence Magazine 12, no. 2 (May 2017): 34–45. http://dx.doi.org/10.1109/mci.2017.2670461.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Laguna, Miguel A., and Yania Crespo. "A systematic mapping study on software product line evolution: From legacy system reengineering to product line refactoring." Science of Computer Programming 78, no. 8 (August 2013): 1010–34. http://dx.doi.org/10.1016/j.scico.2012.05.003.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Yaman, Sezin Gizem, Myriam Munezero, Jürgen Münch, Fabian Fagerholm, Ossi Syd, Mika Aaltola, Christina Palmu, and Tomi Männistö. "Introducing continuous experimentation in large software-intensive product and service organisations." Journal of Systems and Software 133 (November 2017): 195–211. http://dx.doi.org/10.1016/j.jss.2017.07.009.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Ebert, C. "Hands-on experience implementing a product line - Software Product-Line Engineering: A Family-Based Software Development Process [Book Review]." IEEE Software 18, no. 1 (January 2001): 105–6. http://dx.doi.org/10.1109/ms.2001.903177.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Schwanninger, Christa, and David Benavides. "Editorial for the special section on Software Product Line Engineering: Selected papers from Software Product Line conference in 2012." Information and Software Technology 56, no. 9 (September 2014): 1099–100. http://dx.doi.org/10.1016/j.infsof.2014.03.008.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

KIM, YOUNG-GAB, SEOK KEE LEE, and SUNG-BONG JANG. "VARIABILITY MANAGEMENT FOR SOFTWARE PRODUCT-LINE ARCHITECTURE DEVELOPMENT." International Journal of Software Engineering and Knowledge Engineering 21, no. 07 (November 2011): 931–56. http://dx.doi.org/10.1142/s0218194011005542.

Full text

Abstract:

Software Product-Line Engineering (SPLE) is composed of two areas, namely domain engineering and application engineering. Domain engineering is associated with product-line architecture, which is a core asset of the product-line. One of the key issues of the software product-line, especially in domain engineering, is handling the variability among product families. That is, variation management for the software product-line architecture determines the success of software development. Therefore, this paper proposes processes and artifacts to build the software product-line architecture and to manage uniform variability over the life cycle of software product-lines. Furthermore, a case study, namely, the Electronic Medical Record (EMR) system, is presented.

APA, Harvard, Vancouver, ISO, and other styles

48

Haupt, Michael, Stefan Marr, and Robert Hirschfeld. "CSOM/PL — A Virtual Machine Product Line." Journal of Object Technology 10 (2011): 12:1. http://dx.doi.org/10.5381/jot.2011.10.1.a12.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Jaejoon Lee and Gerald Kotonya. "Combining Service-Orientation with Product Line Engineering." IEEE Software 27, no. 3 (May 2010): 35–41. http://dx.doi.org/10.1109/ms.2010.30.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Padmanabhan, Prasanna, and Robyn R. Lutz. "Tool-Supported Verification of Product Line Requirements." Automated Software Engineering 12, no. 4 (October 2005): 447–65. http://dx.doi.org/10.1007/s10515-005-2648-4.

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!