Browsing by Keyword "Software Product Lines"
Now showing 1 - 4 of 4
Results Per Page
Sort Options
Item Introducing product line architectures in the erp industry: Challenges and lessons learned(Lancaster University, 2010) Hamza, Haitham S.; Martinez, Jabier; Alonso, Carmen; Botterweck, Goetz; Jarzabek, Stan; Kishi, Tomoji; Lee, Jaejoon; Livengood, Steve; SWT; IAReturn on Investment (ROI) for companies involved in Enterprise Resource Planning (ERP) system development depends on their flexibility to evolve, maintain, customize and configure their ERP product to respond to new business needs, deployment models and emerging market segments. In this particular aspect, ERP systems can get benefit from commonality and variability management concepts in order to improve evolution and maintainability. Moreover, Product Line Engineering (PLE) methods and practices can substantially reduce time and effort regarding the current complex and tedious configuration procedures that are not only resource-intensive, but also error-prone. This paper introduces practical experiences from the application of product line architectures (PLAs) in four companies of the ERP systems domain.Item A Product Line Approach for AmI Environments(2009) Durán, Jon Imanol; Cobelo, Josu; Laka, Joseba; Gerhauser, Heinz; Hupp, JuRGEN; Heppner, Janina; Efstratiou, Christos; SGWithin the next decade, as digital technologies become increasingly pervasive, we might find ourselves living with almost invisible, intelligent interactive systems - an Ambient Intelligence - that will form part of our everyday existence and ecology. The main challenge at this moment is to guarantee that the new Ambient Intelligence technologies are appropriate, sustainable and meet people's individual and social needs. Human Machine Interfaces are becoming increasingly complicated (more functions, metaphors, combined interfaces) which increases the challenge for configuring and controlling them for home users, office users and OEM related support services. In this paper we will propose a software product line approach for AmI environments. Its main purpose is to offer the best available services according to user preferences while the most suitable interfaces for controlling the environment are built and offered at run-time as well. Besides, we will outline a systematic approach where our AmI software product line could be used.Item Towards an automated product line architecture recovery: The apo-games case study(Association for Computing Machinery, 2018-09-17) Lima, Crescencio; Assuncaõ, Wesley K.G.; Martinez, Jabier; Do Carmo MacHado, Ivan; Chavez, Christina Von Flach G.; Mendonca, Willian D.F.; SWTSoftware Product Line Engineering (SPLE) has been widely adopted for applying systematic reuse in families of systems. Given the high upfront investment required for SPLE adoption, organizations commonly start with more opportunistic reuse approaches (e.g., a single system that they clone and modify). However, maintenance problems appear when managing a large number of similar systems where each of them implements and evolves particular characteristics. One viable solution to solve this issue is to migrate to SPLs using an extractive approach. This initiative, in its early phases, includes the definition of a Product Line Architecture (PLA) supporting the variants derivation and also allowing the customization according to customers' needs. Our objective is to provide automatic support in PLA recovery to reduce the time and effort in this process. One of the main issues in the extractive approach is the explosion of the variability in the PLA representation. Our approach is based on identifying the minimum subset of cross-product architectural information for an effective PLA recovery. To evaluate our approach, we applied it in the case of the Apo-Games projects. The experimentation in this real family of systems showed that our automatic approach is able to identify variant outliers and help domain experts to take informed decisions to support PLA recovery.Item Variability Debt: Characterization, Causes and Consequences(Association for Computing Machinery, 2022-11-08) Wolfart, Daniele; Assunção, Wesley Klewerton Guez; Martinez, Jabier; SWTVariability is an inherent property of software systems to create families of products dealing with needs of different customers and environments. However, some practices to manage variability may incur technical debt. For example, the use of opportunistic reuse strategies, e.g., clone-and-own, harms maintenance and evolution activities; or deciding to abandon variability management and deriving a single product with all the features might threaten system usability. These examples are common problems found in practice but, to the best of or knowledge, not properly investigated from the perspective of technical debt. To expand the knowledge on the research and practice of technical debt in the perspective of variability management, we report results of this phenomenon, which we defined as variability debt. Our work is based on 52 industrial case studies that report problems observed in the use of opportunistic reuse. The results show that variability debt is caused by business, operational and technical aspects; leads to complex maintenance, creates difficulties to customize and create new products, misuse of human resources, usability problems; and impacts artifacts along the whole life-cycle. Although some of these issues are investigated in the field of systematic variability management, e.g., software product lines, our contribution is to present them from a technical debt perspective to enrich and create synergies between the two fields. As additional contribution, we present a catalog of variability debts in the light of technical debts found in the literature.