Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
skip to main content
10.1145/3629479.3629489acmotherconferencesArticle/Chapter ViewAbstractPublication PagessbqsConference Proceedingsconference-collections
research-article

Enhancing Issue Management through the Employment of Inspection Technique: An Experience Report in The Industry

Published: 06 December 2023 Publication History

Abstract

The software industry has been adopting the concept of Global Software Development to release products quicker and with fewer costs, assuring quality by employing software testing techniques which are able to detect issues early. In this context, this paper presents an experience report performed at SIDIA Institute of Science and Technology between the years of 2020 and 2022, during which a process of issue management (IM) was developed to reduce the problems in the issue report, such as: lack of cohesion, absence of confirmation tests and long learning curve time of the testing team. In order to face these challenges, the IM process employs inspection techniques in order to improve the quality of reports, and then, increase its effectiveness, i.e., the number of valid issues. In addition, to support the IM process, it was created an onboarding phase, a template for issue reports and the monitoring of issues until the confirmation test. Through the implementation of this process, there was evaluated a total amount of 11002 issues report, and as a result, it was observed that the issues’ effectiveness rate was increased from to (raising by ) in the period in which this research was performed. In sequence, it was detected that around of issues had problems related to issue report writing. Furthermore, qualitative research revealed that of the interviewed testers consider the process effective. The authors hope that lessons learned described in this paper can contribute to the academic and industry communities by regarding the employment of inspection techniques to evaluate issue reports.

References

[1]
2017. IEEE Recommended Practice on Software Reliability. IEEE Std 1633-2016 (Revision of IEEE Std 1633-2008) (2017), 1–261. https://doi.org/10.1109/IEEESTD.2017.7827907
[2]
2017. IEEE Standard for System, Software, and Hardware Verification and Validation. IEEE Std 1012-2016 (Revision of IEEE Std 1012-2012/ Incorporates IEEE Std 1012-2016/Cor1-2017) (2017), 1–260. https://doi.org/10.1109/IEEESTD.2017.8055462
[3]
2021. IEEE/ISO/IEC International Standard for Software and systems engineering–Software testing–Part 3:Test documentation. ISO/IEC/IEEE 29119-3:2021(E) (2021), 1–98. https://doi.org/10.1109/IEEESTD.2021.9591577
[4]
Ahmed R. Abd Shaheen and Laheeb M. I. Alzubaidy. 2022. Challenges Performance Facing Global Virtual Teams In Global Software Development:Literature Review. In 2022 8th International Conference on Contemporary Information Technology and Mathematics (ICCITM). IEEE, 73–78. https://doi.org/10.1109/ICCITM56309.2022.10031965
[5]
W Richards Adrion, Martha A Branstad, and John C Cherniavsky. 1982. Validation, verification, and testing of computer software. ACM Computing Surveys (CSUR) 14, 2 (1982), 159–192.
[6]
Waqas Ahmad, Usman Qamar, and Shoaib Hassan. 2015. Analyzing different validation and verification techniques for safety critical software systems. In 2015 6th IEEE International Conference on Software Engineering and Service Science (ICSESS). IEEE, 367–370. https://doi.org/10.1109/ICSESS.2015.7339076
[7]
Kaaenat Ali, Junaid Ali Khan, Farwah Aizaz, and Mansoor Ahmed. 2021. Software Requirements Prioritization in the context of Global Software Development. In 2021 International Conference on Frontiers of Information Technology (FIT). IEEE, 13–18. https://doi.org/10.1109/FIT53504.2021.00013
[8]
Naihara Amorim and Gileanes Guedes. 2017. Aplicando Técnicas de V&V na Fase de Projeto do Modelo em Cascata. In Anais da I Escola Regional de Engenharia de Software. SBC, 129–136.
[9]
John Anvik, Lyndon Hiew, and Gail C. Murphy. 2006. Who Should Fix This Bug?. In Proceedings of the 28th International Conference on Software Engineering (Shanghai, China) (ICSE ’06). Association for Computing Machinery, New York, NY, USA, 361–370. https://doi.org/10.1145/1134285.1134336
[10]
Mohammad Azzeh. 2013. Software cost estimation based on use case points for global software development. In 2013 5th International Conference on Computer Science and Information Technology. IEEE, 214–218. https://doi.org/10.1109/CSIT.2013.6588782
[11]
Rafael Ferreira Barcelos and Guilherme Horta Travassos. 2006. ArqCheck: Uma abordagem para inspeção de documentos arquiteturais baseada em checklist. In Brazilian Symposium on Software Quality.
[12]
Victor R Basili and Richard W Selby. 1987. Comparing the effectiveness of software testing strategies. IEEE transactions on software engineering12 (1987), 1278–1296.
[13]
Silvia Breu, Rahul Premraj, Jonathan Sillito, and Thomas Zimmermann. 2010. Information Needs in Bug Reports: Improving Cooperation between Developers and Users. In Proceedings of the 2010 ACM Conference on Computer Supported Cooperative Work (Savannah, Georgia, USA) (CSCW ’10). Association for Computing Machinery, New York, NY, USA, 301–310. https://doi.org/10.1145/1718918.1718973
[14]
Jardelane Brito, Jeanne Trovão, and Arilo Claudio Dias-Neto. 2012. TestCheck – Uma Abordagem Baseada em Checklist para Inspecionar Artefatos de Teste de Software. In Anais do XI Simpósio Brasileiro de Qualidade de Software (Fortaleza). SBC, Porto Alegre, RS, Brasil, 113–127. https://doi.org/10.5753/sbqs.2012.15311
[15]
J. R. Brown and M. Lipow. 1975. Testing for Software Reliability. SIGPLAN Not. 10, 6 (apr 1975), 518–527. https://doi.org/10.1145/390016.808475
[16]
M. Delamaro, M. Jino, and J. Maldonado. 2013. Introdução Ao Teste De Software. Elsevier Brasil. https://books.google.com.br/books?id=zqw4DwAAQBAJ
[17]
William Enck, Machigar Ongtang, and Patrick McDaniel. 2009. Understanding Android Security. IEEE Security & Privacy 7, 1 (2009), 50–57. https://doi.org/10.1109/MSP.2009.26
[18]
Michael Fagan. 2002. Design and code inspections to reduce errors in program development. Software pioneers: contributions to software engineering (2002), 575–607.
[19]
Tom Gilb and Dorothy Graham. 1993. Software inspections. Addison-Wesley Reading, Masachusetts.
[20]
Dorothy Graham, Rex Black, and Erik Van Veenendaal. 2021. Foundations of software testing ISTQB Certification. Cengage Learning.
[21]
Kim Herzig, Michaela Greiler, Jacek Czerwonka, and Brendan Murphy. 2015. The Art of Testing Less without Sacrificing Quality. In 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering, Vol. 1. 483–493. https://doi.org/10.1109/ICSE.2015.66
[22]
Pramod Mathew Jacob and M. Prasanna. 2016. A Comparative analysis on Black box testing strategies. In 2016 International Conference on Information Science (ICIS). 1–6. https://doi.org/10.1109/INFOSCI.2016.7845290
[23]
An Ju, Hitesh Sajnani, Scot Kelly, and Kim Herzig. 2021. A Case Study of Onboarding in Software Teams: Tasks and Strategies. In Proceedings of the 43rd International Conference on Software Engineering (Madrid, Spain) (ICSE ’21). IEEE Press, 613–623. https://doi.org/10.1109/ICSE43902.2021.00063
[24]
Timo Koponen. 2006. Life cycle of defects in open source software projects. In Open Source Systems: IFIP Working Group 2.13 Foundation on Open Source Software, June 8–10, 2006, Como, Italy 2. Springer, 195–200.
[25]
Heli Lintula, Timo Koponen, and Virpi Hotti. 2006. Exploring the Maintenance Process through the Defect Management in the Open Source Projects - Four Case Studies. In 2006 International Conference on Software Engineering Advances (ICSEA’06). 53–53. https://doi.org/10.1109/ICSEA.2006.261309
[26]
Glenford J Myers, Corey Sandler, and Tom Badgett. 2011. The art of software testing. John Wiley & Sons.
[27]
Klaus Olsen, Meile Posthuma, and Stephanie Ulrich. 2019. Certified Tester Syllabus Foundation Level. Vol. V3.1.
[28]
D. O’Neill. [n. d.]. Issues in software inspection. 14 ([n. d.]). https://doi.org/10.1109/52.566420
[29]
M. Parnas, DL e Lawford. [n. d.]. The role of inspection in software quality assurance. IEEE Transactions on Software Engineering 29 ([n. d.]). https://doi.org/10.1109/TSE.2003.1223642
[30]
Roger Pressman. 2009. Software Engineering: A Practitioner’s Approach (7 ed.). McGraw-Hill, Inc., USA.
[31]
Abhijit A Sawant, Pranit H Bari, and PM Chawan. 2012. Software testing techniques and strategies. International Journal of Engineering Research and Applications (IJERA) 2, 3 (2012), 980–986.
[32]
F. Shull, I. Rus, and V. Basili. 2000. How perspective-based reading can improve requirements inspections. Computer 33, 7 (2000), 73–79. https://doi.org/10.1109/2.869376
[33]
Ian Sommerville. 2011. Software Engineering, 9/E. Pearson Education India.
[34]
Saman Tariq, Ahmad Ibrahim, Ali Usama, and M. Saad Shahbaz. 2021. An Overview of Requirements Elicitation Techniques in Software Engineering with a focus on Agile Development. In 2021 4th International Conference on Computing & Information Sciences (ICCIS). 1–6. https://doi.org/10.1109/ICCIS54243.2021.9676192
[35]
Dietmar Winkler, Juergen Musil, Angelika Musil, and Stefan Biffl. 2016. Collective Intelligence-Based Quality Assurance: Combining Inspection and Risk Assessment to Support Process Improvement in Multi-Disciplinary Engineering, Vol. 633. 163–175. https://doi.org/10.1007/978-3-319-44817-6_13
[36]
Hongyu Zhang, Liang Gong, and Steve Versteeg. 2013. Predicting bug-fixing time: An empirical study of commercial software projects. In 2013 35th International Conference on Software Engineering (ICSE). 1042–1051. https://doi.org/10.1109/ICSE.2013.6606654

Cited By

View all
  • (2024)Automating Issue Reporting in Software Testing: Lessons Learned from Using the Template Generator ToolCompanion Proceedings of the 32nd ACM International Conference on the Foundations of Software Engineering10.1145/3663529.3663847(278-282)Online publication date: 10-Jul-2024

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Other conferences
SBQS '23: Proceedings of the XXII Brazilian Symposium on Software Quality
November 2023
391 pages
ISBN:9798400707865
DOI:10.1145/3629479
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected].

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 06 December 2023

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. Inspection Techniques
  2. Issue Effectiveness
  3. Issue Report
  4. Software Testing
  5. V&V Techniques

Qualifiers

  • Research-article
  • Research
  • Refereed limited

Conference

SBQS '23
SBQS '23: XXII Brazilian Symposium on Software Quality
November 7 - 10, 2023
Bras\'{\i}lia, Brazil

Acceptance Rates

Overall Acceptance Rate 35 of 99 submissions, 35%

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)14
  • Downloads (Last 6 weeks)1
Reflects downloads up to 03 Feb 2025

Other Metrics

Citations

Cited By

View all
  • (2024)Automating Issue Reporting in Software Testing: Lessons Learned from Using the Template Generator ToolCompanion Proceedings of the 32nd ACM International Conference on the Foundations of Software Engineering10.1145/3663529.3663847(278-282)Online publication date: 10-Jul-2024

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

HTML Format

View this article in HTML Format.

HTML Format

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media