Peer Review Feedback Response to #153: Missing Components and Requirements for Metrics Collection

Open
#186 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@johnso9 is already working on this.

Since Nov 1, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
tex

Research direction

The work is in the SRS document: Section S.1 needs a component for collecting and storing metrics, and Section S.2 needs SFRs listing which metrics are recorded, how they are stored, and how developers export them. Read the feedback in #153, SSR-002 and the existing fit criteria first, so the new text matches the document's style. Done means the new components and SFRs exist and SSR-002 is consistent with them.

Written by the indexing model from the issue text.

Description

Description of the Feedback

The following feedback was provided for the SRS's Components and Functionality (Sections S.1 and S.2) (see #153):

"Many different sections of the document refer to data-driven usability testing and metric collection.
However, S.1 doesn't include any component responsible for collecting or storing those metrics.
S.2 doesn't have any SFRs describing which metrics are recorded, how they're stored, or how developers export them.
SSR-002 protects data that no requirement actually creates."

"The gameplay side of S.2 is very thorough, and the fit criteria give a clear picture of how the game will look and play. Making the testing and metrics side as concrete would really tie the SRS back to the project's research goal."

Action Items

  • Make testing + metrics component(s) to strengthen that aspect of system
  • More thoroughly describe which metrics will be recorded through SFRs
  • Ensure that these updates are consistent with SSR-002 (secure storage and protection of this collected information)
Dominant language
TeX
Stars
0
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
52

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Aeolus-Software/RealmForge

All issues in Aeolus-Software/RealmForge

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.