Replication Package for HEAR framework

Abstract

HEAR (Human-Evidence-driven Alignment of Requirements) is a requirements engineering framework for building inclusive digital health software. In HEAR, an evidence-attributed requirement leads every iteration: it carries the evidence that raised it, serves as the criterion the build is judged against, and receives the verdict of evaluation as a versioned change. The package holds 3 parts, two complete replication projects and a reuse kit. The first project is the paper's case study. A medication-management application for older adults in Australia taken through four HEAR iterations. It contains the backlog and its realignments at each of the four versions, the personas and cognitive walkthrough tasks, the workshop guideline and questionnaires, the requirement-driven test cases and evidence-driven defects for every version, and the evidence consumed in each iteration, including survey data, walkthrough data, and coded workshop data.The second project is the generalisation study. A redesign branch of the diet-tracking application MyFitnessPal reconstructed from a frozen 2020 baseline and executed largely by an LLM agent under human prioritisation gates, with the same artefacts across its three versions.The third folder holds the framework diagram and instructions for running HEAR on a new project. Workshop recordings and transcripts are withheld under ethics approval ERM49124. 1_case_study/ medication management for older adults, four iterations iteration_map.csv evidence, instrument, realignment, and resulting version per iteration 1_backlog/ the 33 requirements with their realignments, v1 to v4 2_personas_cw/ persona specifications and cognitive walkthrough tasks 3_workshop/ workshop guideline, task scripts, observation record, questionnaires 4_test_cases/ requirement-driven test cases, v1 to v4 5_evidence_bugs/ evidence-driven defects, v1 to v4 6_evidence_data/ survey data, walkthrough data, and coded workshop data per iteration 2_generalisation/ MyFitnessPal redesign branch, three iterations iteration_map.csv as above, including the frozen v0 baseline and each evidence window 1_backlog/ the redesign backlog with its realignments, v1 to v3 2_personas_cw/ persona specifications and the frozen walkthrough task set 3_test_cases/ requirement-driven test cases, v1 to v3 4_evidence_bugs/ evidence-driven defects, v1 to v3 5_evidence_data/ app review data, coding method, and coded results per iteration 3_use_hear/ for teams running HEAR on their own project HEAR_framework.drawio the full framework diagram how_to_use_HEAR.md step-by-step instructions