Exploring the software repositories of embedded systems: An industrial experience

Polaczek, Jakub; Sosnowski, J.

doi:10.1016/j.infsof.2020.106489

Cited by 7 publications

(21 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…They refer to activities (including comment exchanges) of project users, vendors (external provider of some software modules) or technical support. More complex problem handling paths (with several branches and loops) we have observed in other projects [7,25]…”

Section: New → Workaround → Open → In Analysis → Accepted → In_progress → In Review → Resolved → Closedmentioning

confidence: 90%

“…Commercial software projects provide rich repositories on their development and operations. They comprise information on code changes (commits due to bug corrections, added functionalities, performance improvement) and bug or other requested tasks (issues) reports, which constitute development and field (users) knowledge related to some historical project/company perspective [17] [25]. Issue tracking repositories comprise requests of developing new functionalities, code modifications, correcting bugs, merging codes, etc.…”

Section: A Test Challengesmentioning

confidence: 99%

“…The problem of assessing and improving the quality of bug reports is discussed in [26]. We have also explored this in [25]. Historical analysis of software repositories is also helpful in optimal attributing bugs to programmers for fixing (bug triaging [27]).…”

Section: A Test Challengesmentioning

confidence: 99%

“…This additionally confirms negligence of the pointed problems in correlation with testing, which we found as important practical issues needing investigation. [2, 5, 8, 12 -14, 34-36, 44] Testing project performance [16,17] Bug classification [17, 24-26, 28, 29] Test quality assessment [1 -4, 6, 10, 11, 15, 21, 34-37] Fault localization and program diagnosability [3,22,23,38,39] Test optimization and prioritization [18 -23, 42, 43] Logging schemes [9,28,30] Log analysis and parsing [9, 30 -32] Anomaly detection [9,33,34] Log statement optimization [9,34] Issue and version control tracking [7,25,30,37] Bug triaging [27] The created test scenarios are upgraded during the development and maintenance of the program. Moreover, in a large extent they are used during regression testing in relevance to function upgrades, extensions, or corrections.…”

Section: B Test Assessmentmentioning

confidence: 99%

“…Hence, it is reasonable to analyze software version control (SVC) repositories in accordance with issue system (Jira). We have quite rich experience with such analysis presented in [7,25] in relation to open source and commercial projects. This resulted in the original concept of the problem handling graph (PHG) and software development monitoring, which is also useful in tracing links with testing processes.…”

Section: Code and Test Dependanciesmentioning

confidence: 99%

See 4 more Smart Citations

Extending the Space of Software Test Monitoring: Practical Experience

Lasynskyi

Sosnowski

2021

IEEE Access

Self Cite

View full text Add to dashboard Cite

Software reliability depends on the performed tests. Bug detection and diagnosis are based on test outcome (oracle) analysis. Most practical test reports do not provide sufficient information for localizing and correcting bugs. We have found the need to extend the space of test result observation in data and time perspectives. This resulted in tracing supplementary test result features in event logs. They are explored with combined text mining and log parsing techniques. Another important point is correlating test life cycle with project development history journaled in issue tracking and software version control repositories. Dealing with the outlined problems, neglected in the literature, we have introduced original analysis schemes. They focus on assessing test coverage, reasons of low diagnosability, and test result profiles. Multidimensional investigation of test features and their management is supported with the developed test infrastructure. This assures a holistic insight into the test efficiency to identify test scheme deficiencies (e.g., functional inadequacy, aging, insufficient coverage) and possible improvements (test set updates). Our studies have been verified in relevance to a real commercial project (industrial case study) and confronted with the experience of testers engaged in other projects.INDEX TERMS bug diagnostics, software defect repository, software testing, testing framework, test monitoring.

show abstract

Section: New → Workaround → Open → In Analysis → Accepted → In_progress → In Review → Resolved → Closedmentioning

confidence: 90%

Section: A Test Challengesmentioning

confidence: 99%

Section: A Test Challengesmentioning

confidence: 99%

Section: B Test Assessmentmentioning

confidence: 99%

Section: Code and Test Dependanciesmentioning

confidence: 99%

See 3 more Smart Citations

Extending the Space of Software Test Monitoring: Practical Experience

Lasynskyi

Sosnowski

2021

IEEE Access

Self Cite

View full text Add to dashboard Cite

show abstract

Refactoring embedded software: A study in healthcare domain

Smiari

Bibi

Ampatzoglou

et al. 2022

Information and Software Technology

View full text Add to dashboard Cite

Facilitating Reuse of Functions in Embedded Software

2022

View full text Add to dashboard Cite

Developing software-intensive embedded systems is a significant challenge as embedded systems have become more complex and dynamic for integrating various constraints (e.g., real-time performance, design, and functional safety). In general, software practitioners reuse code to reduce development time for implementing required functionalities. However, embedded software development still lacks code reuse on a large scale due to its intricate constraints. This paper presents an approach to identifying reusable functions and their relationships from the legacy embedded software for faster development reducing functionality testing time. A python tool is developed to automatically extract the reusable functions and present them in a feature model. The search time for finding reusable functions speeds up when they are placed as features in a feature model. We conducted experiments on three GitHub embedded software projects (elevator, infotainment, and health monitoring systems). The experimental results find that our proposed approach reduces the feature search time by 59.0%, 49.8%, and 74.5%, respectively, compared to the manual searching approach for 50 features.

show abstract

Exploring the software repositories of embedded systems: An industrial experience

Cited by 7 publications

References 23 publications

Extending the Space of Software Test Monitoring: Practical Experience

Extending the Space of Software Test Monitoring: Practical Experience

Refactoring embedded software: A study in healthcare domain

Facilitating Reuse of Functions in Embedded Software

Contact Info

Product

Resources

About