As discussed in #109, the RQs should be revised. The connection to MI should be more obvious, and the RQs should not be a surprise to the reader. That is, the RQ goals should follow organically from the introductory text.
I believe the RQs can be re-written to reflect the "state of the practice" context of the work. We want to know what is currently done. The comparison of MI software to other domains can also be worked into the RQs, to explain why some of the data is collected, and to motivate the recommendations.
smiths
commented
2 years ago
As discussed in #109, the RQs should be revised. The connection to MI should be more obvious, and the RQs should not be a surprise to the reader. That is, the RQ goals should follow organically from the introductory text.
I believe the RQs can be re-written to reflect the "state of the practice" context of the work. We want to know what is currently done. The comparison of MI software to other domains can also be worked into the RQs, to explain why some of the data is collected, and to motivate the recommendations.