| 1. |
- Borg, Markus, et al.
(författare)
-
Software Engineers' Information Seeking Behavior in Change Impact Analysis : An Interview Study
- 2017
-
Ingår i: IEEE International Conference on Program Comprehension. - : IEEE Computer Society. - 9781538605356 ; , s. 12-22, s. 12-22
-
Konferensbidrag (refereegranskat)abstract
- Software engineers working in large projects must navigate complex information landscapes. Change Impact Analysis (CIA) is a task that relies on engineers' successful information seeking in databases storing, e.g., source code, requirements, design descriptions, and test case specifications. Several previous approaches to support information seeking are task-specific, thus understanding engineers' seeking behavior in specific tasks is fundamental. We present an industrial case study on how engineers seek information in CIA, with a particular focus on traceability and development artifacts that are not source code. We show that engineers have different information seeking behavior, and that some do not consider traceability particularly useful when conducting CIA. Furthermore, we observe a tendency for engineers to prefer less rigid types of support rather than formal approaches, i.e., engineers value support that allows flexibility in how to practically conduct CIA. Finally, due to diverse information seeking behavior, we argue that future CIA support should embrace individual preferences to identify change impact by empowering several seeking alternatives, including searching, browsing, and tracing. © 2017 IEEE.
|
|
| 2. |
- Jonsson, Leif, et al.
(författare)
-
Automated Bug Assignment: Ensemble-based Machine Learning in Large Scale Industrial Contexts
- 2015
-
Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1573-7616 .- 1382-3256. ; 21:4
-
Tidskriftsartikel (refereegranskat)abstract
- Bug report assignment is an important part of software maintenance. In particular, incorrect assignments of bug reports to development teams can be very expensive in large software development projects. Several studies propose automating bug assignment techniques using machine learning in open source software contexts, but no study exists for large-scale proprietary projects in industry. The goal of this study is to evaluate automated bug assignment techniques that are based on machine learning classification. In particular, we study the state-of-the-art ensemble learner Stacked Generalization (SG) that combines several classifiers. We collect more than 50,000 bug reports from five development projects from two companies in different domains. We implement automated bug assignment and evaluate the performance in a set of controlled experiments. We show that SG scales to large scale industrial application and that it outperforms the use of individual classifiers for bug assignment, reaching prediction accuracies from 50 % to 89 % when large training sets are used. In addition, we show how old training data can decrease the prediction accuracy of bug assignment. We advice industry to use SG for bug assignment in proprietary contexts, using at least 2,000 bug reports for training. Finally, we highlight the importance of not solely relying on results from cross-validation when evaluating automated bug assignment.
|
|
| 3. |
- Linåker, Johan, et al.
(författare)
-
Sustaining Open Data as a Digital Common - Design principles for Common Pool Resources applied to Open Data Ecosystems
- 2022
-
Ingår i: ACM International Conference Proceeding Series. 7 September 2022, Article number 10. - New York, NY, USA : Association for Computing Machinery. - 9781450398459
-
Konferensbidrag (refereegranskat)abstract
- Motivation. Digital commons is an emerging phenomenon and of increasing importance, as we enter a digital society. Open data is one example that makes up a pivotal input and foundation for many of today's digital services and applications. Ensuring sustainable provisioning and maintenance of the data, therefore, becomes even more important. Aim. We aim to investigate how such provisioning and maintenance can be collaboratively performed in the community surrounding a common. Specifically, we look at Open Data Ecosystems (ODEs), a type of community of actors, openly sharing and evolving data on a technological platform. Method. We use Elinor Ostrom's design principles for Common Pool Resources as a lens to systematically analyze the governance of earlier reported cases of ODEs using a theory-oriented software engineering framework. Results. We find that, while natural commons must regulate consumption, digital commons such as open data maintained by an ODE must stimulate both use and data provisioning. Governance needs to enable such stimulus while also ensuring that the collective action can still be coordinated and managed within the frame of available maintenance resources of a community. Subtractability is, in this sense, a concern regarding the resources required to maintain the quality and value of the data, rather than the availability of data. Further, we derive empirically-based recommended practices for ODEs based on the design principles by Ostrom for how to design a governance structure in a way that enables a sustainable and collaborative provisioning and maintenance of the data. Conclusion. ODEs are expected to play a role in data provisioning which democratize the digital society and enables innovation from smaller commercial actors. Our empirically based guidelines intend to support this development.
|
|
| 4. |
- Skoglund, Mats, et al.
(författare)
-
A case study of the class firewall regression test selection technique on a large scale distributed software system
- 2005
-
Ingår i: 2005 International Symposium on Empirical Software Engineering (ISESE), Proceedings. - NEW YORK : IEEE. - 9780780395084 - 0780395077 ; , s. 74-83
-
Konferensbidrag (refereegranskat)abstract
- Regression testing is expensive and may consume much of organizations' software development budgets. Thus, it is of interest to reduce the total time devoted to test execution by using test selection techniques. Many techniques have been proposed but few have been evaluated on real-world, large scale systems. In this paper we report on an empirical evaluation of using the class firewall regression test selection technique, in combination with scenario testing, on a large scale industrial software system using the Java byte code in the analysis. The study was performed on a large complex distributed software system in one of Sweden's largest banks. Effects of using scenario testing together with regression test selection are reported. The results are that not all test cases were selected by the class firewall selection technique. Using scenario testing, where test cases are dependent,. affects the number of test cases selected, as do the location and number of changes in the system.
|
|
| 5. |
- Skoglund, Mats, et al.
(författare)
-
Improving class firewall regression test selection by removing the class firewall
- 2007
-
Ingår i: International journal of software engineering and knowledge engineering. - 0218-1940. ; 17:3, s. 359-378
-
Tidskriftsartikel (refereegranskat)abstract
- One regression test selection technique proposed for object-oriented programs is the Class firewall regression test selection technique. The selection technique selects test classes for regression test, which test changed classes and classes depending on changed classes. However, in empirical studies of the application of the technique, we observed that another technique found the same defects, selected fewer tests and required a simpler, less costly, analysis. The technique, which we refer to as the Change-based regression test selection technique, is basically the Class firewall technique, but with the class firewall removed. In this paper we formulate a hypothesis stating that these empirical observations are not incidental, but an inherent property of the Class firewall technique. We prove that the hypothesis holds for Java in a stable testing environment, and conclude that the effectiveness of the Class firewall regression testing technique can be improved without sacrificing the defect detection capability of the technique, by removing the class firewall.
|
|
| 6. |
- Bjarnason, Elizabeth, et al.
(författare)
-
Challenges and practices in aligning requirements with verification and validation : a case study of six companies
- 2014
-
Ingår i: Empirical Software Engineering. - : Springer. - 1382-3256 .- 1573-7616. ; 19:6, s. 1809-1855
-
Tidskriftsartikel (refereegranskat)abstract
- Weak alignment of requirements engineering (RE) with verification and validation (VV) may lead to problems in delivering the required products in time with the right quality. For example, weak communication of requirements changes to testers may result in lack of verification of new requirements and incorrect verification of old invalid requirements, leading to software quality problems, wasted effort and delays. However, despite the serious implications of weak alignment research and practice both tend to focus on one or the other of RE or VV rather than on the alignment of the two. We have performed a multi-unit case study to gain insight into issues around aligning RE and VV by interviewing 30 practitioners from 6 software developing companies, involving 10 researchers in a flexible research process for case studies. The results describe current industry challenges and practices in aligning RE with VV, ranging from quality of the individual RE and VV activities, through tracing and tools, to change control and sharing a common understanding at strategy, goal and design level. The study identified that human aspects are central, i.e. cooperation and communication, and that requirements engineering practices are a critical basis for alignment. Further, the size of an organisation and its motivation for applying alignment practices, e.g. external enforcement of traceability, are variation factors that play a key role in achieving alignment. Our results provide a strategic roadmap for practitioners improvement work to address alignment challenges. Furthermore, the study provides a foundation for continued research to improve the alignment of RE with VV.
|
|
| 7. |
|
|
| 8. |
- Linåker, Johan, et al.
(författare)
-
A Survey on the Perception of Innovation in a Large Product-focused Software Organization
- 2015
-
Ingår i: Lecture Notes in Business Information Processing (LNBIP). - Cham : Springer International Publishing. - 1865-1348. ; 210, s. 66-80, s. 66-80
-
Konferensbidrag (refereegranskat)abstract
- Context.Innovation is promoted in companies to help them stay competitive. Four types of innovation are defined: product, process, business, and organizational. Objective. We want to understand the perception of the innovation concept in industry, and particularly how the innovation types relate to each other. Method. We launched a survey at a branch of a multi-national corporation. Results. From a qualitative analysis of the 229 responses, we see that the understanding of the innovation concept is somewhat narrow, and mostly related to product innovation. A majority of respondents indicate that product innovation triggers process, business, and organizational innovation, rather than vice versa. However, there is a complex interdependency between the types. We also identify challenges related to each of the types. Conclusion. Increasing awareness and knowledge of different types of innovation, may improve the innovation. Further, they cannot be handled one by one, but in their interdependent relations.
|
|
| 9. |
- Munir, Hussan, et al.
(författare)
-
Open innovation in software engineering: a systematic mapping study
- 2016
-
Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1573-7616 .- 1382-3256. ; 21:2, s. 684-723
-
Tidskriftsartikel (refereegranskat)abstract
- Open innovation (OI) means that innovation is fostered by using both external and 5 internal influences in the innovation process. In software engineering (SE), OI has existed 6 for decades, while we currently see a faster and broader move towards OI in SE. We there- 7 fore survey research on how OI takes place and contributes to innovation in SE. This study 8 aims to synthesize the research knowledge on OI in the SE domain. We launched a system- 9 atic mapping study and conducted a thematic analysis of the results. Moreover, we analyzed 10 the strength of the evidence in the light of a rigor and relevance assessment of the research. 11 We identified 33 publications, divided into 9 themes related to OI. 17/33 studies fall in the 12 high–rigor/high–relevance category, suggesting the results are highly industry relevant. The 13 research indicates that start-ups have higher tendency to opt OI compared to incumbents. 14 The evidence also suggests that firms assimilating knowledge into their internal R&D activ- 15 ities, have higher likelihood of gaining financial advantages. We concluded that OI should 16 be adopted as a complementary approach to facilitate internal innovation and not to substi- 17 tute it. Further research is advised on situated OI strategies and the interplay between OI 18 and agile practices.
|
|
| 10. |
- Petersson, Håkan, et al.
(författare)
-
Capture-Recapture in Software Inspections after 10 Years Research : Theory, Evaluation and Application.
- 2004
-
Ingår i: Journal of Systems and Software. - 0164-1212 .- 1873-1228. ; 72:2, s. 249-264
-
Tidskriftsartikel (refereegranskat)abstract
- Software inspection is a method to detect faults in the early phases of the software life cycle. In order to estimate the number of faults not found, capture-recapture was introduced for software inspections in 1992 to estimate remaining faults after an inspection. Since then, several papers have been written in the area, concerning the basic theory, evaluation of models and application of the method. This paper summarizes the work made in capture-recapture for software inspections during these years. Furthermore, and more importantly, the contribution of the papers are classified as theory, evaluation or application, in order to analyse the performed research as well as to highlight the areas of research that need further work. It is concluded that (1) most of the basic theory is investigated within biostatistics, (2) most software engineering research is performed on evaluation, a majority ending up in recommendation of the Mh-JK model, and (3) there is a need for application experiences. In order to support the application, an inspection process is presented with decision points based on capture-recapture estimates.
|
|
