Process Inspection Support: an Industrial Case Study

Christoph Mayr-Dorn, Johann Tuder, Alexander Egyed
{"title":"Process Inspection Support: an Industrial Case Study","authors":"Christoph Mayr-Dorn, Johann Tuder, Alexander Egyed","doi":"10.1145/3379177.3388900","DOIUrl":null,"url":null,"abstract":"Organizational factors such as team structure, coordination among engineers, or processes have a significant impact on software quality and development progress. Projects often take much longer to complete than planned and miscommunications among engineers are common. Yet, the process for exploring the project-specific or organization-specific root causes why this happens is still poorly supported. Investigations are cumbersome and require significant effort. In the context of this industrial case study, our industry partner was interested in measuring and assessing how the organization structure and issue handling processes ultimately affected software quality and time. Reducing the effort of such investigations/retrospectives and speeding up fact finding is important as it allows for more frequent, informed engineering process improvements and feedback to managers, team leads, and engineers. This paper describes our approach of pairing process metrics with visual historical inspection of issues. Stakeholders such as managers, team leads, or quality assurance engineers inspect metrics (and deviations from expected values) for individual issues and utilize a historical visualization of the affected (and related) issues to obtain insights into the reason for the metric (deviation) and its root cause. We demonstrate the usefulness of our approach based on our ProcessInspector prototype providing access to data on four real industry projects and a qualitative evaluation with team leads and group leads from our industry partner.","PeriodicalId":299473,"journal":{"name":"2020 IEEE/ACM International Conference on Software and System Processes (ICSSP)","volume":"44 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2020-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2020 IEEE/ACM International Conference on Software and System Processes (ICSSP)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3379177.3388900","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1

Abstract

Organizational factors such as team structure, coordination among engineers, or processes have a significant impact on software quality and development progress. Projects often take much longer to complete than planned and miscommunications among engineers are common. Yet, the process for exploring the project-specific or organization-specific root causes why this happens is still poorly supported. Investigations are cumbersome and require significant effort. In the context of this industrial case study, our industry partner was interested in measuring and assessing how the organization structure and issue handling processes ultimately affected software quality and time. Reducing the effort of such investigations/retrospectives and speeding up fact finding is important as it allows for more frequent, informed engineering process improvements and feedback to managers, team leads, and engineers. This paper describes our approach of pairing process metrics with visual historical inspection of issues. Stakeholders such as managers, team leads, or quality assurance engineers inspect metrics (and deviations from expected values) for individual issues and utilize a historical visualization of the affected (and related) issues to obtain insights into the reason for the metric (deviation) and its root cause. We demonstrate the usefulness of our approach based on our ProcessInspector prototype providing access to data on four real industry projects and a qualitative evaluation with team leads and group leads from our industry partner.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
过程检验支持:一个工业案例研究
组织因素,如团队结构,工程师之间的协调,或过程对软件质量和开发进度有重要的影响。项目完成的时间往往比计划的要长得多,工程师之间的沟通不畅也很常见。然而,探索特定于项目或特定于组织的根本原因的过程仍然得不到很好的支持。调查工作十分繁琐,需要付出巨大的努力。在这个工业案例研究的上下文中,我们的工业伙伴对度量和评估组织结构和问题处理过程最终如何影响软件质量和时间很感兴趣。减少此类调查/回顾的工作量并加快事实发现是很重要的,因为它允许更频繁、更明智的工程过程改进,并向经理、团队领导和工程师提供反馈。本文描述了我们将过程度量与问题的视觉历史检查配对的方法。涉众,如经理、团队领导或质量保证工程师,检查单个问题的度量标准(以及与期望值的偏差),并利用受影响(和相关)问题的历史可视化来深入了解度量标准(偏差)的原因及其根本原因。我们基于ProcessInspector原型展示了我们的方法的实用性,该原型提供了对四个真实行业项目的数据访问,并与我们的行业合作伙伴的团队领导和小组领导进行了定性评估。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
EcoKnow: Engineering Effective, Co-created and Compliant Adaptive Case Management Systems for Knowledge Workers Digital Re-imagination of Software and Systems Processes for Quality Engineering: iSPIN Approach Developing ML/DL Models: A Design Framework How are Hybrid Development Approaches Organized? - A Systematic Literature Review Constructing a Hybrid Software Process Simulation Model in Practice: An Exemplar from Industry
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1