dc.contributor.author | Mayr-Dorn, Christoph | |
dc.contributor.author | Vierhauser, Michael | |
dc.contributor.author | Bichler, Stefan | |
dc.contributor.author | Keplinger, Felix | |
dc.contributor.author | Cleland-Huang, Jane | |
dc.contributor.author | Egyed, Alexander | |
dc.contributor.author | Mehofer, Thomas | |
dc.contributor.editor | Grunske, Lars | |
dc.contributor.editor | Siegmund, Janet | |
dc.contributor.editor | Vogelsang, Andreas | |
dc.date.accessioned | 2022-01-19T12:56:53Z | |
dc.date.available | 2022-01-19T12:56:53Z | |
dc.date.issued | 2022 | |
dc.identifier.isbn | 978-3-88579-714-2 | |
dc.identifier.issn | 1617-5468 | |
dc.identifier.uri | http://dl.gi.de/handle/20.500.12116/37975 | |
dc.description.abstract | This abstract summarizes the work published as an ICSE 2021 research track paper ''Supporting Quality Assurance with Automated Process-Centric Quality Constraints Checking'' available at https://doi.org/10.1109/ICSE43902.2021.00118 . We propose an approach that, on the one hand, assists in checking compliance with traceability requirements but, on the other hand, allows engineers to temporarily deviate from the prescribed software engineering process. Through the observation of developer activities in the form of changes to engineering artifacts in tools such as Jira or Jama, we build up a representation of the ongoing process progress. This tracking in the background does not force the software developer to work only on activities as defined in a process description. At the same time, it enables us to provide timely feedback to the developer on whether tasks fulfill all QA criteria. This approach lifts the burden off QA engineers in manually checking QA constraints, often a time-consuming, tedious, and error-prone task where feedback reaches developers usually very late. We evaluate our approach by applying it to two different case studies; one open source community system and a safety-critical system in the air-traffic control domain. Results from the analysis show that trace links are often corrected or completed after the fact and thus timely and automated constraint checking support has significant potential on reducing rework. | en |
dc.language.iso | en | |
dc.publisher | Gesellschaft für Informatik e.V. | |
dc.relation.ispartof | Software Engineering 2022 | |
dc.relation.ispartofseries | Lecture Notes in Informatics (LNI) - Proceedings, Volume P-320 | |
dc.subject | software engineering process | |
dc.subject | traceability | |
dc.subject | developer support | |
dc.subject | artifact change monitoring | |
dc.title | Automated Process-Centric Quality Constraints Checking for Quality Assurance in Safety-critical Systems | en |
dc.type | Text/Conference Paper | |
dc.pubPlace | Bonn | |
mci.reference.pages | 71-72 | |
mci.conference.sessiontitle | Wissenschaftliches Hauptprogramm | |
mci.conference.location | Berlin/Virtuell | |
mci.conference.date | 21.-25. Feburar 2022 | |
dc.identifier.doi | 10.18420/se2022-ws-022 | |