Wyniki wyszukiwania - BazTech

1

Value-based Software Engineering: A Systematic Mapping Study

Salleh Norsaremah, Mendes Emilia, Mendes Fabiana, Lekamlage Charitha Dissanayake, Petersen Kai

e-Informatica Software Engineering Journal

|

2023

|

Vol. 17, nr 1

art. no. 230106

EN

Background: Integrating value-oriented perspectives into the principles and practices of software engineering is fundamental to ensure that software development activities address key stakeholders’ views and also balance short-and long-term goals. This is put forward in the discipline of value-based software engineering (VBSE) Aim: This study aims to provide an overview of VBSE with respect to the research efforts that have been put into VBSE. Method: We conducted a systematic mapping study to classify evidence on value definitions, studies’ quality, VBSE principles and practices, research topics, methods, types, contribution facets, and publication venues. Results: From 143 studies we found that the term “value” has not been clearly defined in many studies. VB Requirements Engineering and VB Planning and Control were the two principles mostly investigated, whereas VB Risk Management and VB People Management were the least researched. Most studies showed very good reporting and relevance quality, acceptable credibility, but poor in rigour. Main research topic was Software Requirements and case study research was the method used the most. The majority of studies contribute towards methods and processes, while very few studies have proposed metrics and tools.Conclusion: We highlighted the research gaps and implications for research and practice to support VBSE.

2

A Systematic Reuse Process for Automated Acceptance Tests: Construction and Elementary Evaluation

Irshad Mohsin, Petersen Kai

e-Informatica Software Engineering Journal

|

2021

|

Vol. 15, nr 1

133--162

EN

Context: Automated acceptance testing validates a product’s functionality from the customer’s perspective. Text-based automated acceptance tests (AATs) have gained popularity because they link requirements and testing. Objective: To propose and evaluate a cost-effective systematic reuse process for automated acceptance tests. Method: A systematic approach, method engineering, is used to construct a systematic reuse process for automated acceptance tests. The techniques to support searching, assessing, adapting the reusable tests are proposed and evaluated. The constructed process is evaluated using (i) qualitative feedback from software practitioners and (ii) a demonstration of the process in an industry setting. The process was evaluated for three constraints: performance expectancy, effort expectancy, and facilitating conditions. Results: The process consists of eleven activities that support development for reuse, development with reuse, and assessment of the costs and benefits of reuse. During the evaluation, practitioners found the process a useful method to support reuse. In the industrial demonstration, it was noted that the activities in the solution helped in developing an automated acceptance test with reuse faster than creating a test from scratch i.e., searching, assessment and adaptation parts. Conclusion: The process is found to be useful and relevant to the industry during the preliminary investigation.

3

Usage, Retention, and Abandonment of Agile Practices: A Survey and Interviews Results

Nurdiani Indira, Börstler Jürgen, Fricker Samuel, Petersen Kai

e-Informatica Software Engineering Journal

|

2019

|

Vol. 13, nr 1

7--35

EN

Background: A number of Agile maturity models (AMMs) have been proposed to guide software organizations in their adoption of Agile practices. Typically the AMMs suggest that higher maturity levels are reached by gradually adding more practices. However, recent research indicates that certain Agile practices, like test-driven development and continuous integration, are being abandoned. Little is known on the rationales for abandoning Agile practices. Aim: We aim to identify which Agile practices are abandoned in industry, as well as the reasons for abandoning them. Method: We conducted a web survey with 51 respondents and interviews with 11 industry practitioners with experience in Agile adoption to investigate why Agile practices are abandoned. Results: Of the 17 Agile practices that were included in the survey, all have been abandoned at some point. Nevertheless, respondents who retained all practices as well as those who abandoned one or more practices, perceived their overall adoption of Agile practices as successful. Conclusion: Going against the suggestions of the AMMs, i.e. abandoning Agile one or more practices, could still lead to successful outcomes. This finding indicates that introducing Agile practices gradually in a certain order, as the AMMs suggest, may not always be suitable in different contexts.