Software Product Line Engineering: Future Research Directions

The recent trend of switching from single software product development tolines of software products in the software industry has made the software product line concept viable and widely accepted methodology in the future. Some of the potential benefits of this approach include cost reduction, improvement in quality and a decrease in product development time. Many organizations that deal in wide areas of operation, from consumer electronics, telecommunications, and avionics to information technology, are using software product lines practice because it deals with effective utilization ofsoftware assets and provides numerous benefits. Software product line engineering is an inter-disciplinary concept. It spans over the dimensions of business, architecture, process and organization. The business dimension of software product lines deals with managing a strong coordination between product line engineering and the business aspects of product line. Software product line architecture is regarded as one of the crucial piece of entity in software product lines. All the resulting products share thiscommon architecture. The organizational theories, behavior and management play critical role in the process of institutionalization of software product line engineering in an organization. The objective of this chapter is to discuss the state of the art of software product line engineering from the perspectives of business, architecture, organizational management and software engineering process. This work also highlights and discusses the future research directions in this area thus providing an opportunity to researchers and practitioners to better understand the future trends and requirements

A Model-Based Approach to Managing Feature Binding Time in Software Product Line Engineering

Software Product Line Engineering (SPLE) is a software reuse paradigm for developing software products, from managed reusable assets, based on analysis of commonality and variability (C & V) of a product line. Many approaches of SPLE use a feature as a key abstraction to capture the C&V. Recently, there have been increasing demands for the provision of flexibility about not only the variability of features but also the variability of when features should be selected (i.e., variability on feature binding times). Current approaches to support variations of feature binding time mostly focused on ad hoc implementation mechanisms. In this paper, we first identify the challenges of feature binding time management and then propose an approach to analyze the variation of feature binding times and use the results to specify model-based architectural components for the product line. Based on the specification, components implementing variable features are parameterized with the binding times and the source codes for the components and the connection between them are generated

Using XDAQ in Application Scenarios of the CMS Experiment

XDAQ is a generic data acquisition software environment that emerged from a rich set of of use-cases encountered in the CMS experiment. They cover not the deployment for multiple sub-detectors and the operation of different processing and networking equipment as well as a distributed collaboration of users with different needs. The use of the software in various application scenarios demonstrated the viability of the approach. We discuss two applications, the tracker local DAQ system for front-end commissioning and the muon chamber validation system. The description is completed by a brief overview of XDAQ.Comment: Conference CHEP 2003 (Computing in High Energy and Nuclear Physics, La Jolla, CA

Some Findings Concerning Requirements in Agile Methodologies

gile methods have appeared as an attractive alternative to conventional methodologies. These methods try to reduce the time to market and, indirectly, the cost of the product through flexible development and deep customer involvement. The processes related to requirements have been extensively studied in literature, in most cases in the frame of conventional methods. However, conclusions of conventional methodologies could not be necessarily valid for Agile; in some issues, conventional and Agile processes are radically different. As recent surveys report, inadequate project requirements is one of the most conflictive issues in agile approaches and better understanding about this is needed. This paper describes some findings concerning requirements activities in a project developed under an agile methodology. The project intended to evolve an existing product and, therefore, some background information was available. The major difficulties encountered were related to non-functional needs and management of requirements dependencies

Дослідження системи операційного менеджменту організації, на прикладі Apple Computer, Inc

The object of investigation is the process of managing of operating activities of Apple, Inc. The aim of the work is to formulate theoretical approaches and to develop practical recommendations on directions of improvement of operating management at the organization. Research methods cover methods of analysis, synthesis, comparison, detailing, system approach. This master’s research paper analyzes the operational management of Apple, Inc. and provides recommendations for it’s improvement. In particular, the main directions of solving the problems of operational management of the company have been outlined, the proposals on improvement of expansion distribution network and organization of innovative activity of the Apple Inc. have been made.Об'єкт дослідження ‒ процес управління операційною діяльністю компанії Apple, Inc. Мета дослідження - формування теоретичних підходів та розробка практичних рекомендацій щодо напрямів вдосконалення системи операційного менеджменту компанії Apple, Inc. Методи дослідження: методи аналізу, синтезу, порівняння, деталізації, системний підхід. У роботі проведено аналіз операційного менеджменту Apple, Inc., а також викладені рекомендації щодо його вдосконалення. Зокрема, окреслено основні напрями вирішення проблем операційного менеджменту компанії, внесено пропозиції щодо розширення дистриб’юторської мережі, а також вдосконалення організації інноваційної діяльності Apple Inc.Introduction 6 CHAPTER 1 THE THEORETICAL FRAMEWORK OF OPERATIONAL MANAGEMENT 8 1.1 Meanings and definition of operational management 8 1.2 Principles and methods of operations management 12 1.3 Factors affecting the Operations activity of Apple Inc. company 21 CHAPTER 2 RESEARCH AND ANALYSIS 31 2.1 Сompany introduction 31 2.2 SWOT - analysis of Apple Inc. Company 46 2.3 Analysis of operation management at Apple Inc 50 CHAPTER 3 RECOMMENDATIONS FOR IMPROVING OF OPERATIONAL MANAGEMENT AT THE APPLE INC 63 3.1 The main directions of solving operational management problems of the company 63 3.2 Recommendations concerning improvements of Distribution in the organization 65 3.3 Recommendations concerning improvements of innovative activity at the organization 67 CHAPTER 4 SPECIAL PART 73 4.1 Current trends in the field 73 4.2 Company policy in the market 75 CHAPTER 5 RATIONALE FOR RECOMMENDATIONS 77 5.1 Statement for recommendations at Company 77 CHAPTER 6 OCCUPATIONAL HEALTH AND SAFETY AT THE ENTERPRISE 79 6.1 The aim of occupational health 79 6.2 Organization of occupational health and safety at the enterprise 86 CHAPTER 7 ENVIRONMENTAL ISSUES 92 7.1 Environmental issues in the field 92 7.2 Еnvironmental factors 94 Conclusions 96 References 98 Appendices 10