Implementation issues in product line scoping

Often product line engineering is treated similar to the waterfall model in traditional software engineering, i.e., the different phases (scoping, analysis, architecting, implementation) are treated as if they could be clearly separated and would follow each other in an ordered fashion. However, in practice strong interactions between the individual phases become apparent. In particular, how implementation is done has a strong impact on economic aspects of the project and thus how to adequately plan it. Hence, assessing these relationships adequately in the beginning has a strong impact on performing a product line project right. In this paper we present a framework that helps in exactly this task. It captures on an abstract level the relationships between scoping information and implementation aspects and thus allows to provide rough guidance on implementation aspects of the project. We will also discuss the application of our framework to a specific industrial project

How Do Real Options Concepts Fit in Agile Requirements Engineering?

Agile requirements engineering is driven by creating business value for the client and heavily involves the client in decision-making under uncertainty. Real option thinking seems to be suitable in supporting the client’s decision making process at inter-iteration time. This paper investigates the fit between real option thinking and agile requirements engineering. We first look into previously published experiences in the agile software engineering literature to identify (i) ‘experience clusters’ suggesting the ways in which real option concepts fit into the agile requirements process and (ii) ‘experience gaps’ and under-researched agile requirements decision-making topics which require further empirical studies. Furthermore, we conducted a cross-case study in eight agile development organizations and interviewed 11 practitioners about their decision-making process. The results suggest that options are almost always identified, reasoned about and acted upon. They are not expressed in quantitative terms, however, they are instead explicitly or implicitly taken\ud into account during the decision-making process at interiteration time

PuLSE-I: Deriving instances from a product line infrastructure

Reusing assets during application engineering promises to improve the efficiency of systems development. However, in order to benefit from reusable assets, application engineering processes must incorporate when and how to use the reusable assets during single system development. However, when and how to use a reusable asset depends on what types of reusable assets have been created.Product line engineering approaches produce a reusable infrastructure for a set of products. In this paper, we present the application engineering process associated with the PuLSE product line software engineering method - PuLSE-I. PuLSE-I details how single systems can be built efficiently from the reusable product line infrastructure built during the other PuLSE activities

Scoping study of the feasibility of developing a software tool to assist designers of pedestrian crossing places

This report is the outcome of a scoping study of how guidance can be provided for practising highway engineers in designing informal pedestrian crossing facilities. The main component of this report is an analysis by an IT consultant of a range of mechanisms for delivery of this. The study was informed by the opinions of a group of practitioners who have a direct interest in the provision of pedestrian facilities. These results are placed in context and their consequences are explored in the first part of the report

Towards a human resources management approach in supply chain management

Supply chain management (SCM) has grown as a discipline since the field attracted attention in the 1980s. However, it is observed that effective implementation of SCM is limited because the current focus is too task-based and information-centric. The concept is often conflated, in practice, with subcontractor management, where numerical flexibility is pertinent. At the same time, consideration of human resources management (HRM) in SCM has been limited. Strategic fit within supply chains tends to emphasise taskbased numerical flexibility, rather than genuine consideration and development of human resources. On the other hand, HRM has, until recently, rarely taken into account interorganisational characteristics that typify the construction industry. Therefore, this research intends to plug the gap by examining the use of human resources in construction supply chains, with a view of developing good practice for HRM in construction SCM. To achieve this, a two-phase research methodology comprising a scoping phase and case study phase will be ensued