For each reply we show the original reply and a tracking document that shows how well the reply covers each of the 30 issues. On average, each reply addressed only 10 of the 30 issues.
For comparison, we also show a reply based on problem-oriented requirements. It covers 29 of the 30 issues. Further it covers issues not mentioned by stakeholders, but needed in most software acquisitions, for instance: ease of learning, response time, security, system maintenance, and phasing-out requirements. None of these were mentioned in the 8 replies.
The published paper in Software 2022 - with improved formatting: User story quality in practice: A case study
The project description: The analysis report
Reply S: Using problem-oriented requirements: Reply, Tracked