logseq/pages/ICSOFT_2025_34.md

type:: REVIEWS tags:: year:: 2025 venue:: ICSOFT full-title:: Automated Quality Model Management Using Semantic Technologies date-start:: 09-03-2025 - 19:45 date-submitted:: 09-03-2025 external-links:: status:: DONE deadline-submission:: file:: @ICSOFT_2025_34 parent:: todoist:: https://app.todoist.com/app/task/icsoft-2025-reviews-assignment-notification-6XH3vgJg7wV2rPjg

- ### [[Highlights]]
	- # Annotazioni  
	  
	  (9/3/2025, 19:47:45)
	- “Abstract” ([Plösch et al., p. 1](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=1&annotation=68FJF4NS)) #ff6666  
	  
	  *This needs major revision. It is not effective in presenting neither the problem nor the solution.*
	- “The starting point for this paper and service for the query-based generation of quality models was the requirement to be able to manage software quality models dynamically, as detailed domain knowledge is usually required for this task.” ([Plösch et al., p. 1](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=1&annotation=ZVFZMCHK)) #ff6666  
	  
	  *It does not parse.*
	- “and service” ([Plösch et al., p. 1](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=1&annotation=GDM4TB2A)) #ff6666
	- “(Wagner et al., 2012a)” ([Plösch et al., p. 1](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=1&annotation=KQLU8NNZ)) #ff6666  
	  
	  *tha authors of ... state....*
	- “The Quamoco meta-model has been selected and, therefore, all further steps are going to be performed using this specific QM.” ([Plösch et al., p. 1](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=1&annotation=LH5XRUH4)) #ffd400  
	  
	  *Which stepts, of what... what is the problem to be solved?*
	- “it changes relatively fast compared to more static-like data in SonarQube-like metrics and rules.” ([Plösch et al., p. 1](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=1&annotation=HZCZHDH2)) #ffd400  
	  
	  *what does it mean that data changes dynamically? What kinds of data are you talking about? What are the types of systems of interest?*
	- “A quality profile can be seen as a collection of metrics and rules which are grouped into a profile. These profiles are then associated with projects” ([Plösch et al., p. 1](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=1&annotation=E552CF7Z)) #5fb236
	- “Based on this context, the following RQs were defined:” ([Plösch et al., p. 2](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=2&annotation=ZSCZ3CGB)) #ffd400  
	  
	  *The used dictionary/terminology should be introduced early in the paper. The authors assume too many terms that have to be properly defined. Authors assume that readers are aware of SonarQube and constituting components. They also assume that the way quality models can be defined in SonarQube are in the knowledge of the readers.*
	- “categorization of software metrics based on machine learning algorithms suitable?” ([Plösch et al., p. 2](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=2&annotation=76EFPVXV)) #ffd400  
	  
	  *What does it mean? What's that?*
	- “”An effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it.”” ([Plösch et al., p. 2](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=2&annotation=LTQCJ7XY)) #ffd400  
	  
	  *Is this a definition of software quality? Is Software Quality a process?*
	- “per d” ([Plösch et al., p. 2](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=2&annotation=MARHQ2SF)) #ff6666
	- “While there is still ongoing work in how to structure the abstract term Software Qualtiy, there are no approaches known from the scientific literature that support systematic tailoring of quality models to the quality requirements of a software project.” ([Plösch et al., p. 2](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=2&annotation=NQRDXZLE)) #ffd400  
	  
	  *That's no true!*
	- “dynamic aspects is to collect usage data of rules’ issues in projects within SonarQube which then can be further used for tailoring QMs” ([Plösch et al., p. 4](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=4&annotation=LF3VFAL3)) #5fb236
	- “where the ratio of related issues that are marked as won’t fix to the total number of issues of the corresponding rule is larger than x%. This could make sense as it is an indicator that the related rule is not suitable for a specific application domain” ([Plösch et al., p. 4](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=4&annotation=6UBENQC6)) #5fb236
	- “Main component” ([Plösch et al., p. 7](zotero://select/library/items/SA3WKFXB)) ([pdf](zotero://open-pdf/library/items/KYQLJ9PU?page=7&annotation=L6SCSIR4)) #ff6666
- ### [[Comments]]
	- SUMMARY: The paper presents an approach to support the specification of quality models to be developed in SonarQube. A knowledge graph representing the main components of quality models has been devised. Machine learning techniques are employed to create the hierarchical structure of quality models with respect to the available software metrics.
	- COMMENTS: Although the paper is about an interesting and relevant problem, it does not properly present the problem to be solved and the proposed solution. Thus, the main concerns of the paper are related to its presentation as detailed below:
		- The abstract does not effectively present the problem or solution. It should concisely outline the research gap, the proposed approach, and the key contributions.
		- Important terms such as "quality models," "SonarQube," and "quality metrics" should be introduced earlier in the paper to help the reader follow the discussion. The paper assumes familiarity with SonarQube's structure and how it defines quality models, which should be explicitly clarified.
		- The term "dynamic data" is vague. The paper should specify what kinds of data change dynamically and what types of systems this applies.
		- The statement *"While there is still ongoing work in how to structure the abstract term Software Quality, there are no approaches known from the scientific literature that support systematic tailoring of quality models to the quality requirements of a software project."* is inaccurate. Relevant literature does exist, and the authors should either justify their claim with citations or revise it. Authors should consider for instance the work done in the context of the OSSMETER project http://www.ossmeter.org/
		- The dynamic aspects of quality models are not explained thoroughly, and explanatory examples or use cases would help illustrate the practical impact of the proposed approach.
		- There are many grammar and typographical errors to be fixed.
	- To summarize, the paper presents an interesting topic, but substantial revisions are necessary to improve the clarity, presentation of the novelty, and justification of claims.
- ### [[REVIEWS/Notes]]
- ### YELLOW CONCERNS
  background-color:: yellow
	- {{query (and [[ffd400]] [[ICSOFT_2025_34]] )}}
	  collapsed:: true
- ### ❓️Questions
	- {{query (and [[question]] [[ICSOFT_2025_34]] )[[question]]}}
	  query-table:: true
	  query-properties:: [:block]