Requirement-to-Evaluation Alignment
This page briefly reviews how our coursework connects requirements, design goals, prototype features, and evaluation tasks.
Students and visitors need a tangible reason to move through campus instead of only reading static information.
DG1: Turn campus movement into active exploration.
Stylized narrative map, clue-based route, physical NFC-style check-in.
SF1: Treasure hunt map, clue drawer, NFC simulation, location unlock state.
High-fi React prototype: interactive pins, unlock modal, collection progress.
T1 tested clue readability and pin discovery; T2 tested NFC unlock discoverability.
Users need memorable moments that make campus exploration emotionally engaging and shareable.
DG2: Create memorable and shareable campus moments.
AR companion appears after location unlock and connects the real place with a playful mascot.
SF2: AR camera entry, 3D mascot model, photo-oriented interaction flow.
High-fi prototype: AR launch path and 3D mascot preview for unlocked places.
T3 measured AR activation, compatibility, latency, and model loading success.
Users need visible progression so the experience does not end after one successful check-in.
DG3: Sustain motivation through visible progression.
Passport-style stamp collection with achievement tiers and post-collection rewards.
SF3: Digital collection board, badge state, reward animations, avatar dressing.
High-fi prototype: collection gallery and 3D dressing room preview.
T5 tested accessory selection, 3D manipulation, gesture conflicts, and render performance.
Users need a way to connect their individual exploration with the wider campus community.
DG4: Connect individual exploration to community presence.
Geo-locked message wall attached to unlocked landmarks with anti-spoiler constraints.
SF4: Location-bound posting, wall feed, likes, Campass Credit reward loop.
High-fi prototype: message wall, location tag binding, social feedback loop.
T4 tested post creation, automatic location binding, and blocked empty submissions.
How to Read This Matrix
- R1-R4 are the core user requirements defined in the Requirements List.
- DG1-DG4 translate those requirements into design goals.
- SF1-SF4 identify the system features that operationalize each goal.
- Prototype Evidence points to what users can actually interact with in the high-fidelity prototype.
- Evaluation Evidence shows which usability tasks tested whether the requirement was met.
Portfolio-Level Mapping
| Requirement | Design Goal | Main Design Section | Prototype Section | Evaluation Task |
|---|---|---|---|---|
| R1 Tangible Check-in | DG1 Active exploration | Map paradigm and clue-based navigation | Treasure hunt map and NFC unlock | T1, T2 |
| R2 AR Companion | DG2 Memorable sharing | AR companion and mascot interaction | AR camera and 3D mascot | T3 |
| R3 Stamp Collection | DG3 Sustained motivation | Post-collection retention loop | Collection board and dressing room | T5 |
| R4 Message Wall | DG4 Community presence | Master-detail wall and anti-spoiler loop | Location-bound message wall | T4 |