Detecting Scattered and Tangled Quality Concerns in Source Code to Aid Maintenance and Evolution Tasks. Krasniqi, R. In 2023 IEEE/ACM 45th International Conference on Software Engineering: Companion Proceedings (ICSE-Companion), pages 184–188, Melbourne, Australia, May, 2023. IEEE. Paper doi abstract bibtex 5 downloads Quality concerns, such as reliability, security, usability concerns, among others, are typically well-defined and prioritized at the requirement level with the set goal of achieving high quality, robust, user-friendly, and trustworthy systems. However, quality concerns are challenging to address at the implementation level. Often they are scattered across multiple modules in the codebase. In other instances, they are tangled with functional ones within a single module. Reasoning about quality concerns and their interactions with functional ones while being hindered by the effects of scattered and tangled code can only yield to more unseen problems. For example, developers can inadvertently retrofit new bugs or wrongly implement new features that deviate from original system requirement specifications. The goal of this thesis is twofold. First, we aim to detect quality concerns implemented at code level to differentiate them from functional ones when they are scattered across the codebase. Second, we aim to untangle quality concerns from unrelated changes to gain a detailed knowledge about the history of specific quality changes. This knowledge is crucial to support consistency between the requirements-and-design and to verify architecture conformance. From the practical stance, developers could gain a breadth of understanding about quality concerns and their relations with other artifacts. Thus, with more confidence, they could perform code modifications, improve module traceability, and provide a better holistic assessment of change impact analysis.
@inproceedings{krasniqi_detecting_2023,
address = {Melbourne, Australia},
title = {Detecting {Scattered} and {Tangled} {Quality} {Concerns} in {Source} {Code} to {Aid} {Maintenance} and {Evolution} {Tasks}},
isbn = {9798350322637},
url = {https://ieeexplore.ieee.org/document/10172720/},
doi = {10.1109/ICSE-Companion58688.2023.00051},
abstract = {Quality concerns, such as reliability, security, usability concerns, among others, are typically well-defined and prioritized at the requirement level with the set goal of achieving high quality, robust, user-friendly, and trustworthy systems. However, quality concerns are challenging to address at the implementation level. Often they are scattered across multiple modules in the codebase. In other instances, they are tangled with functional ones within a single module. Reasoning about quality concerns and their interactions with functional ones while being hindered by the effects of scattered and tangled code can only yield to more unseen problems. For example, developers can inadvertently retrofit new bugs or wrongly implement new features that deviate from original system requirement specifications. The goal of this thesis is twofold. First, we aim to detect quality concerns implemented at code level to differentiate them from functional ones when they are scattered across the codebase. Second, we aim to untangle quality concerns from unrelated changes to gain a detailed knowledge about the history of specific quality changes. This knowledge is crucial to support consistency between the requirements-and-design and to verify architecture conformance. From the practical stance, developers could gain a breadth of understanding about quality concerns and their relations with other artifacts. Thus, with more confidence, they could perform code modifications, improve module traceability, and provide a better holistic assessment of change impact analysis.},
language = {en},
urldate = {2023-07-20},
booktitle = {2023 {IEEE}/{ACM} 45th {International} {Conference} on {Software} {Engineering}: {Companion} {Proceedings} ({ICSE}-{Companion})},
publisher = {IEEE},
author = {Krasniqi, Rrezarta},
month = may,
year = {2023},
keywords = {Conference Short Papers},
pages = {184--188},
}
Downloads: 5
{"_id":"R73cph8FdmzTkMjHF","bibbaseid":"krasniqi-detectingscatteredandtangledqualityconcernsinsourcecodetoaidmaintenanceandevolutiontasks-2023","author_short":["Krasniqi, R."],"bibdata":{"bibtype":"inproceedings","type":"inproceedings","address":"Melbourne, Australia","title":"Detecting Scattered and Tangled Quality Concerns in Source Code to Aid Maintenance and Evolution Tasks","isbn":"9798350322637","url":"https://ieeexplore.ieee.org/document/10172720/","doi":"10.1109/ICSE-Companion58688.2023.00051","abstract":"Quality concerns, such as reliability, security, usability concerns, among others, are typically well-defined and prioritized at the requirement level with the set goal of achieving high quality, robust, user-friendly, and trustworthy systems. However, quality concerns are challenging to address at the implementation level. Often they are scattered across multiple modules in the codebase. In other instances, they are tangled with functional ones within a single module. Reasoning about quality concerns and their interactions with functional ones while being hindered by the effects of scattered and tangled code can only yield to more unseen problems. For example, developers can inadvertently retrofit new bugs or wrongly implement new features that deviate from original system requirement specifications. The goal of this thesis is twofold. First, we aim to detect quality concerns implemented at code level to differentiate them from functional ones when they are scattered across the codebase. Second, we aim to untangle quality concerns from unrelated changes to gain a detailed knowledge about the history of specific quality changes. This knowledge is crucial to support consistency between the requirements-and-design and to verify architecture conformance. From the practical stance, developers could gain a breadth of understanding about quality concerns and their relations with other artifacts. Thus, with more confidence, they could perform code modifications, improve module traceability, and provide a better holistic assessment of change impact analysis.","language":"en","urldate":"2023-07-20","booktitle":"2023 IEEE/ACM 45th International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)","publisher":"IEEE","author":[{"propositions":[],"lastnames":["Krasniqi"],"firstnames":["Rrezarta"],"suffixes":[]}],"month":"May","year":"2023","keywords":"Conference Short Papers","pages":"184–188","bibtex":"@inproceedings{krasniqi_detecting_2023,\n\taddress = {Melbourne, Australia},\n\ttitle = {Detecting {Scattered} and {Tangled} {Quality} {Concerns} in {Source} {Code} to {Aid} {Maintenance} and {Evolution} {Tasks}},\n\tisbn = {9798350322637},\n\turl = {https://ieeexplore.ieee.org/document/10172720/},\n\tdoi = {10.1109/ICSE-Companion58688.2023.00051},\n\tabstract = {Quality concerns, such as reliability, security, usability concerns, among others, are typically well-defined and prioritized at the requirement level with the set goal of achieving high quality, robust, user-friendly, and trustworthy systems. However, quality concerns are challenging to address at the implementation level. Often they are scattered across multiple modules in the codebase. In other instances, they are tangled with functional ones within a single module. Reasoning about quality concerns and their interactions with functional ones while being hindered by the effects of scattered and tangled code can only yield to more unseen problems. For example, developers can inadvertently retrofit new bugs or wrongly implement new features that deviate from original system requirement specifications. The goal of this thesis is twofold. First, we aim to detect quality concerns implemented at code level to differentiate them from functional ones when they are scattered across the codebase. Second, we aim to untangle quality concerns from unrelated changes to gain a detailed knowledge about the history of specific quality changes. This knowledge is crucial to support consistency between the requirements-and-design and to verify architecture conformance. From the practical stance, developers could gain a breadth of understanding about quality concerns and their relations with other artifacts. Thus, with more confidence, they could perform code modifications, improve module traceability, and provide a better holistic assessment of change impact analysis.},\n\tlanguage = {en},\n\turldate = {2023-07-20},\n\tbooktitle = {2023 {IEEE}/{ACM} 45th {International} {Conference} on {Software} {Engineering}: {Companion} {Proceedings} ({ICSE}-{Companion})},\n\tpublisher = {IEEE},\n\tauthor = {Krasniqi, Rrezarta},\n\tmonth = may,\n\tyear = {2023},\n\tkeywords = {Conference Short Papers},\n\tpages = {184--188},\n}\n\n","author_short":["Krasniqi, R."],"key":"krasniqi_detecting_2023","id":"krasniqi_detecting_2023","bibbaseid":"krasniqi-detectingscatteredandtangledqualityconcernsinsourcecodetoaidmaintenanceandevolutiontasks-2023","role":"author","urls":{"Paper":"https://ieeexplore.ieee.org/document/10172720/"},"keyword":["Conference Short Papers"],"metadata":{"authorlinks":{}},"downloads":5},"bibtype":"inproceedings","biburl":"https://api.zotero.org/users/10198036/collections/2RHJXKSI/items?key=X0RoN8iO9RtTbrWfSkRasb7b&format=bibtex&limit=100","dataSources":["37aX9ioouEvzbunGp","JHDShjsHrs6ZHE4bz","srzvYyhPWR5PMfzfx","A6LHtF3YYwr9M952d"],"keywords":["conference short papers"],"search_terms":["detecting","scattered","tangled","quality","concerns","source","code","aid","maintenance","evolution","tasks","krasniqi"],"title":"Detecting Scattered and Tangled Quality Concerns in Source Code to Aid Maintenance and Evolution Tasks","year":2023,"downloads":5}