Requirements for adopting software process lines

Abstract

A Software Process Line (SPrL) is potentially suitable for constructing software development methodologies by reusing core assets. However, adopting this approach without prior assessment of its suitability can lead to failure. The aim of this paper is to identify a set of requirements that can be used for deciding whether to adopt the SPrL approach in an organization. Identification of the requirements was accomplished in two stages: the characteristics important in method tailoring were first identified via a Systematic Mapping Study (SMS) that focused on analyzing 43 primary studies; the degree of importance of the identified characteristics was then determined using a questionnaire survey in which 31 experts participated. By analyzing the results of the SMS and the survey, we have identified 12 productrelated, 22 project-related, and 10 organization-related requirements. In addition to these requirements, we have also identified two relevant requirements by studying previous research on Software Product Lines (SPL) and Business Process Lines (BPL). The requirements thus identified can help organizations decide on whether to adopt the SPrL approach: the more an organization satisfies the requirements, the more frequently method tailoring occurs in that organization, and hence, the more justified it is to adopt the SPrL approach.

A reference model for software product line capability assessment

“…They face challenges in coordinating and managing this adoption. 7 Therefore, there is a need for assistance and guidance in the provision of a clear road map for improvement of the SPL approach in software organizations. [8][9][10][11][12] Structural approaches, such as process capability maturity models and standards, are developed to assist organizations by providing extensive guidance for improvement.…”

“…Although most software organizations are aware of the potential benefits of it, many of them do not have a clear path to redesign their existing software development processes in line with the SPL approach. They face challenges in coordinating and managing this adoption 7 . Therefore, there is a need for assistance and guidance in the provision of a clear road map for improvement of the SPL approach in software organizations 8–12 …”

A Model-Driven Approach for Software Process Line Engineering

“…Based on this definition, SPrLs focus on identifying the variabilities among a set of processes and modeling them as a core process; the core process is then instantiated to produce a bespoke process. Although the SPrL approach can potentially help define specific processes faster and with less effort [12], its successful implementation requires that organizations first examine its suitability for their specific needs [13]. However, existing SPrL approaches fail to dedicate proper attention to this issue.…”

“…None of the approaches provides mechanisms for examining the suitability and feasibility of SPrLs for the target organization; they suppose that SPrLs have already been deemed as suitable for the target organization. Therefore, they begin by identifying the commonalities and variabilities among the processes; however, adopting the SPrL approach without prior assessment of its suitability can lead to failure [13].…”

“…Feasibility analysis: The feasibility of using an SPrL approach for the organization is examined during DE by a set of requirements specifically defined for this purpose [13].…”