| 1. |
- Ahmad, Azeem, et al.
(författare)
-
A Multi-factor Approach for Flaky Test Detection and Automated Root Cause Analysis
- 2021
-
Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - : IEEE COMPUTER SOC. - 1530-1362. ; , s. 338-348
-
Konferensbidrag (refereegranskat)abstract
- Developers often spend time to determine whether test case failures are real failures or flaky. The flaky tests, also known as non-deterministic tests, switch their outcomes without any modification in the codebase, hence reducing the confidence of developers during maintenance as well as in the quality of a product. Re-running test cases to reveal flakiness is resource-consuming, unreliable and does not reveal the root causes of test flakiness. Our paper evaluates a multi-factor approach to identify flaky test executions implemented in a tool named MDF laker. The four factors are: trace-back coverage, flaky frequency, number of test smells, and test size. Based on the extracted factors, MDFlaker uses k-Nearest Neighbor (KNN) to determine whether failed test executions are flaky. We investigate MDFlaker in a case study with 2166 test executions from different open-source repositories. We evaluate the effectiveness of our flaky detection tool. We illustrate how the multi-factor approach can be used to reveal root causes for flakiness, and we conduct a qualitative comparison between MDF laker and other tools proposed in literature. Our results show that the combination of different factors can be used to identify flaky tests. Each factor has its own trade-off, e.g., trace-back leads to many true positives, while flaky frequency yields more true negatives. Therefore, specific combinations of factors enable classification for testers with limited information (e.g., not enough test history information).
|
|
| 2. |
- Alahyari, Hiva, 1979, et al.
(författare)
-
What Do Agile Teams Find Important for Their Success?
- 2018
-
Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - 1530-1362. ; 2018-December, s. 474-483
-
Konferensbidrag (refereegranskat)abstract
- Although the general benefits of agile methods have been shown, it is not always clear what makes the application of agile successful or not in a company. With this motivation, we investigate agile success factors, particularly from the viewpoint of teams. We conduct in-company surveys to collect and rank agile team success factors, comparing these results with success factors found in the literature. Our results introduce new success factors not previously discussed in related work. The findings emphasize the importance of team environment, team spirit, and team capability as opposed to previous work which emphasizes project management process and customer involvement. These findings can help find issues and improve the performance of agile teams.
|
|
| 3. |
- Berbyuk Lindström, Nataliya, 1978, et al.
(författare)
-
Understanding Metrics Team-Stakeholder Communication in Agile Metrics Service Delivery
- 2021
-
Ingår i: APSEC (Asian Pacific Software Engineering conference), December 6-10, Taiwan-Virtual.. ; 2021-December, s. 401-409
-
Konferensbidrag (refereegranskat)abstract
- In this paper, we explore challenges in communication between metrics teams and stakeholders in metrics service delivery. Drawing on interviews and interactive workshops with team members and stakeholders at two different Swedish agile software development organizations, we identify interrelated challenges such as aligning expectations, prioritizing demands, providing regular feedback, and maintaining continuous dialogue, which influence team-stakeholder interaction, relationships and performance. Our study shows the importance of understanding communicative hurdles and provides suggestions for their mitigation, therefore meriting further empirical research.
|
|
| 4. |
- Burden, Håkan, 1976, et al.
(författare)
-
Executable and Translatable UML - How Difficult Can It Be?
- 2011
-
Ingår i: 18th Asia Pacific Software Engineering Conference, APSEC 2011; Ho Chi Minh; Viet Nam; 5 December 2011 through 8 December 2011. - 1530-1362. - 9781457721991 ; , s. 114-121
-
Konferensbidrag (refereegranskat)abstract
- Executable and Translatable UML enables Model-Driven Architecture by specifying Platform-Independent Models that can be automatically transformed into Platform-Specific Models through model compilation. Previous research shows that the transformations result in both efficient code and consistency between the models. However, there are neither results for the effort of introducing the technology in a new context nor on the level of expertise needed for designing the Platform-Independent Models. We wanted to know if teams of novice software developers could design Executable and Translatable UML models without prior experiences of software modelling. As part of a new university course we conducted an exploratory case study with two data collections over two years. Bachelor students were given the task to design a hotel reservation system and the necessary test cases for verifying the functionality and structure of the models within 300 hours, using Executable and Translatable UML. In total, 43 out of 50 teams succeeded in delivering verified and consistent models within the time frame. During the second data collection the students were given limited tool training. This gave a raise in the quality of the models. Due to the executable feature of the models the students were given constant feedback on their design until the models behaved as expected, with the required level of detail and structure. Our results show that using Executable and Translatable UML does not require more expertise than a bachelor program in computer science. All in all, Executable and Translatable UML could play an important role in future software development.
|
|
| 5. |
- Dakkak, Anas, et al.
(författare)
-
Towards Continuous Data Collection from In-service Products: Exploring the Relation between Data Dimensions and Collection Challenges
- 2021
-
Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - 1530-1362. ; 2021-December, s. 243-252
-
Konferensbidrag (refereegranskat)abstract
- Data collected from in-service products play an important role in enabling software-intensive embedded systems suppliers to embrace data-driven practices. Data can be used in many different ways such as to continuously learn and improve the product, enhance post-deployment services, reduce operational cost or create a better user experience. While there is no shortage of possible use cases leveraging data from in-service products, software-intensive embedded systems companies struggle to continuously collect data from their in-service products. Often, data collection is done in an ad-hoc way and targeting specific use cases or needs. Besides, few studies have investigated data collection challenges in relation to the data dimensions, which are the minimum set of quantifiable data aspects that can define software-intensive embedded product data from a collection point of view. To help address data collection challenges, and to provide companies with guidance on how to improve this process, we conducted a case study at a large multinational telecommunications supplier focusing on data characteristics and collection challenges from the Radio Access Networks (RAN) products. We further investigated the relations of these challenges to the data dimensions to increase our understanding of how data dominions contribute to the challenges.
|
|
| 6. |
- Figalist, Iris, et al.
(författare)
-
Mining customer satisfaction on b2b online platforms using service quality and web usage metrics
- 2020
-
Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - : IEEE. - 1530-1362. ; 2020-December, s. 435-444, s. 435-444
-
Konferensbidrag (refereegranskat)abstract
- In order to distinguish themselves from their competitors, software service providers constantly try to assess and improve customer satisfaction. However, measuring customer satisfaction in a continuous way is often time and cost intensive, or requires effort on the customer side. Especially in B2B contexts, a continuous assessment of customer satisfaction is difficult to achieve due to potential restrictions and complex provider-customer-end user setups. While concepts such as web usage mining enable software providers to get a deep understanding of how their products are used, its application to quantitatively measure customer satisfaction has not yet been studied in greater detail. For that reason, our study aims at combining existing knowledge on customer satisfaction, web usage mining, and B2B service characteristics to derive a model that enables an automated calculation of quantitative customer satisfaction scores. We apply web usage mining to validate these scores and to compare the usage behavior of satisfied and dissatisfied customers. This approach is based on domain-specific service quality and web usage metrics and is, therefore, suitable for continuous measurements without requiring active customer participation. The applicability of the model is validated by instantiating it in a real-world B2B online platform.
|
|
| 7. |
- Gencel, Cigdem, et al.
(författare)
-
On the Relationship between Different Size Measures in the Software Life Cycle
- 2009
-
Ingår i: 16th Asia-Pacific Software Engineering Conference, APSEC 2009; Penang; Malaysia; 1 December 2009 through 3 December 2009. - Penang, Malaysia : IEEE Computer Society. - 1530-1362. - 9780769539096 ; , s. 19-26
-
Konferensbidrag (refereegranskat)abstract
- Various measures and methods have been developed to measure the sizes of different software entities produced throughout the software life cycle. Understanding the nature of the relationship between the sizes of these products has become significant due to various reasons. One major reason is the ability to predict the size of the later phase products by using the sizes of early life cycle products. For example, we need to predict the Source Lines of Code (SLOC) from Function Points (FP) since SLOC is being used as the main input for most of the estimation models when this measure is not available yet. SLOC/FP ratios have been used by the industry for such purposes even though the assumed linear relationship has not been validated yet. Similarly, FP has recently started to be used to predict the Bytes of code for estimating the amount of spare memory needed in systems. In this paper, we aim to investigate further the nature of the relationship between the software functional size and the code size by conducting a series of empirical studies.
|
|
| 8. |
- Gomes, Francisco, 1987, et al.
(författare)
-
Visualizing test diversity to support test optimisation
- 2018
-
Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - 1530-1362. - 9781728119700 ; 2018-December
-
Konferensbidrag (refereegranskat)abstract
- Diversity has been used as an effective criteria to optimise test suites for cost-effective testing. Particularly, diversity-based (alternatively referred to as similarity-based) techniques have the benefit of being generic and applicable across different Systems Under Test (SUT), and have been used to automatically select or prioritise large sets of test cases. However, it is a challenge to feedback diversity information to developers and testers since results are typically many-dimensional. Furthermore, the generality of diversity-based approaches makes it harder to choose when and where to apply them. In this paper we address these challenges by investigating: i) what are the trade-off in using different sources of diversity (e.g., diversity of test requirements or test scripts) to optimise large test suites, and ii) how visualisation of test diversity data can assist testers for test optimisation and improvement. We perform a case study on three industrial projects and present quantitative results on the fault detection capabilities and redundancy levels of different sets of test cases. Our key result is that test similarity maps, based on pair-wise diversity calculations, helped industrial practitioners identify issues with their test repositories and decide on actions to improve. We conclude that the visualisation of diversity information can assist testers in their maintenance and optimisation activities.
|
|
| 9. |
- Hebig, Regina, et al.
(författare)
-
Surveying the Corpus of Model Resolution Strategies for Metamodel Evolution
- 2015
-
Ingår i: 22nd Asia-Pacific Software Engineering Conference, APSEC 2015; Holiday Inn Hotel at International AirportNew Delhi; India; 1 December 2015 through 4 December 2015. - 1530-1362. - 9781467396448 ; , s. 135-142
-
Konferensbidrag (refereegranskat)abstract
- Modeling languages evolve regularly. Companies need to maintain all those models that are used in running projects, which can cause these projects to fall back in their schedules. Since 10 years research addresses this issue with approaches for automating co-evolution. The dominant core of these approaches are model resolution strategies. They define 1) how models have to be changed in reaction to specific metamodel changes, 2) what degree of automation can be reached, and 3) to what extent the user can control the resolution outcome. In this paper, we survey existing co-evolution approaches and analyze model resolution strategies. We present a corpus of more than 200 resolution strategies for 116 types of metamodel changes and discuss degree of automation and choices that users have today.
|
|
| 10. |
- Heldal, Rogardt, 1964, et al.
(författare)
-
Modeling executable test actors: Exploratory study done in executable and translatable UML
- 2012
-
Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - 1530-1362. - 9780769549224 ; 1, s. 784-789
-
Konferensbidrag (refereegranskat)abstract
- Model-based testing presents new challenges in how to perform software testing due to the fact that models offer testing on several abstraction levels. This is largely an unexplored area. We propose a pattern to construct test actors which can be used to test Platform-Independent Models. In addition, these test actors can also be automatically transformed to Platform-Specific Model level to test the implementation deployed on target. Our work is one step in the direction of permitting early testing without any waste, since the test models can be reused at a lower level of abstraction.
|
|
