SwePub
Sök i SwePub databas

  Extended search

Träfflista för sökning "L773:2047 7481 OR L773:2047 7473 OR L773:1532 060X "

Search: L773:2047 7481 OR L773:2047 7473 OR L773:1532 060X

  • Result 1-50 of 85
Sort/group result
   
EnumerationReferenceCoverFind
1.
  • Jalali, Samireh, et al. (author)
  • Global software engineering and agile practices : a systematic review
  • 2012
  • In: Journal of Software Maintenance and Evolution. - : John Wiley & Sons, Ltd.. - 1532-060X .- 1532-0618. ; 24:6
  • Journal article (peer-reviewed)abstract
    • Agile practices have received attention from industry as an alternative to plan-driven software development approaches. Agile encourages, for example, small self-organized collocated teams, whereas global software engineering (GSE) implies distribution across cultural, temporal, and geographical boundaries. Hence, combining them is a challenge. A systematic review was conducted to capture the status of combining agility with GSE. The results were limited to peer-reviewed conference papers or journal articles, published between 1999 and 2009. The synthesis was made through classifying the papers into different categories (e.g. publication year, contribution type, research method). At the end, 81 papers were judged as primary for further analysis. The distribution of papers over the years indicated that GSE and Agile in combination has received more attention in the last 5 years. However, the majority of the existing research is industrial experience reports in which Agile practices were modified with respect to the context and situational requirements. The emergent need in this research area is suggested to be developing a framework that considers various factors from different perspectives when incorporating Agile in GSE. Practitioners may use it as a decision-making basis in early phases of software development.
  •  
2.
  • Gren, Lucas, 1984, et al. (author)
  • Agile ways of working: A team maturity perspective
  • 2020
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473 .- 1532-060X. ; 32:6
  • Journal article (peer-reviewed)abstract
    • With the agile approach to managing software development projects comes an increased dependability on well-functioning teams, since many of the practices are built on teamwork. The objective of this study was to investigate if, and how, team development from a group psychological perspective is related to some work practices of agile teams. Data were collected from 34 agile teams (200 individuals) from six software development organizations and one university in both Brazil and Sweden using the Group Development Questionnaire (Scale IV) and the Perceptive Agile Measurement (PAM). The result indicates a strong correlation between levels of group maturity and the two agile practices iterative development and retrospectives. We, therefore, conclude that agile teams at different group development stages adopt parts of team agility differently, thus confirming previous studies but with more data and by investigating concrete and applied agile practices. We thereby add evidence to the hypothesis that an agile implementation and management of agile projects need to be adapted to the group maturity levels of the agile teams.
  •  
3.
  • Gorschek, Tony, et al. (author)
  • Introduction of a Process Maturity Model for Market-driven Product Management and Requirements engineering
  • 2012
  • In: Journal of Software Maintenance and Evolution. - : John Wiley and Sons. - 1532-060X .- 1532-0618. ; 24:1, s. 83-113
  • Journal article (peer-reviewed)abstract
    • The area of software product development of software intensive products has received much attention, especially in the area of requirements engineering and product management. Many companies are faced with new challenges when operating in an environment where potential requirements number in thousands or even tens of thousands, and where a product does not have a customer, but any number of customers or markets. The development organization carries not only all the costs of development, but also takes all the risks. In this environment traditional bespoke requirements engineering, together with traditional process assessment and improvement models fall short as they do not address the unique challenges of a market-driven environment. This paper introduces the Market-driven Requirements Engineering Process Model, aimed at enabling process improvement and process assurance for organizations faced with these new challenges. The model is also validated in the industry through three case studies where the model is used for process assessment and improvement suggestion. Initial results show that the model is appropriate for process improvement for organizations operating in a market-driven environment. In addition, the model was designed to be light weight in terms of low cost and thus adapted not only for large organizations but suitable for small and medium enterprises as well.
  •  
4.
  • Khurum, Mahvish, et al. (author)
  • The software value map—an exhaustive collection of value aspects for the development of software intensive products
  • 2013
  • In: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 25:7, s. 711-741
  • Journal article (peer-reviewed)abstract
    • In software intensive products such as cars or telecom systems, software has traditionally been associated with cost, and there has been no real perception of its value in relation to the entire product offering. However, because software is becoming a larger part of the main competitive advantage, driving innovation and product differentiation, hardware is becoming more standardized, thus the valuation of software is becoming critical. In existing literature, several value constructs and corresponding valuation/measurement solutions needed for making decisions about software product development are presented. However, the contributions are often isolated with respect to a certain perspective such as focusing on product's internal or external quality aspects only. Consequently, a complete view of value constructs relevant from different perspectives required for making decisions about software product development is missing. This paper presents a consolidated view of the software value concept utilizing the major perspectives and introduces a software value map. The created value map was evaluated through an industry case study through the development of impact evaluation patterns, which were subsequently used by professionals in industry, and experiences gathered. During industry evaluation, practitioners found substantial benefits of having a consolidated, vastly improved, and extended value aspect's view of software. Copyright © 2012 John Wiley & Sons, Ltd.
  •  
5.
  • Lagerström, Robert, et al. (author)
  • Increasing software development efficiency and maintainability for complex industrial systems - A case study
  • 2013
  • In: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 25:3, s. 285-301
  • Journal article (peer-reviewed)abstract
    • It is difficult to manage complex software systems. Thus, many research initiatives focus on how to improve software development efficiency and maintainability. However, the trend in the industry is still alarming, software development projects fail, and maintenance is becoming more and more expensive. One problem could be that research has been focusing on the wrong things. Most research publications address either process improvements or architectural improvements. There are few known approaches that consider how architectural changes affect processes and vice versa. One method proposed, called the BusinessArchitectureProcess method, takes these aspects into consideration. In 2007 the method was tested in one case study. Findings in the 2007 case study show that the method is useful, but in need of improvements and further validation. The present paper employs the method in a second case study. The contribution in this paper is thus a second test and validation of the proposed method, and useful method improvements for future use of the method.
  •  
6.
  • Petersen, Kai, et al. (author)
  • Early identification of bottlenecks in very large scale system of systems software development
  • 2014
  • In: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 26:12, s. 1150-1171
  • Journal article (peer-reviewed)abstract
    • System of systems are of high complexity, and for each system, many different requirements are implemented in parallel. Systems are developed with some degree of managerial independence but later on have to work together. In this situation, many requirements are written, implemented, and tested in parallel for different systems that are to be integrated. This makes identifying bottlenecks challenging, and visualizations often used on project level (such as Kanban boards or burndown charts) have to be extended/complemented to cope with the increased complexity. In response to these challenges, the contributions of this study are to propose the following: (i) a visualization for early identification and proactive removal of bottlenecks; (ii) a visualization to check on the success of bottleneck resolution; and (iii) to provide an industry evaluation of the visualizations in a case study of a system of systems developed at Ericsson AB in Sweden. The feedback by the practitioners showed that the visualizations were perceived as useful in improving throughput and lead time. The quantitative analysis showed that the visualizations were able in identifying bottlenecks and showing improvements or the lack thereof. On the basis of the qualitative and quantitative data collected, we conclude that the visualizations are useful in bottleneck identification and resolution.
  •  
7.
  • Shahzad, Khurram, et al. (author)
  • Process warehouses in practice : a goal-driven method for business process analysis
  • 2012
  • In: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 24:3, s. 321-339
  • Journal article (peer-reviewed)abstract
    • Process analysis and improvement, one of the core phases in the business process management life cycle, is reaching the top of the agenda for many enterprises and organizations. An emerging approach to analyzing business processes involves the use of process-oriented data warehouses to collect information about executed processes to enable their detailed analysis and thereby provide bases for possible improvements. However, very little work has been carried out on employing business orientation in the design and utilization of a process warehouse. The approach presented in this study addresses that limitation by proposing a method that relates business goals to the information from the warehouse. To do so, we start by defining a desired goal structure that concerns an existing business process. The obtained goal model is firstly utilized for scoping and designing a corresponding data model for a process warehouse, and further for retrieving the information from the warehouse to examine the fulfillment of the goals of interest. The key benefits of the proposed method are the provision of the relevant and accurate business process information as well as tracing the process-related goals to the process execution data and further to the analysis of the process. As validation of the proposed method, we develop a prototype, and a healthcare process is used as an illustrative example. Also, to demonstrate the method quality, we perform an experiment on the effectiveness of the information access and retrieval.
  •  
8.
  • Šmite, Darja, et al. (author)
  • Lessons learned from transferring software products to India
  • 2012
  • In: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 24:6
  • Journal article (peer-reviewed)abstract
    • Globalization has influenced the way software is developed today, and many software organizations have started to actively utilize resources from around the world. However, these endeavors are recognized as very challenging, and they have attracted a lot of attention in software research in the past decade. Unlike many other research initiatives, which explore the complexities of distributed software development activities, the focus of this paper is on software transfers. Software transfers refer to activities that are moved from one location to another. The authors draw attention to the lessons learned from an empirical investigation of two transfer projects conducted at Ericsson. Both transfers were performed between a site in Sweden and a site in India. The observations outline a set of generic practices that have been found useful for transferring software development within a company. It also highlights a number of challenges to be addressed and a set of corresponding recommendations. Finally, the paper emphasizes the need to identify software products that are suitable for transfers and the need to monitor the long-term effects of transfer.
  •  
9.
  • Borg, Markus (author)
  • TuneR : A Framework for Tuning Software Engineering Tools with Hands-on Instructions in R
  • 2016. - 15
  • In: Journal of Software. - : John Wiley & Sons Ltd. - 2047-7473 .- 2047-7481. ; 28:6, s. 427-459
  • Journal article (peer-reviewed)abstract
    • Numerous tools automating various aspects of software engineering have been developed, and many of the tools are highly configurable through parameters. Understanding the parameters of advanced tools often requires deep understanding of complex algorithms. Unfortunately, suboptimal parameter settings limit the performance of tools and hinder industrial adaptation, but still few studies address the challenge of tuning software engineering tools. We present TuneR, an experiment framework that supports finding feasible parameter settings using empirical methods. The framework is accompanied by practical guidelines of how to use R to analyze the experimental outcome. As a proof-of-concept, we apply TuneR to tune ImpRec, a recommendation system for change impact analysis in a software system that has evolved for more than two decades. Compared with the output from the default setting, we report a 20.9% improvement in the response variable reflecting recommendation accuracy. Moreover, TuneR reveals insights into the interaction among parameters, as well as nonlinear effects. TuneR is easy to use, thus the framework has potential to support tuning of software engineering tools in both academia and industry.
  •  
10.
  • Ahmad, Muhammad Ovais, Associate Professor/Lektor, et al. (author)
  • Early career software developers and work preferences in software engineering
  • 2024
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 36:2
  • Journal article (peer-reviewed)abstract
    • Context: The software engineering researchers and practitioners echoed the needfor investigations to better understand the engineers developing software andservices. In light of current studies, there are significant associations between thepersonalities of software engineers and their work preferences. However, limitedstudies are using psychometric measurements in software engineering.Objective: We aim to evaluate attitudes of early-stage software engineers andinvestigate link between their personalities and work preferences.Method: We collected extensive psychometric data from 303 graduate-levelstudents in Computer Science programs at four Pakistani and one Swedish universityusing Five-Factor Model. The statistical analysis investigated associations betweenvarious personality traits and work preferences.Results: The data support the existence of two clusters of software engineers, one ofwhich is more highly rated across the board. Numerous correlations exist betweenpersonality qualities and the preferred types of employment for software developers.For instance, those who exhibit greater levels of emotional stability, agreeableness,extroversion, and conscientiousness like working on technical activities on a settimetable. Similar relationships between personalities and occupational choices arealso evident in the earlier studies. More neuroticism is reported in femalerespondents than in male respondents. Higher intelligence was demonstrated bythose who worked on the“entire development process”and“technical componentsof the project.”Conclusion: When assigning project tasks to software engineers, managers might usethe statistically significant relationships that emerged from the analysis of personalityattributes. It would be beneficial to construct effective teams by taking personalityfactors like extraversion and agreeableness into consideration. The study techniquesand analytical tools we use may identify subtle relationships and reflect distinctionsacross various groups and populations, making them valuable resources for bothfuture academic research and industrial practice.
  •  
11.
  • Ahmad, Muhammad Ovais, Associate Professor/Lektor, et al. (author)
  • The Pandora's box of social, process, and people debts in software engineering
  • 2024
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 36:2
  • Journal article (peer-reviewed)abstract
    • In software engineering, technical debt (TD) has been widely investigated, but debt regarding social issues, people, and processes has not been explored as much. It should be noted here that we use nontechnical debt (NTD) as an umbrella term to cover social, process, and people debts. Although the number of studies on NTD in software is increasing, the majority of them are descriptive rather than rigorous, and there is no systematic development of cumulative knowledge. As a result, identifying the fundamental causes of NTD and the associated mitigation techniques in software engineering is challenging. Therefore, this study investigates the scientific evidence regarding NTD till date by conducting a systematic mapping review of software engineering research between January 2000 and October 2021. The search strategy resulted in 175 studies, 17 of which were identified as unique and relevant primary papers. The primary studies show that NTD and TD are inextricably linked. In addition, this study also captured a plethora of causes and mitigation strategies for managing NTD and thus makes four important contributions: (i) highlighting state-of-the-art NTD research; (ii) identification of the reported causes and mitigation strategies in the primary papers; and (iii) determination of opportunities for future NTD research.
  •  
12.
  • Al Sabbagh, Khaled, 1987, et al. (author)
  • The connections between group maturity, software development velocity, and planning effectiveness
  • 2018
  • In: Journal of Software-Evolution and Process. - : Wiley. - 2047-7473 .- 2047-7481. ; 30:1
  • Journal article (peer-reviewed)abstract
    • Empirical evidence regarding the connection between group development (maturity) and the success of software development teams is lacking. The purpose of this research is to gain a qualitative and quantitative understanding of how velocity and planning effectiveness of software teams connect to a group development model. The Group Development Questionnaire was given to 19 software developers from 4 work groups to assess their group development maturity. The work groups' responses to the survey were checked for correlation with development velocity and planning effectiveness. Semistructured interviews were conducted with 16 individuals from the same 4 work groups to explore issues about their group maturity and to validate the responses of the interviewees in the Group Development Questionnaire. The measurement of the fourth stage of group development had a strong association with the planning effectiveness measurement, which means that a team with less issues in the fourth phase of group development is more effective in adhering to its plans. On the other hand, group development and velocity showed no significant convergent validity. We conclude that the dynamics within software development teams might correlate to their ability to deliver the expected outcome as planned but not to their ability to develop tasks faster.
  •  
13.
  • Bosch, Jan, 1967, et al. (author)
  • Digital for real: A multicase study on the digital transformation of companies in the embedded systems domain
  • 2021
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 33:5
  • Journal article (peer-reviewed)abstract
    • With digitalization and with technologies such as software, data, and artificial intelligence, companies in the embedded systems domain are experiencing a rapid transformation of their conventional businesses. While the physical products and associated product sales provide the core revenue, these are increasingly being complemented with service offerings, new data-driven services, and digital products that allow for continuous value creation and delivery to customers. However, although there is significant research on digitalization and digital transformation, few studies highlight the specific needs of embedded systems companies and what it takes to transform from a traditional towards a digital company within business domains characterized by high complexity, hardware dependencies, and safety-critical system functionality. In this paper, we capture the difference between what constitutes a traditional and a digital company and we detail the typical evolution path embedded systems companies take when transitioning towards becoming digital companies.
  •  
14.
  • Bosch, Jan, 1967, et al. (author)
  • Ecosystem traps and where to find them
  • 2018
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 30:11
  • Journal article (peer-reviewed)abstract
    • Today, companies operate in business ecosystems where they collaborate, compete, share, and learn from others with benefits such as to present more attractive offerings and sharing innovation costs. With ecosystems being the new way of operating, the ability to strategically reposition oneself to increase or shift power balance is becoming key for competitive advantage. However, companies run into a number of traps when trying to realize strategical changes in their ecosystems. In this paper, we identify 5 traps that companies fall into. First, the “descriptive versus prescriptive trap” is when companies assume that current boundaries between partners are immutable. Second, the “assumptions trap” is when powerful ecosystem partners assume that they understand what others regard as value-adding without validating their assumptions. Third, the “keeping it too simple trap” is when companies overlooks the effort required to align interests. Fourth, the “doing it all at once trap” is when companies disrupt an ecosystem assuming that all partners can change direction at the same time. Finally, the “planning trap” is when companies are unable to move forward without a complete plan. We provide empirical evidence for each trap, and we propose an ecosystem engagement process for how to avoid falling into these.
  •  
15.
  • Britto, Ricardo, 1982-, et al. (author)
  • Onboarding Software Developers and Teams in Three Globally Distributed Legacy Projects : A Multi-Case Study
  • 2018
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 30:4
  • Journal article (peer-reviewed)abstract
    • Onboarding is the process of supporting new employees regarding their social and performance adjustment to their new job. Software companies have faced challenges with recruitment and onboarding of new team members and there is no study that investigates it in a holistic way. In this paper, we conducted a multi-case study to investigate the onboarding of software developers/teams, associated challenges, and areas for further improvement in three globally distributed legacy projects. We employed Bauer's model for onboarding to identify the current state of the onboarding strategies employed in each case. We learned that the employed strategies are semi-formalized. Besides, in projects with multiple sites, some functions are executed locally and the onboarding outcomes may be hard to control. We also learned that onboarding in legacy projects is especially challenging and that decisions to distribute such projects across multiple locations shall be approached carefully. In our cases, the challenges to learn legacy code were further amplified by the project scale and the distance to the original sources of knowledge. Finally, we identified practices that can be used by companies to increase the chances of being successful when onboarding software developers and teams in globally distributed legacy projects.
  •  
16.
  • Bucaioni, Alessio, 1987-, et al. (author)
  • Model-based generation of test scripts across product variants : An experience report from the railway industry
  • 2022
  • In: Journal of Software. - : John Wiley and Sons Ltd. - 2047-7473 .- 2047-7481. ; 34:11
  • Journal article (peer-reviewed)abstract
    • Software product line engineering emerged as an effective approach for the development of families of software-intensive systems in several industries. Although its use has been widely discussed and researched, there are still several open challenges for its industrial adoption and application. One of these is how to efficiently develop and reuse shared software artifacts, which have dependencies on the underlying electrical and hardware systems of products in a family. In this work, we report on our experience in tackling such a challenge in the railway industry and present a model-based approach for the automatic generation of test scripts for product variants in software product lines. The proposed approach is the result of an effort leveraging the experiences and results from the technology transfer activities with our industrial partner Alstom SA in Sweden. We applied and evaluated the proposed approach on the Aventra software product line from Alstom SA. The evaluation showed that the proposed approach mitigates the development effort, development time, and consistency drawbacks associated with the traditional, manual creation of test scripts. We performed an online survey involving 37 engineers from Alstom SA for collecting feedback on the approach. The result of the survey further confirms the aforementioned benefits. © 2022 The Authors.
  •  
17.
  • Bucaioni, Alessio, 1987-, et al. (author)
  • Reference architectures modelling and compliance checking
  • 2022
  • In: Journal of Software. - : WILEY. - 2047-7473 .- 2047-7481.
  • Journal article (peer-reviewed)abstract
    • Reference architectures (RAs) are successfully used to represent families of concrete software architectures in several domains such as automotive, banking, and the Internet of Things. RAs inspire architects when designing concrete architectures, and they help to guarantee compliance with architectural decisions, regulatory requirements, as well as architectural qualities. Despite their importance, reference architectures still suffer from a number of open technical issues, including (i) the lack of a common interpretation, a precise notation for their representation and documentation, and (ii) the lack of conformance mechanisms for checking the compliance of concrete architectures to their related reference architecture, architectural decisions, regulatory requirements, etc. This paper addresses these two issues by introducing a model-driven approach that leverages (i) a domain-independent metamodel for the representation of reference architectures and (ii) the combination of model transformation and weaving techniques for the automatic conformance checking of concrete architectures. We evaluate the applicability, effectiveness, and generalizability of our approach using illustrative examples from the web browsers and automotive domains, including an assessment from an independent practitioner.
  •  
18.
  • Capilla, Rafael, et al. (author)
  • Opportunities for Software Reuse in an Uncertain World : From Past to Emerging Trends
  • 2019
  • In: Journal of Software. - : Wiley. - 2047-7473 .- 2047-7481. ; 31:8
  • Journal article (peer-reviewed)abstract
    • Much has been investigated about software reuse since the software crisis. The development of software reuse methods, implementation techniques, and cost models has resulted in a significant amount of research over years. Nevertheless, the increasing adoption of reuse techniques, many of them subsumed under higher level software engineering processes, and advanced programming techniques that ease the way to reuse software assets, have hidden somehow in the recent years new research trends on the practice of reuse and caused the disappearance of several reuse conferences. Also, new forms of reuse like open data and feature models have brought new opportunities for reuse beyond the traditional software components. From past to present, we summarize in this research the recent history of software reuse, and we report new research areas and forms of reuse according to current needs in industry and application domains, as well as promising research trends for the upcoming years.
  •  
19.
  • Capilla, R., et al. (author)
  • The new era of software reuse
  • 2019
  • In: Journal of Software. - : John Wiley and Sons Ltd. - 2047-7473 .- 2047-7481. ; 31:8
  • Journal article (other academic/artistic)
  •  
20.
  • Castellanos Ardila, Julieth Patricia, Doctoral student, 1976-, et al. (author)
  • Compliance checking of software processes : A systematic literature review
  • 2022
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 34:5
  • Journal article (peer-reviewed)abstract
    • The processes used to develop software need to comply with normative requirements (e.g., standards and regulations) to align with the market and the law. Manualcompliance checking is challenging because there are numerous requirements withchanging nature and different purposes. Despite the importance of automated techniques, there is not any systematic study in this field. This lack may hinder organizations from moving toward automated compliance checking practices. In this paper,we characterize the methods for automatic compliance checking of software processes, including used techniques, potential impacts, and challenges. For this, weundertake a systematic literature review (SLR) of studies reporting methods in thisfield. As a result, we identify solutions that use different techniques (e.g., anthologiesand metamodels) to represent processes and their artifacts (e.g., tasks and roles). Various languages, which have diverse capabilities for managing competing and changingnorms, and agile strategies, are also used to represent normative requirements. Mostsolutions require tool-support concretization and enhanced capabilities to handleprocesses and normative diversity. Our findings outline compelling areas for futureresearch. In particular, there is a need to select suitable languages for consolidating ageneric and normative-agnostic solution, increase automation levels, tool support,and boost the application in practice by improving usability aspects.
  •  
21.
  • Chatzimparmpas, Angelos, 1994-, et al. (author)
  • Maintenance process modeling and dynamic estimations based on Bayesian networks and association rules
  • 2019
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 31:9, s. 1-25
  • Journal article (peer-reviewed)abstract
    • Managing the maintenance process and estimating accurately the effort and duration required for a new release is considered to be a crucial task as it affects successful software project survival and progress over time. In this study, we propose the combination of two well-known machine learning (ML) techniques, Bayesian Networks (BNs), and Association Rules (ARs) for modeling the maintenance process by identifying the relationships among the internal and external quality metrics related to a particular project release to both the maintainability of the project and the maintenance process indicators (i.e., effort and duration). We also exploit Bayesian inference, to test the effect of certain changes in internal and external project factors to the maintainability of a project. We evaluate our approach through a case study on 957 releases of five open source JavaScript applications. The results show that the maintainability of a release, the changes observed between subsequent releases, and the time required between two releases can be accurately predicted from size, complexity, and activity metrics. The proposed combined approach achieves higher accuracy when evaluated against the BN model accuracy.
  •  
22.
  • Dakkak, Anas, et al. (author)
  • Towards AIOps enabled services in continuously evolving software-intensive embedded systems
  • 2024
  • In: Journal of Software: Evolution and Process. - : John Wiley & Sons. - 2047-7481 .- 2047-7473. ; 36:5
  • Journal article (peer-reviewed)abstract
    • Continuous deployment has been practiced for many years by companies developing web- and cloud-based applications. To succeed with continuous deployment, these companies have a strong collaboration culture between the operations and development teams. In addition, these companies use AI, analytics, and big data to assist with time-consuming postdeployment activities such as continuous monitoring and fault identification. Thus, the term AIOps has evolved to highlight the importance and difficulty of maintaining highly available applications in a complex and dynamic environment. In contrast, software-intensive embedded systems often provide customer product-related services, such as maintenance, optimization, and support. These services are critical for these companies as they provide significant revenue and increase customer satisfaction. Therefore, the objective of our study is to gain an in-depth understanding of the impact of continuous deployment on product-related services provided by software-intensive embedded systems companies. In addition, we aim to understand how AIOps can support continuous deployment in the context of software-intensive embedded systems. To address this objective, we conducted a case study at a large and multinational telecommunications systems provider focusing on the radio access network (RAN) systems for 4G and 5G networks. The company provides RAN products and three complementing services: rollout, optimization, and customer support. The results from the case study show that the boundaries between product-related services become blurry with continuous deployment. In addition, product-related services, which were conducted in sequence by independent projects, converge with continuous deployment and become part of the same project. Further, AIOps platforms play an important role in reducing costs and increasing postdeployment activities' efficiency and speed. These results show that continuous deployment has a profound impact on the software-intensive system's provider service organization. The service organization becomes the connection between the R&D organization and the customer. In order to cope with the increased speed of releases, deployment and postdeployment activities need to be largely automated. AIOps platforms are seen as a critical enabler in managing the increasing complexity without increasing human involvement.
  •  
23.
  • Dzhusupova, Rimman, et al. (author)
  • Using artificial intelligence to find design errors in the engineering drawings
  • 2023
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 35:12
  • Journal article (peer-reviewed)abstract
    • Artificial intelligence is increasingly becoming important to businesses because many companies have realized the benefits of applying machine learning (ML) and deep learning (DL) in their operations. ML and DL have become attractive technologies for organizations looking to automate repetitive tasks to reduce manual work and free up resources for innovation. Unlike rule-based automation, typically used for standardized and predictable processes, machine learning, especially deep learning, can handle more complex tasks and learn over time, leading to greater accuracy and efficiency improvements. One of such promising applications is to use AI to reduce manual engineering work. This paper discusses a particular case within McDermott where the research team developed a DL model to do a quality check of complex blueprints. We describe the development and the final product of this case—AI-based software for the engineering, procurement, and construction (EPC) industry that helps to find the design mistakes buried inside very complex engineering drawings called piping and instrumentation diagrams (P&IDs). We also present a cost-benefit analysis and potential scale-up of the developed software. Our goal is to share the successful experience of AI-based product development that can substantially reduce the engineering hours and, therefore, reduce the project's overall costs. The developed solution can also be potentially applied to other EPC companies doing a similar design for complex installations with high safety standards like oil and gas or petrochemical plants because the design errors it captures are common within this industry. It also could motivate practitioners and researchers to create similar products for the various fields within engineering industry.
  •  
24.
  • Fabijan, Aleksander, et al. (author)
  • Experimentation growth: Evolving trustworthy A/B testing capabilities in online software companies
  • 2018
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 30:12
  • Journal article (peer-reviewed)abstract
    • Companies need to know how much value their ideas deliver to customers. One of the most powerful ways to accurately measure this is by conducting online controlled experiments (OCEs). To run experiments, however, companies need to develop strong experimentation practices as well as align their organization and culture to experimentation. The main objective of this paper is to demonstrate how to run OCEs at large scale using the experience of companies that succeeded in scaling. Based on case study research at Microsoft, Booking.com, Skyscanner, and Intuit, we present our main contribution-The Experiment Growth Model. This four-stage model addresses the seven critical aspects of experimentation and can help companies to transform their organizations into learning laboratories where new ideas can be tested with scientific accuracy. Ultimately, this should lead to better products and services.
  •  
25.
  • Gallina, Barbara (author)
  • Quantitative Evaluation of Tailoring within SPICE-compliant Security-informed Safety-oriented Process Lines
  • 2020
  • In: Journal of Software. - Sweden : Wiley. - 2047-7473 .- 2047-7481. ; 32:3
  • Journal article (peer-reviewed)abstract
    • In the context of SPICE‐compliant and (security‐informed) safety processes, efficient process tailoring is necessary due to the increasing proliferation of requirements, which, if not systematised, may become an unmanageable cognitive overload leading to process degradation instead of improvement. Recently, security‐informed safety‐oriented process line engineering (SiSoPLE) has been proposed as a sound solution to systematise common and variable process elements in the context of security‐informed safety‐oriented processes described within security as well as safety‐related standards. SiSoPLE represents an extension of safety‐oriented process line engineering (SoPLE). The gain of the application of SoPLE in terms of efficient tailoring via reuse was measured in a previous work, where the GQM+ Strategies model, an extension of the goal/question/metric (GQM) paradigm, was adopted to develop a measurement model for achieving quantitative evidence. In this paper, we develop further our previously proposed measurement model to achieve quantitative evidence regarding the benefits of using process line engineering extended to SPICE‐compliant security‐informed safety processes. We then apply our extended GQM+ Strategies model on a SPICE for space‐compliant SiSoPL to illustrate and assess its usefulness. Finally, we discuss our findings and provide our perspectives on quantitative evaluation of tailoring in the context of critical‐systems engineering.
  •  
26.
  • Gallina, Barbara, et al. (author)
  • Towards an ontology for process compliance with the (machinery) legislations
  • 2024
  • In: Journal of Software. - : WILEY. - 2047-7473 .- 2047-7481.
  • Journal article (peer-reviewed)abstract
    • Legislations impose requirements on the manufacturing of machinery. Typically, these requirements are interpreted and refined by (domain-specific) technical committees and published in terms of standards. At the company level, these refined requirements are further interpreted, refined, and documented in terms of internal processes. Due to the proliferation of (interdependent) legislations and standards and the consequent increase of the cognitive complexity, at the company level, manual knowledge management is becoming more and more challenging and requires automated decision support. Despite the availability of approaches aimed at automating the decision support, no one offers a satisfactory solution. In this paper, we focus on knowledge management for process compliance and we propose a novel structured ontology. Our ontology aims at mastering (by dividing and conquering via tracing) the cognitive complexity of the compliance problem, when heterogeneous and sometimes geographically distributed knowledge-driven organizational structures (legal department, standardization department, etc.) are involved and need to communicate. We also illustrate the potential usefulness of our proposed ontology in the context of pumps manufacturing and safety process compliance with the Machinery Directive and related harmonized standards including EN 809:1998+A1. Specifically, first, we identify the competencies that characterize departments and interdepartment interactions, then we formulate an initial set of competency questions that translate those identified competencies, then we show how the ontology can be exploited to retrieve the answers to the questions and how the answers can be exploited to build a justification for compliance. Precisely, we propose an argumentation pattern given in two different argumentation notations, and we show how it can be partly instantiated by exploiting the returned answers. The illustration also partly covers the compliance with the Machinery Regulation, expected to replace the Machinery Directive by January 2027. Finally, we sketch our intended future work.
  •  
27.
  • Garousi, Vahid, et al. (author)
  • Exploring the industry's challenges in software testing : An empirical study
  • 2020
  • In: Journal of Software. - : WILEY. - 2047-7473 .- 2047-7481. ; 32:8
  • Journal article (peer-reviewed)abstract
    • Context Software testing is an important and costly software engineering activity in the industry. Despite the efforts of the software testing research community in the last several decades, various studies show that still many practitioners in the industry report challenges in their software testing tasks. Objective To shed light on industry's challenges in software testing, we characterize and synthesize the challenges reported by practitioners. Such concrete challenges can then be used for a variety of purposes, eg, research collaborations between industry and academia. Method Our empirical research method is opinion survey. By designing an online survey, we solicited practitioners' opinions about their challenges in different testing activities. Our dataset includes data from 72 practitioners from eight different countries. Results Our results show that test management and test automation are considered the most challenging among all testing activities by practitioners. Our results also include a set of 104 concrete challenges in software testing that may need further investigations by the research community. Conclusion We conclude that the focal points of industrial work and academic research in software testing differ. Furthermore, the paper at hand provides valuable insights concerning practitioners' "pain" points and, thus, provides researchers with a source of important research topics of high practical relevance.
  •  
28.
  • Hartmann, H., et al. (author)
  • Towards a multi-criteria decision support method for consumer electronics software ecosystems
  • 2016
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 28:6, s. 460-482
  • Journal article (peer-reviewed)abstract
    • Many consumer electronics firms are adopting an ecosystem-centric approach for supporting third-party applications. In an emerging market, a consumer electronics firm may need to create a new ecosystem or adopt a newly developed platform, both which has significant commercial and technical implications. In this paper we identify three types of ecosystems that are used today: vertically integrated hardware/software platforms, closed-source software platforms, and open-source software platforms. We introduce a first step towards a multi-criteria decision support method, which determines what type of ecosystem is most suitable for a specific product category from a software engineering perspective. We use this method to analyze a wide range of consumer electronics products. The analysis shows that the vertically integrated platform type is most suitable for product with a high degree of innovation, and open-source software platforms are more suitable when a large amount of variants are needed. The closed-source software platform type is less suitable for most types of consumer electronics devices. This first step towards a full-fledged decision support method can be used by platform owners to decide whether their platform can also be successfully transferred to another product type.
  •  
29.
  • Hebig, Regina, et al. (author)
  • Hybrid and evolving processes for software and systems—ICSSP 2019 special issue
  • 2021
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 33:1
  • Journal article (other academic/artistic)abstract
    • © 2020 The Authors. Journal of Software: Evolution and Process published by John Wiley & Sons Ltd The volume at hand presents the special issue of the 12th International Conference on Software and Systems Process (ICSSP) 2019, which was held in Montreal, Canada, from May 25 to 26, 2019. ICSSP 2019 is the latest in a series of conferences that have been organized by the International Software and Systems Process Association. In our evolving landscape, many companies are making efforts to move towards new technologies and tools, agile principles, and continuous integration and delivery. In doing so, they find opportunity, flexibility, and strength in evolving towards hybrid processes, which are neither purely traditional nor can count as textbook agile. This special issue focuses on hybrid processes.
  •  
30.
  • Hebig, Regina, et al. (author)
  • The changing balance of technology and process: A case study on a combined setting of model-driven development and classical C coding
  • 2017
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 29:11
  • Journal article (peer-reviewed)abstract
    • © 2017 John Wiley & Sons, Ltd. The increasing flexibility in industry leads to an ecosystem of change, affecting the balance of processes and technology as well as the developers who have to cope with the change. Furthermore, the change itself might impact the ability to use quantitative methods to learn from previous experience. The goal of this study is to better understand the ecosystem of mutual impacts and changes of process and technologies as well as how developers perceive a technology setting and deal with its change. Therefore, we conducted a case study at Ericsson, performing a series of interviews among 6 employees (senior developers and architects). We identified a time line of changes that happened over 7years. A set of observations about the relation between processes and tooling, and observations about developer's perceptions of the technology settings, and their strategy to deal with these changing technology settings. We discuss how the observed change impacts the ability to perform quantitative evaluations of technology and processes. The findings show that a bad choice of technologies can lead to unexpected impact on team dynamics. Furthermore, change happens so regular that it needs to be considered when collecting data for a quantitative evaluation of, eg, productivity.
  •  
31.
  • Helali Moghadam, Mahshid, et al. (author)
  • Machine learning testing in an ADAS case study using simulation-integrated bio-inspired search-based testing
  • 2024
  • In: Journal of Software. - : John Wiley and Sons Ltd. - 2047-7473 .- 2047-7481. ; :5
  • Journal article (peer-reviewed)abstract
    • This paper presents an extended version of Deeper, a search-based simulation-integrated test solution that generates failure-revealing test scenarios for testing a deep neural network-based lane-keeping system. In the newly proposed version, we utilize a new set of bio-inspired search algorithms, genetic algorithm (GA), (Formula presented.) and (Formula presented.) evolution strategies (ES), and particle swarm optimization (PSO), that leverage a quality population seed and domain-specific crossover and mutation operations tailored for the presentation model used for modeling the test scenarios. In order to demonstrate the capabilities of the new test generators within Deeper, we carry out an empirical evaluation and comparison with regard to the results of five participating tools in the cyber-physical systems testing competition at SBST 2021. Our evaluation shows the newly proposed test generators in Deeper not only represent a considerable improvement on the previous version but also prove to be effective and efficient in provoking a considerable number of diverse failure-revealing test scenarios for testing an ML-driven lane-keeping system. They can trigger several failures while promoting test scenario diversity, under a limited test time budget, high target failure severity, and strict speed limit constraints. 
  •  
32.
  • Issa Mattos, David, 1990, et al. (author)
  • The HURRIER process for experimentation in business-to-business mission-critical systems
  • 2023
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 35:5
  • Journal article (peer-reviewed)abstract
    • Continuous experimentation (CE) refers to a set of practices used by software companies to rapidly assess the usage, value, and performance of deployed software using data collected from customers and systems in the field using an experimental methodology. However, despite its increasing popularity in developing web-facing applications, CE has not been studied in the development process of business-to-business (B2B) mission-critical systems. By observing the CE practices of different teams, with a case study methodology inside Ericsson, we were able to identify the different practices and techniques used in B2B mission-critical systems and a description and classification of the four possible types of experiments. We present and analyze each of the four types of experiments with examples in the context of the mission-critical long-term evolution (4G) product. These examples show the general experimentation process followed by the teams and the use of the different CE practices and techniques. Based on these examples and the empirical data, we derived the HURRIER process to deliver high-quality solutions that the customers value. Finally, we discuss the challenges, opportunities, and lessons learned from applying CE and the HURRIER process in B2B mission-critical systems.
  •  
33.
  • Jabangwe, Ronald, et al. (author)
  • A method for investigating the quality of evolving object-oriented software using defects in global software development projects
  • 2016
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 28:8, s. 622-641
  • Journal article (peer-reviewed)abstract
    • Context: Global software development (GSD) projects can have distributed teams that work independently in different locations or team members that are dispersed. The various development settings in GSD can influence quality during product evolution. When evaluating quality using defects as a proxy, the development settings have to be taken into consideration. Objective: The aim is to provide a systematic method for supporting investigations of the implication of GSD contexts on defect data as a proxy for quality. Method: A method engineering approach was used to incrementally develop the proposed method. This was done through applying the method in multiple industrial contexts and then using lessons learned to refine and improve the method after application. Results: A measurement instrument and visualization was proposed incorporating an understanding of the release history and understanding of GSD contexts. Conclusion: The method can help with making accurate inferences about development settings because it includes details on collecting and aggregating data at a level that matches the development setting in a GSD context and involves practitioners at various phases of the investigation. Finally, the information that is produced from following the method can help practitioners make informed decisions when planning to develop software in comparable circumstances. Copyright © 2016 John Wiley & Sons, Ltd. Copyright © 2016 John Wiley & Sons, Ltd.
  •  
34.
  • Jabbari, Ramtin, et al. (author)
  • Towards a benefits dependency network for DevOps based on a systematic literature review
  • 2018
  • In: Journal of Software. - : John Wiley and Sons Ltd. - 2047-7473 .- 2047-7481. ; 30:11
  • Journal article (peer-reviewed)abstract
    • DevOps as a new way of thinking for software development and operations has received much attention in the industry, while it has not been thoroughly investigated in academia yet. The objective of this study is to characterize DevOps by exploring its central components in terms of principles, practices and their relations to the principles, challenges of DevOps adoption, and benefits reported in the peer-reviewed literature. As a key objective, we also aim to realize the relations between DevOps practices and benefits in a systematic manner. A systematic literature review was conducted. Also, we used the concept of benefits dependency network to synthesize the findings, in particular, to specify dependencies between DevOps practices and link the practices to benefits. We found that in many cases, DevOps characteristics, ie, principles, practices, benefits, and challenges, were not sufficiently defined in detail in the peer-reviewed literature. In addition, only a few empirical studies are available, which can be attributed to the nascency of DevOps research. Also, an initial version of the DevOps benefits dependency network has been derived. The definition of DevOps principles and practices should be emphasized given the novelty of the concept. Further empirical studies are needed to improve the benefits dependency network presented in this study. © 2018 John Wiley & Sons, Ltd.
  •  
35.
  • Jalali, Amin, et al. (author)
  • A Hybrid Approach for Aspect-Oriented Business Process Modeling
  • 2018
  • In: Journal of Software. - : Wiley. - 2047-7473 .- 2047-7481. ; 30:8
  • Journal article (peer-reviewed)abstract
    • Separation of concerns has long been an important strategy to deal with complexity when developing a system. Some concerns (like security) are scattered through the whole system, and different modules are tangled to such concerns. These concerns are known as cross‐cutting concerns. When the system in question is a business process, cross‐cutting concerns are aimed at being encapsulated by Aspect‐Oriented Business Process Modeling. However, the state‐of‐the‐art techniques in this field lack efficient mechanisms that (1) support composition of cross‐cutting concerns that can be defined in parallel to (a part of) a process model and (2) enable specifying both mandatory and optional cross‐cutting concerns. To address these limitations, this paper proposes a new Aspect‐Oriented Business Process Modeling approach. The approach is hybrid since it is based on declarative rules to relate imperative cross‐cutting concerns and imperative business process models. The approach is explained, formally grounded with precise semantics, and used accordingly to implement the artifacts that support modeling and enactment of business processes in the proposed fashion as a proof of concept. In addition, the approach is evaluated on the basis of the Technology Acceptance Model during a workshop session. The result shows that participants perceived the approach usable and easy to use.
  •  
36.
  • John, Meenu Mary, et al. (author)
  • Towards an AI-driven business development framework: A multi-case study
  • 2023
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 35:6
  • Journal article (peer-reviewed)abstract
    • Artificial intelligence (AI) and the use of machine learning (ML) and deep learning (DL) technologies are becoming increasingly popular in companies. These technologies enable companies to leverage big quantities of data to improve system performance and accelerate business development. However, despite the appeal of ML/DL, there is a lack of systematic and structured methods and processes to help data scientists and other company roles and functions to develop, deploy and evolve models. In this paper, based on multi-case study research in six companies, we explore practices and challenges practitioners experience in developing ML/DL models as part of large software-intensive embedded systems. Based on our empirical findings, we derive a conceptual framework in which we identify three high-level activities that companies perform in parallel with the development, deployment and evolution of models. Within this framework, we outline activities, iterations and triggers that optimize model design as well as roles and company functions. In this way, we provide practitioners with a blueprint for effectively integrating ML/DL model development into the business to achieve better results than other (algorithmic) approaches. In addition, we show how this framework helps companies solve the challenges we have identified and discuss checkpoints for terminating the business case.
  •  
37.
  • Jolak, Rodi, et al. (author)
  • Design thinking and creativity of colocated versus globally distributed software developers
  • 2021
  • In: Journal of Software-Evolution and Process. - : Wiley. - 2047-7473 .- 2047-7481.
  • Journal article (peer-reviewed)abstract
    • Designing software is an activity in which software developers think and make design decisions that shape the structure and behavior of software products. Designing software is one of the least understood software engineering activities. In a collaborative design setting, various types of distances can lead to challenges and effects that potentially affect how software is designed. To contribute to a better understanding of collaborative software design, we investigate how communication gaps caused by social and geographic distances affect its design thinking and the creativity of its discussions. To this end, we conducted a multiple-case study exploring the design thinking and creativity of colocated and distributed software developers in a collaborative design setting. Compared with colocated developers, distributed developers spend less time on exploring the problem space, which could be related to different sociotechnical challenges, such as lack of awareness and common understanding. Distributed development does not seem to affect the creativity of their activities. Developers engaging in collaborative design need to be aware that problem space exploration is reduced in a distributed setting. Unless distributed teams take compensatory measures, this could adversely affect the development. Regarding the effect distance has on creativity, our results are inconclusive and further studies are needed.
  •  
38.
  • Khelladi, Djamel Eddine, et al. (author)
  • Coadapting multidimension process properties
  • 2017
  • In: Journal of Software: Evolution and Process, 29 (11). - : Wiley. - 2047-7481 .- 2047-7473.
  • Conference paper (peer-reviewed)abstract
    • © 2017 John Wiley & Sons, Ltd. In the last decades, process verification has been intensively addressed and has become an essential activity to correct and to remove errors before process execution. Typical process verification ecosystems propose to express properties to be verified on the process. A property expresses a desired behavior that must hold or not in the process execution. Processes during their lifespan are continuously adapted for several purposes: enriching, correcting, and refactoring the process. When a process is adapted, the existing properties must naturally be rechecked to ensure that no errors have been introduced, ie, the properties still hold. However, the properties may become outdated and must be coadapted w.r.t. the adapted process before to be rechecked. Otherwise, the verification may raise false alarms or may not detect newly introduced errors. In this paper, we propose a coadaptation approach of properties while considering process adaptation for the different dimensions, namely, control flow, object flow, resources, and timing. We systematically studied process changes in the multiple dimensions to identify those that do impact properties and for which we propose resolution strategies. Our preliminary evaluation shows that our resolutions strategies allow to support users in correctly coadapting impacted properties.
  •  
39.
  • Khurum, Mahvish, et al. (author)
  • Extending value stream mapping through waste definition beyond customer perspective
  • 2014
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 26:12, s. 1074-1105
  • Journal article (peer-reviewed)abstract
    • Value Stream Mapping is one of the several Lean practices, which has recently attracted interest in the software engineering community. In other contexts (such as military, health, production), Value Stream Mapping has achieved considerable improvements in processes and products. The goal is to also leverage on these benefits in the software intensive product development context. The primary contribution is that we are extending the definition of waste to fit in the software intensive product development context. As traditionally in Value Stream Mapping everything that is not considered valuable is waste, we do this practically by looking at value beyond the customer perspective, and using the Software Value Map. A detailed illustration, via application in an industrial case at Ericsson AB, demonstrates usability and usefulness of the proposed extension. The case study results consist of two parts. First, the instantiation and motivations for selecting certain strategies have been provided. Second, the outcome of the value stream map is described in detail. Overall, the conclusion is that this case study indicates that Value Stream Mapping and the integration with the Software Value Map is useful in a software intensive product development context. In a retrospective the value stream approach was perceived positively by the practitioners with respect to process and outcome.
  •  
40.
  • Lenberg, Per, 1976, et al. (author)
  • Misaligned values in software engineering organizations
  • 2019
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 31:3
  • Journal article (peer-reviewed)abstract
    • The values of software organizations are crucial for achieving high performance; in particular, agile development approaches emphasize their importance. Researchers have thus far often assumed that a specific set of values, compatible with the development methodologies, must be adopted homogeneously throughout the company. It is not clear, however, to what extent such assumptions are accurate. Preliminary findings have highlighted the misalignment of values between groups as a source of problems when engineers discuss their challenges. Therefore, in this study, we examine how discrepancies in values between groups affect software companies' performance. To meet our objectives, we chose a mixed method research design. First, we collected qualitative data by interviewing fourteen (N = 14) employees working in four different organizations and processed it using thematic analysis. We then surveyed seven organizations (N = 184). Our analysis indicated that value misalignment between groups is related to organizational performance. The aligned companies were more effective, more satisfied, had higher trust, and fewer conflicts. Our efforts provide encouraging findings in a critical software engineering research area. They can help to explain why some companies are more efficient than others and, thus, point the way to interventions to address organizational challenges.
  •  
41.
  • Lenberg, Per, et al. (author)
  • Qualitative software engineering research : Reflections and guidelines
  • 2024
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 36:6
  • Research review (peer-reviewed)abstract
    • Researchers are increasingly recognizing the importance of human aspects in software development. Because qualitative methods are used to explore human behavior in-depth, we believe that studies using such methods will become more common. Existing qualitative software engineering guidelines do not cover the full breadth of qualitative methods and the knowledge on how to use them like in social sciences. The purpose of this study was to extend the software engineering community's current body of knowledge regarding available qualitative methods and their quality assurance frameworks and to provide recommendations and guidelines for their use. With the support of an epistemological argument and a survey of the literature, we suggest that future research would benefit from (1) utilizing a broader set of research methods, (2) more strongly emphasizing reflexivity, and (3) employing qualitative guidelines and quality criteria. We present an overview of three qualitative methods commonly used in social sciences but rarely seen in software engineering research, namely interpretative phenomenological analysis, narrative analysis, and discourse analysis. Furthermore, we discuss the meaning of reflexivity in relation to the software engineering context and suggest means of fostering it. Our paper will help software engineering researchers better select and then guide the application of a broader set of qualitative research methods. © 2023 John Wiley & Sons, Ltd.
  •  
42.
  • Li Helgesson, Yeni, et al. (author)
  • A review of methods for evaluation of maturity models for process improvement
  • 2012
  • In: Journal of Software Maintenance and Evolution: Research and Practice. - : Wiley. - 1532-060X. ; 24, s. 436-454
  • Journal article (peer-reviewed)abstract
    • Maturity models are widely used in process improvement. The users of a maturity model should be confident that the weak points of the assessed processes can be found, and that the most valuable changes are introduced. Therefore, the evaluation of maturity models is an important activity. In this paper, a mapping study of the literature on the evaluation of maturity models is presented. Two databases are searched resulting in a set of relevant papers. The identified papers can be classified according to six categories, namely the maturity model under evaluation, type of evaluation, relation of the evaluators/authors to the maturity model, level of objectivity, main purpose of the paper, and size of study. Further, a framework of different evaluations of maturity models is developed, and the relevant papers are mapped to the framework. Finally, the relevant research on the evaluation of the maturity models in the Capability Maturity Model family is discussed in more detail. The result of this mapping study is a clear overview of how the evaluation of maturity models has been done, and some discussions are provided for further research on the evaluation of commonly used or newly developed maturity models.
  •  
43.
  • Lindholm, Christin (author)
  • Involving user perspective in a software risk management process
  • 2015
  • In: Journal of software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 27:12, s. 953-975
  • Journal article (peer-reviewed)abstract
    • More and more user groups are using medical devices. Heart starters are, for example, available in public places and used by non-professionals. Different mobile medical applications, designed to help people manage their own health, are now being added to the medical device spectra. Users handling medical devices make errors, but by involving users in the risk management process, it is possible to lower the risk of these errors. This paper presents an evaluation of the value of complementing a traditional risk management process with an emphasised user perspective. A medical device software risk management framework is being designed, and the risk management process should be regarded as the first part of the framework. The main goal of the evaluated risk management process is to integrate users and user perspective into the risk management process. The results indicate that the use of use cases as input at risk meetings makes the discussions more focused, saving effort and time. When users attend the risk meetings, user perspective and domain knowledge are brought into the process, affecting risk identification and risk assessment. The results also show that the use of usability testing gives valuable input to the risk management process.
  •  
44.
  • Martini, Antonio, 1982, et al. (author)
  • A multiple case study on the inter-group interaction speed in large, embedded software companies employing agile
  • 2016
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 28:1, s. 4-26
  • Journal article (peer-reviewed)abstract
    • The adoption of Agile Software Development in large companies is a recent phenomenon of great interest both for researchers and practitioners. Although intra-team interaction is well supported by established agile practices, the critical interaction between the agile team and other parts of the organization is still unexplored in literature. Such interactions slow down the development, hindering the achievement of business goals based on speed: short time to market, quick replication of products of a product-line, and reaction time for product evolution.We have employed a two-year long multiple-case case-study, collecting data through interviews and a survey in three large companies developing embedded software. Through a combination of qualitative and quantitative analysis, we have found strong evidence that interaction challenges between the development team and other groups in the organization hinder speed and are widespread in the organizations.This paper also identifies current practices in use at the studied companies and provides detailed guidelines for novel solutions in the investigated domain. Such practices are called boundary-spanning activities in information system research and coordination theory. We present a comparison between large embedded software companies employing agile and developing a line of products based on reused assets and agile companies developing pure software. We highlight specific contextual factors and areas where novel spanning activities are needed for mitigating the interaction challenges hindering speed.
  •  
45.
  • Martini, Antonio, 1982, et al. (author)
  • On the interest of architectural technical debt: Uncovering the contagious debt phenomenon
  • 2017
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 29:10
  • Journal article (peer-reviewed)abstract
    • A known problem in large software companies is to balance the prioritization of short-term and long-term business goals. As an example, architecture suboptimality (Architectural Technical Debt), incurred to deliver fast, might hinder future feature development. However, some technical debt generates more interest to be paid than other. We conducted a multi-phase, multiple-case embedded case study comprehending 9 sites at 6 large international software companies. We have investigated which architectural technical debt items generate more interest , how the interest occurs during software development and which costly extra-activities are triggered as a result. We presented a taxonomy of the most dangerous items identified during the qualitative investigation and a model of their effects that can be used for prioritization, for further investigation and as a quality model for extracting more precise and context-specific metrics. We found that some architectural technical debt items are contagious, causing the interest to be not only fixed, but potentially compound, which leads to the hidden growth of interest (possibly exponential). We found important factors to be monitored to refactor the debt before it becomes too costly. Instances of these phenomena need to be identified and stopped before the development reaches a crises.
  •  
46.
  • Minhas, Nasir Mehmood, et al. (author)
  • A Systematic Mapping of Test Case Generation Techniques Using UML Interaction Diagrams
  • 2020
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 32:6
  • Research review (peer-reviewed)abstract
    • Testing plays a vital role for assuring software quality. Among the activities performed during testing process, test cases generation is a challenging and labor intensive task. Test case generation techniques based on UML models are getting the attention of researchers and practitioners. This study provides a systematic mapping of test case generation techniques based on interaction diagrams. The study compares the test case generation techniques, regarding their capabilities and limitations, and it also assesses the reporting quality of the primary studies. It has been revealed that UML interaction diagrams based techniques are mainly used for integration testing. The majority of the techniques are using sequence diagrams as input models, while some are using collaboration. A notable number of techniques are using interaction diagram along with some other UML diagram for test case generation. These techniques are mainly focusing on interaction, scenario, operational, concurrency, synchronization and deadlock related faults.From the results of this study, we can conclude that the studies presenting test case generation techniques using UML interaction diagrams failed to illustrate the use of rigorous methodology, and these techniques did not demonstrate the empirical evaluation in an industrial context. Our study revealed the need for tool support to facilitate the transfer of solutions to industry.
  •  
47.
  • Minhas, Nasir Mehmood, et al. (author)
  • Using goal-question-metric to Compare Research and Practice Perspectives on Regression Testing
  • 2023
  • In: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 35:2
  • Journal article (peer-reviewed)abstract
    • Regression testing is challenging because of its complexity and the amount of effort and time it requires, especially in large-scale environments with continuous integration and delivery. Regression test selection and prioritization techniques have been proposed in the literature to address the regression testing challenges, but adoption rates of these techniques in industry are not encouraging. One of the possible reasons could be the disparity in the regression testing goals in industry and literature. This work compares the research perspective to industry practice on regression testing goals, corresponding information needs, and metrics required to evaluate these goals. We have conducted a literature review of 44 research papers and a survey with 56 testing practitioners. The survey comprises 11 interviews and 45 responses to an online questionnaire. We identified that industry and research accentuate different regression testing goals. For instance, the literature emphasizes increasing the fault detection rates of test suites and early identification of critical faults. In contrast, the practitioners' focus is on test suite maintenance, controlled fault slippage, and awareness of changes. Similarly, the literature suggests maintaining information needs from test case execution histories to evaluate regression testing techniques based on various metrics, whereas, at large, the practitioners do not use the metrics suggested in the literature. To bridge the research and practice gap, based on the literature and survey findings, we have created a goal-question-metric (GQM) model that maps the regression testing goals, associated information needs, and metrics from both perspectives. The GQM model can guide researchers in proposing new techniques closer to industry contexts. Practitioners can benefit from information needs and metrics presented in the literature and can use GQM as a tool to follow their regression testing goals. 
  •  
48.
  •  
49.
  • Muhammad Ali Shah, Syed, et al. (author)
  • Towards a Hybrid Testing Process Unifying Exploratory Testing and Scripted Testing
  • 2014
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 26:2, s. 220-250
  • Journal article (peer-reviewed)abstract
    • Context: Given the current state of the art in research, practitioners are faced with the challenge of choosing scripted testing (ST) or exploratory testing (ET). Objective: This study aims at systematically incorporating strengths of ET and ST in a hybrid testing process to overcome the weaknesses of each. Method: We utilized systematic review and practitioner interviews to identify strengths and weaknesses of ET and ST. Strengths of ET were mapped to weaknesses of ST, and vice versa. Noblit and Hare’s Lines of Argument method was used for data analysis. The results of the mapping were used as input to co-design a hybrid process with experienced practitioners. Results: We found a clear need to create a hybrid process as: 1) both ST and ET provide strengths and weaknesses and these depend on some particular conditions, which prevents preference of one approach to another, and 2) the mapping showed that it is possible to address the weaknesses in one process by the strengths of the other in a hybrid form. With the input from literature and industry experts a flexible and iterative hybrid process was designed. Conclusions: Practitioners can clearly benefit from using a hybrid process given the mapping of advantages and disadvantages.
  •  
50.
  • Mårtensson, T., et al. (author)
  • Test activities in the continuous integration and delivery pipeline
  • 2019
  • In: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473. ; 31:4
  • Journal article (peer-reviewed)abstract
    • Based on 25 interviews with participants from four case study companies that develop large-scale software embedded systems, this paper presents the Test Activity Stakeholders (TAS) model. The TAS model shows how the continuous integration and delivery pipeline can be designed to include test activities that support four stakeholder interests: “Check changes,” “Secure stability,” “Measure progress,” and “Verify compliance.” The model is developed to show how each of the stakeholder interests are best supported by unit/component tests or system tests, by automated testing or manual testing and by tests executed in simulated environments or on real hardware. The TAS model may serve as a starting point for companies when evaluating and designing their continuous integration and delivery pipeline. The validation of the TAS model included twelve individuals from three case study companies. The validation showed that the TAS model is actionable and useful in practice, enabling the identification of stakeholders and showing where improvement efforts should be focused in order to support all stakeholder interests in the continuous integration and delivery pipeline.
  •  
Skapa referenser, mejla, bekava och länka
  • Result 1-50 of 85
Type of publication
journal article (81)
research review (3)
artistic work (1)
conference paper (1)
Type of content
peer-reviewed (79)
other academic/artistic (6)
Author/Editor
Wohlin, Claes (6)
Gallina, Barbara (5)
Hebig, Regina (4)
Šmite, Darja (4)
Höst, Martin (3)
Gren, Lucas, 1984 (3)
show more...
Pelliccione, Patrizi ... (2)
Saadatmand, Mehrdad, ... (2)
Inayat, Irum (2)
Wnuk, Krzysztof, 198 ... (2)
Muccini, Henry (2)
Feldt, Robert (2)
Ahmad, Muhammad Ovai ... (2)
Martini, Antonio, 19 ... (2)
Nyström, Staffan (2)
Zdravkovic, Jelena (1)
Staron, Miroslaw, 19 ... (1)
Weyns, Danny (1)
Olsson, Thomas (1)
Hartmann, H. (1)
Saadatmand, Mehrdad (1)
Helali Moghadam, Mah ... (1)
Unterkalmsteiner, Mi ... (1)
Abrahamsson, P. (1)
Wang, X. F. (1)
Karlsson, Göran (1)
Capilla, R. (1)
Viscusi, Gianluigi (1)
Börstler, Jürgen (1)
Ciccozzi, Federico, ... (1)
Lisper, Björn (1)
Cicchetti, Antonio (1)
Felderer, Michael, 1 ... (1)
Larsson, Mats (1)
Johannesson, Paul (1)
Torkar, Richard (1)
Gorschek, Tony, 1972 ... (1)
Di Ruscio, D. (1)
Moe, Nils Brede (1)
Nilsson, Christer (1)
Feldt, Robert, 1972 (1)
Ahmad, Iftikhar (1)
Gustavsson, Tomas, 1 ... (1)
Qayum, Fawad (1)
Axelsson, Jakob (1)
Wohlrab, Rebekka, 19 ... (1)
Bjarnason, Elizabeth (1)
Seyed Jalaleddin, Mo ... (1)
Al Sabbagh, Khaled, ... (1)
Meding, Wilhelm (1)
show less...
University
Blekinge Institute of Technology (28)
Chalmers University of Technology (20)
Mälardalen University (13)
University of Gothenburg (12)
Malmö University (9)
Lund University (8)
show more...
RISE (7)
Royal Institute of Technology (6)
Stockholm University (3)
Linnaeus University (3)
Linköping University (2)
Karlstad University (2)
Mid Sweden University (1)
show less...
Language
English (85)
Research subject (UKÄ/SCB)
Natural sciences (76)
Engineering and Technology (23)
Social Sciences (7)

Year

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Close

Copy and save the link in order to return to this view