A software process line for service-oriented applications

Garcia, Cleiton dos Santos; Paludo, Marco; Malucelli, Andreia; Reinehr, Sheila

doi:10.1145/2695664.2695743

Cited by 5 publications

(2 citation statements)

References 18 publications

(21 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [33], a canonical software process family based on the Unified Process (UP) is proposed to support software process tailoring; the UP-process line is constructed based on the CASPER meta-process [10]. In [34], an SPrL is proposed for engineering service-oriented products; an environment is also developed to support the proposed SPrL.…”

Section: Related Researchmentioning

confidence: 99%

“…Table 7 shows the results of evaluating our approach and existing model-driven SPrLE approaches based on their support for these four activities. It should be mentioned that tool-focused approaches [27,30,32] and approaches for proposing general SPrLs for specific domains [33,34] have been excluded from this comparison, as they cannot be considered as specialized engineering approaches for constructing bespoke SPrLs. Results of the comparison are explained below:  Construct validity: The first threat to construct validity is misunderstanding the questions in the post-questionnaire; to deal with this, we added explanations to each measure.…”

Section: Comparative Analysismentioning

confidence: 99%

See 1 more Smart Citation

A Model-Driven Approach for Software Process Line Engineering

Agh

Ramsin

2023

Software

View full text Add to dashboard Cite

It has become increasingly preferable to construct bespoke software development processes according to the specifications of the project at hand; however, defining a separate process for each project is time consuming and costly. One solution is to use a Software Process Line (SPrL), a specialized Software Product Line (SPL) in the context of process definition. However, instantiating an SPrL is a slow and error-prone task if performed manually; an adequate degree of automation is therefore essential, which can be achieved by using a Model-Driven Development (MDD) approach. Furthermore, we have identified specific shortcomings in existing approaches for SPrL Engineering (SPrLE). To address the identified shortcomings, we propose a novel MDD approach specifically intended for SPrLE; this approach can be used by method engineers and project managers to first define an SPrL, and then construct custom processes by instantiating it. The proposed approach uses a modeling framework for modeling an SPrL, and applies transformations to provide a high degree of automation when instantiating the SPrL. The proposed approach addresses the shortcomings by providing an adequate coverage of four activities, including Feasibility analysis, Enhancing the core process, Managing configuration complexity, and Post-derivation enhancement. The proposed approach has been validated through an industrial case study and an experiment; the results have shown that the proposed approach can improve the processes being used in organizations, and is rated highly as to usefulness and ease of use.

show abstract

Section: Related Researchmentioning

confidence: 99%

Section: Comparative Analysismentioning

confidence: 99%

A Model-Driven Approach for Software Process Line Engineering

Agh

Ramsin

2023

Software

View full text Add to dashboard Cite

show abstract

Directions for future research on the integration of SOA, BPM, and BRM

Fischer

Imgrund

Janiesch

et al. 2019

BPMJ

View full text Add to dashboard Cite

Purpose Digital transformation has been changing the economic environment of enterprises in recent years. To remain competitive, they rely on an extensible software architecture, flexible workflow execution, and automated decision management. The concepts of service-oriented architectures (SOA), business process management (BPM), and business rules management (BRM) provide an adequate, yet isolated means of addressing many of these requirements. The paper aims to discuss these issues. Design/methodology/approach This study adapts from established research frameworks to structure the current state of research on the integration of SOA, BPM and BRM. The authors highlight the current research scope, point to disregarded topics and sketch out multidisciplinary research approaches. Findings While the three concepts are often discussed only in isolation or pairwise, approaches that integrate them are scarce. Against this backdrop, this study defines three types of research opportunities and identifies several directions for future research that should be explored from a technological as well as organizational perspective. Given the breadth of open questions, the authors present sources for each area of our research framework, which can serve as starting points for future investigations. Practical implications Except for well-established support for separate tasks and technologies, there is a lack of integrated standards, methods and platforms, which for example enable integrated decision-making across BPM and SOA. Originality/value Our contribution builds on established frameworks and clearly shows that the discussion on the integration of SOA, BPM and BRM cannot yet be regarded as sufficient. The research agenda highlights which areas explicitly benefit from a more precise consideration.

show abstract