From d683922c1f181240dab5a28fa056b3ba652d8b97 Mon Sep 17 00:00:00 2001 From: Dominic Kempf Date: Thu, 30 Jul 2026 16:34:18 +0200 Subject: [PATCH] Add answers that whose issues somehow slipped --- review_answers/review_1_answers.md | 2 +- review_answers/review_2_answers.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/review_answers/review_1_answers.md b/review_answers/review_1_answers.md index 7eef86e..711111b 100644 --- a/review_answers/review_1_answers.md +++ b/review_answers/review_1_answers.md @@ -32,7 +32,7 @@ We did not intend to conduct a statistically significant, representative survey ### Comment 2 > Clarify the limitations of the small survey sample. -**Answer:** +**Answer:** We added a sentence that the small survey size does not allow quantitative analysis. --- diff --git a/review_answers/review_2_answers.md b/review_answers/review_2_answers.md index c8f26d3..342492c 100644 --- a/review_answers/review_2_answers.md +++ b/review_answers/review_2_answers.md @@ -168,7 +168,7 @@ A mobile app development was selected as a domain-agnostic example. We have adde ### Comment 15 > Module 8 ("Software maintenance service") lists three criteria for maintenance but criterion 3 ("mechanism for selecting projects") is not explained. How should institutions prioritize? Give at least two example prioritization strategies. -**Answer:** +**Answer:** The criterion reads: "For an overview of potential selection criteria see the section 'How to decide which software to sustain?' in Anzt et al, 2021." We would not want to redundantly repeat the information given there. ---