Blame
|
1 | <!-- Generated from applied-computing-au vic/unit3-4/sat/C09-2026 by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. --> |
||||||
| 2 | # Case Study: FitTrack |
|||||||
| 3 | ||||||||
| 4 | ## Fitness App Beta Testing Scenario |
|||||||
| 5 | ||||||||
| 6 | **C9 Skills Development - Complete Beta Testing Example** |
|||||||
| 7 | ||||||||
| 8 | --- |
|||||||
| 9 | ||||||||
| 10 | ## Background Context |
|||||||
| 11 | ||||||||
| 12 | ### The FitTrack Pro App |
|||||||
| 13 | ||||||||
| 14 | **Company:** HealthTech Solutions |
|||||||
| 15 | **Product:** FitTrack Pro - Mobile fitness tracking application |
|||||||
| 16 | **Version:** 3.0 Beta (major update with new GPS algorithms) |
|||||||
| 17 | **Platform:** iOS and Android smartphones + Apple Watch/Wear OS integration |
|||||||
| 18 | ||||||||
| 19 | ### Recent Development |
|||||||
| 20 | ||||||||
| 21 | FitTrack Pro has undergone significant updates to improve GPS accuracy and battery efficiency. The development team has completed alpha testing and is ready for beta testing with real users in authentic exercise environments. |
|||||||
| 22 | ||||||||
| 23 | ### Target Users |
|||||||
| 24 | ||||||||
| 25 | - **Primary:** Recreational joggers and runners (ages 25-45) |
|||||||
| 26 | - **Secondary:** Fitness enthusiasts tracking multiple activities |
|||||||
| 27 | - **Tertiary:** Personal trainers monitoring client progress |
|||||||
| 28 | ||||||||
| 29 | --- |
|||||||
| 30 | ||||||||
| 31 | ## Beta Testing Plan Overview |
|||||||
| 32 | ||||||||
| 33 | ### Objective |
|||||||
| 34 | ||||||||
| 35 | Evaluate the app's performance in **real-world jogging scenarios** to validate GPS tracking accuracy, user interface effectiveness, and overall user experience during active exercise. |
|||||||
| 36 | ||||||||
| 37 | ### Key Features to Test |
|||||||
| 38 | ||||||||
| 39 | - **GPS tracking accuracy** for distance and route mapping |
|||||||
| 40 | - **Real-time data display** during exercise |
|||||||
| 41 | - **Battery performance** during extended tracking |
|||||||
| 42 | - **User interface usability** while exercising |
|||||||
| 43 | - **Data synchronisation** with wearable devices |
|||||||
| 44 | - **Post-exercise data analysis** and presentation |
|||||||
| 45 | ||||||||
| 46 | --- |
|||||||
| 47 | ||||||||
| 48 | ## Test Scenario: Tracking a Morning Jog |
|||||||
| 49 | ||||||||
| 50 | ### Pre-Test Setup |
|||||||
| 51 | ||||||||
| 52 | **Participant Profile:** |
|||||||
| 53 | ||||||||
| 54 | - **Name:** Sarah, 32, Marketing Manager |
|||||||
| 55 | - **Experience:** Regular jogger (3x per week, 5km average) |
|||||||
| 56 | - **Technology:** iPhone 14, Apple Watch Series 8 |
|||||||
| 57 | - **Previous app experience:** Used Strava and Nike Run Club |
|||||||
| 58 | ||||||||
| 59 | **Environment:** |
|||||||
| 60 | ||||||||
| 61 | - **Location:** Local park with mixed terrain (paths, grass, hills) |
|||||||
| 62 | - **Distance:** Planned 5km route (known distance for accuracy comparison) |
|||||||
| 63 | - **Weather:** Clear morning, 18°C, light breeze |
|||||||
| 64 | - **Time:** 7:00 AM (peak usage time for target demographic) |
|||||||
| 65 | ||||||||
| 66 | ### Phase 1: Preparation |
|||||||
| 67 | ||||||||
| 68 | **Duration:** 5 minutes |
|||||||
| 69 | ||||||||
| 70 | **User Actions:** |
|||||||
| 71 | ||||||||
| 72 | 1. **App installation** completed the previous evening |
|||||||
| 73 | 2. **Account setup** and basic profile information entered |
|||||||
| 74 | 3. **Device connectivity** - iPhone paired with Apple Watch |
|||||||
| 75 | 4. **GPS and permissions** verified and activated |
|||||||
| 76 | 5. **Pre-jog warm-up** while reviewing app interface |
|||||||
| 77 | ||||||||
| 78 | **Observer Notes:** |
|||||||
| 79 | ||||||||
| 80 | - Monitor ease of initial setup and configuration |
|||||||
| 81 | - Document any confusion with interface elements |
|||||||
| 82 | - Note time taken for GPS signal acquisition |
|||||||
| 83 | - Record any pre-exercise user questions or concerns |
|||||||
| 84 | ||||||||
| 85 | **Success Criteria:** |
|||||||
| 86 | ||||||||
| 87 | - App ready for tracking within 2 minutes |
|||||||
| 88 | - GPS signal acquired and stable |
|||||||
| 89 | - User feels confident to begin tracking |
|||||||
| 90 | ||||||||
| 91 | ### Phase 2: Starting the Activity |
|||||||
| 92 | ||||||||
| 93 | **Duration:** 2 minutes |
|||||||
| 94 | ||||||||
| 95 | **User Actions:** |
|||||||
| 96 | ||||||||
| 97 | 1. **Open FitTrack Pro** and navigate to "Start Workout" |
|||||||
| 98 | 2. **Select activity type** - "Outdoor Running" |
|||||||
| 99 | 3. **Configure settings** - audio feedback, display preferences |
|||||||
| 100 | 4. **Wait for GPS lock** - app indicates when ready |
|||||||
| 101 | 5. **Press "Start"** to begin tracking |
|||||||
| 102 | 6. **Begin jogging** at comfortable pace |
|||||||
| 103 | ||||||||
| 104 | **Data Collection Focus:** |
|||||||
| 105 | ||||||||
| 106 | - **Interface responsiveness** during activity initiation |
|||||||
| 107 | - **GPS acquisition time** and accuracy indicators |
|||||||
| 108 | - **Audio/visual feedback** clarity and usefulness |
|||||||
| 109 | - **User confidence** in starting the tracking process |
|||||||
| 110 | ||||||||
| 111 | **Observation Points:** |
|||||||
| 112 | ||||||||
| 113 | - Time from opening app to successful tracking start |
|||||||
| 114 | - User interaction difficulties while preparing to exercise |
|||||||
| 115 | - GPS signal strength and initial accuracy readings |
|||||||
| 116 | - Any hesitation or confusion during startup process |
|||||||
| 117 | ||||||||
| 118 | ### Phase 3: During the Jog |
|||||||
| 119 | ||||||||
| 120 | **Duration:** 30 minutes (5km route) |
|||||||
| 121 | ||||||||
| 122 | **User Actions:** |
|||||||
| 123 | ||||||||
| 124 | 1. **Maintain comfortable jogging pace** (approximately 6:00 min/km) |
|||||||
| 125 | 2. **Periodically check app display** for distance, pace, time |
|||||||
| 126 | 3. **Navigate through different terrains** - paved paths, grass, slight hills |
|||||||
| 127 | 4. **Test audio feedback** - distance milestones and pace updates |
|||||||
| 128 | 5. **Pause/resume functionality** - brief water break at 2.5km mark |
|||||||
| 129 | 6. **Monitor device battery** and app performance |
|||||||
| 130 | ||||||||
| 131 | **Systematic Data Collection:** |
|||||||
| 132 | ||||||||
| 133 | **Every 1km checkpoint:** |
|||||||
| 134 | ||||||||
| 135 | - **Distance accuracy** (compare to known route markers) |
|||||||
| 136 | - **Pace consistency** with perceived effort |
|||||||
| 137 | - **Route mapping** visual verification on app |
|||||||
| 138 | - **User interface visibility** in morning sunlight |
|||||||
| 139 | - **Audio feedback quality** and timing |
|||||||
| 140 | ||||||||
| 141 | **Environmental challenges:** |
|||||||
| 142 | ||||||||
| 143 | - **Tree cover areas** (potential GPS interference) |
|||||||
| 144 | - **Hill sections** (elevation tracking accuracy) |
|||||||
| 145 | - **Path intersections** (route accuracy maintenance) |
|||||||
| 146 | - **Crowded areas** (app performance under stress) |
|||||||
| 147 | ||||||||
| 148 | **User experience monitoring:** |
|||||||
| 149 | ||||||||
| 150 | - **Ease of checking stats** while jogging |
|||||||
| 151 | - **Screen readability** during movement |
|||||||
| 152 | - **Audio volume** and clarity over ambient noise |
|||||||
| 153 | - **Overall distraction level** from exercise focus |
|||||||
| 154 | ||||||||
| 155 | ### Phase 4: Ending the Activity |
|||||||
| 156 | ||||||||
| 157 | **Duration:** 3 minutes |
|||||||
| 158 | ||||||||
| 159 | **User Actions:** |
|||||||
| 160 | ||||||||
| 161 | 1. **Complete 5km route** and return to starting point |
|||||||
| 162 | 2. **Stop tracking** using app interface |
|||||||
| 163 | 3. **Save workout** with optional name/notes |
|||||||
| 164 | 4. **Review immediate summary** - time, distance, pace, route |
|||||||
| 165 | 5. **Check data synchronisation** with Apple Watch |
|||||||
| 166 | 6. **Export/share** workout data (optional) |
|||||||
| 167 | ||||||||
| 168 | **Critical Assessment Points:** |
|||||||
| 169 | ||||||||
| 170 | - **Ease of stopping** tracking while tired/sweaty |
|||||||
| 171 | - **Data accuracy** compared to known 5km route |
|||||||
| 172 | - **Summary presentation** - clarity and completeness |
|||||||
| 173 | - **Synchronisation success** across devices |
|||||||
| 174 | - **User satisfaction** with immediate results |
|||||||
| 175 | ||||||||
| 176 | ### Phase 5: Post-Exercise Review |
|||||||
| 177 | ||||||||
| 178 | **Duration:** 10 minutes (after cool-down) |
|||||||
| 179 | ||||||||
| 180 | **Detailed Analysis Tasks:** |
|||||||
| 181 | ||||||||
| 182 | 1. **Compare total distance** with known 5km route measurement |
|||||||
| 183 | 2. **Review route map** for accuracy and detail |
|||||||
| 184 | 3. **Analyse pace data** for consistency and accuracy |
|||||||
| 185 | 4. **Check elevation profile** against known terrain |
|||||||
| 186 | 5. **Examine battery usage** on both devices |
|||||||
| 187 | 6. **Test data export** functionality |
|||||||
| 188 | 7. **Compare results** with previous tracking apps |
|||||||
| 189 | ||||||||
| 190 | **Data Verification Methods:** |
|||||||
| 191 | ||||||||
| 192 | - **Manual route measurement** using Google Maps |
|||||||
| 193 | - **GPS watch comparison** (if available) |
|||||||
| 194 | - **Known distance markers** verification |
|||||||
| 195 | - **Previous workout comparison** for consistency |
|||||||
| 196 | - **Battery usage analysis** vs. competing apps |
|||||||
| 197 | ||||||||
| 198 | --- |
|||||||
| 199 | ||||||||
| 200 | ## Expected Outcomes |
|||||||
| 201 | ||||||||
| 202 | ### Quantitative Success Measures |
|||||||
| 203 | ||||||||
| 204 | - **Distance accuracy:** Within 2% of known 5km route (4.9-5.1km) |
|||||||
| 205 | - **GPS tracking:** Continuous signal with <5% data loss |
|||||||
| 206 | - **Battery efficiency:** <15% battery drain on smartphone |
|||||||
| 207 | - **Route accuracy:** 95% overlap with actual path taken |
|||||||
| 208 | - **Interface responsiveness:** All user inputs <2 second response |
|||||||
| 209 | ||||||||
| 210 | ### Qualitative Success Measures |
|||||||
| 211 | ||||||||
| 212 | - **User interface:** Easy to read and navigate while exercising |
|||||||
| 213 | - **Audio feedback:** Clear, timely, and helpful pace/distance updates |
|||||||
| 214 | - **Overall experience:** Positive user feeling about app reliability |
|||||||
| 215 | - **Workflow efficiency:** Intuitive start/stop/save process |
|||||||
| 216 | - **Data presentation:** Clear, comprehensive post-exercise summary |
|||||||
| 217 | ||||||||
| 218 | ### User Experience Targets |
|||||||
| 219 | ||||||||
| 220 | - **Confidence level:** User feels app accurately tracked their workout |
|||||||
| 221 | - **Satisfaction rating:** 8/10 or higher for overall experience |
|||||||
| 222 | - **Recommendation likelihood:** User would recommend to other joggers |
|||||||
| 223 | - **Continued use intention:** User plans to use for future workouts |
|||||||
| 224 | ||||||||
| 225 | --- |
|||||||
| 226 | ||||||||
| 227 | ## Feedback Collection Framework |
|||||||
| 228 | ||||||||
| 229 | ### Real-Time Feedback (During Exercise) |
|||||||
| 230 | ||||||||
| 231 | **Method:** Verbal observations recorded by test observer |
|||||||
| 232 | ||||||||
| 233 | - **Audio clarity** and usefulness ratings |
|||||||
| 234 | - **Interface visibility** in various lighting conditions |
|||||||
| 235 | - **Ease of interaction** while maintaining exercise rhythm |
|||||||
| 236 | - **Distraction level** from primary exercise focus |
|||||||
| 237 | ||||||||
| 238 | ### Immediate Post-Exercise Feedback (5 minutes post) |
|||||||
| 239 | ||||||||
| 240 | **Method:** Structured interview while experience is fresh |
|||||||
| 241 | ||||||||
| 242 | - **Overall satisfaction** with tracking accuracy |
|||||||
| 243 | - **User interface** effectiveness during exercise |
|||||||
| 244 | - **Comparison** with previous app experiences |
|||||||
| 245 | - **Immediate improvement** suggestions |
|||||||
| 246 | ||||||||
| 247 | ### Detailed Analysis Feedback (15 minutes post) |
|||||||
| 248 | ||||||||
| 249 | **Method:** Comprehensive questionnaire + data review |
|||||||
| 250 | ||||||||
| 251 | - **Accuracy assessment** of all tracked metrics |
|||||||
| 252 | - **Feature usefulness** evaluation (GPS, audio, interface) |
|||||||
| 253 | - **Battery performance** satisfaction |
|||||||
| 254 | - **Data export/sharing** functionality review |
|||||||
| 255 | - **Long-term usage** likelihood and recommendations |
|||||||
| 256 | ||||||||
| 257 | ### Follow-Up Feedback (24 hours later) |
|||||||
| 258 | ||||||||
| 259 | **Method:** Email survey |
|||||||
| 260 | ||||||||
| 261 | - **Data retention** and app stability |
|||||||
| 262 | - **Motivation impact** from tracked workout data |
|||||||
| 263 | - **Sharing experience** with social features |
|||||||
| 264 | - **Overall app ecosystem** integration satisfaction |
|||||||
| 265 | ||||||||
| 266 | --- |
|||||||
| 267 | ||||||||
| 268 | ## Critical Evaluation Points |
|||||||
| 269 | ||||||||
| 270 | ### Technical Performance |
|||||||
| 271 | ||||||||
| 272 | - **GPS accuracy** in various environmental conditions |
|||||||
| 273 | - **Battery optimization** compared to competing apps |
|||||||
| 274 | - **Device integration** seamless functionality |
|||||||
| 275 | - **App stability** during extended use |
|||||||
| 276 | - **Data synchronisation** reliability |
|||||||
| 277 | ||||||||
| 278 | ### User Experience Quality |
|||||||
| 279 | ||||||||
| 280 | - **Interface usability** while exercising |
|||||||
| 281 | - **Information hierarchy** - most important data prominent |
|||||||
| 282 | - **Accessibility** for users with different needs |
|||||||
| 283 | - **Learning curve** for new app features |
|||||||
| 284 | - **Error recovery** when problems occur |
|||||||
| 285 | ||||||||
| 286 | ### Competitive Analysis |
|||||||
| 287 | ||||||||
| 288 | - **Feature comparison** with established apps (Strava, Nike Run Club) |
|||||||
| 289 | - **Performance benchmarking** against industry standards |
|||||||
| 290 | - **User migration** ease from other platforms |
|||||||
| 291 | - **Unique value proposition** identification |
|||||||
| 292 | - **Market positioning** effectiveness |
|||||||
| 293 | ||||||||
| 294 | --- |
|||||||
| 295 | ||||||||
| 296 | ## Risk Factors and Mitigation |
|||||||
| 297 | ||||||||
| 298 | ### Environmental Risks |
|||||||
| 299 | ||||||||
| 300 | - **Weather changes** during testing |
|||||||
| 301 | - **GPS interference** in certain locations |
|||||||
| 302 | - **Safety concerns** while monitoring app during exercise |
|||||||
| 303 | - **Device security** during outdoor exercise |
|||||||
| 304 | ||||||||
| 305 | ### Technical Risks |
|||||||
| 306 | ||||||||
| 307 | - **App crashes** during critical tracking |
|||||||
| 308 | - **Battery failure** mid-exercise |
|||||||
| 309 | - **GPS signal loss** in problematic areas |
|||||||
| 310 | - **Data corruption** or loss during save |
|||||||
| 311 | ||||||||
| 312 | ### User Experience Risks |
|||||||
| 313 | ||||||||
| 314 | - **Participant fatigue** affecting feedback quality |
|||||||
| 315 | - **Observer interference** with natural usage |
|||||||
| 316 | - **Pressure to provide positive feedback** |
|||||||
| 317 | - **Learning curve** masking true usability |
|||||||
| 318 | ||||||||
| 319 | --- |
|||||||
| 320 | ||||||||
| 321 | ## Success Indicators for Beta Testing |
|||||||
| 322 | ||||||||
| 323 | ### Immediate Success (Test Day) |
|||||||
| 324 | ||||||||
| 325 | - **Successful completion** of full 5km tracking |
|||||||
| 326 | - **Positive user feedback** on core functionality |
|||||||
| 327 | - **Technical performance** meeting minimum benchmarks |
|||||||
| 328 | - **No critical bugs** or app failures during use |
|||||||
| 329 | ||||||||
| 330 | ### Short-Term Success (1 week) |
|||||||
| 331 | ||||||||
| 332 | - **Continued app usage** by beta tester |
|||||||
| 333 | - **Positive word-of-mouth** to other potential users |
|||||||
| 334 | - **Feature utilisation** beyond basic tracking |
|||||||
| 335 | - **Integration success** with user's fitness routine |
|||||||
| 336 | ||||||||
| 337 | ### Long-Term Success (1 month) |
|||||||
| 338 | ||||||||
| 339 | - **Regular usage pattern** established |
|||||||
| 340 | - **User retention** and engagement maintained |
|||||||
| 341 | - **Feature evolution** based on beta feedback |
|||||||
| 342 | - **Market readiness** for broader release |
|||||||
| 343 | ||||||||
| 344 | --- |
|||||||
| 345 | ||||||||
| 346 | ## Learning Applications for Students |
|||||||
| 347 | ||||||||
| 348 | ### C9-1 Planning Skills |
|||||||
| 349 | ||||||||
| 350 | **This case study demonstrates:** |
|||||||
| 351 | ||||||||
| 352 | - **Comprehensive test scenario** development |
|||||||
| 353 | - **Multiple data collection methods** integration |
|||||||
| 354 | - **User selection rationale** based on target demographics |
|||||||
| 355 | - **Success criteria** definition with measurable outcomes |
|||||||
| 356 | ||||||||
| 357 | ### C9-2 Execution Skills |
|||||||
| 358 | ||||||||
| 359 | **Students can analyse:** |
|||||||
| 360 | ||||||||
| 361 | - **Systematic approach** to user coordination |
|||||||
| 362 | - **Professional observation** techniques |
|||||||
| 363 | - **Real-time data collection** strategies |
|||||||
| 364 | - **Environmental variable** management |
|||||||
| 365 | ||||||||
| 366 | ### C9-3 Documentation Skills |
|||||||
| 367 | ||||||||
| 368 | **Documentation framework shows:** |
|||||||
| 369 | ||||||||
| 370 | - **Structured results** organisation |
|||||||
| 371 | - **Multiple data types** integration (quantitative/qualitative) |
|||||||
| 372 | - **Clear reporting** standards |
|||||||
| 373 | - **Evidence-based analysis** methodologies |
|||||||
| 374 | ||||||||
| 375 | ### C9-4 Recommendation Skills |
|||||||
| 376 | ||||||||
| 377 | **Students learn to develop:** |
|||||||
| 378 | ||||||||
| 379 | - **Evidence-linked modifications** from specific feedback |
|||||||
| 380 | - **Prioritised improvements** based on user impact |
|||||||
| 381 | - **Technical feasibility** assessment |
|||||||
| 382 | - **User experience enhancement** strategies |
|||||||
| 383 | ||||||||
| 384 | --- |
|||||||
| 385 | ||||||||
| 386 | ## Extended Activities for Students |
|||||||
| 387 | ||||||||
| 388 | ### Activity 1: Scenario Adaptation |
|||||||
| 389 | ||||||||
| 390 | **Task:** Adapt this jogging scenario for testing a different fitness app feature (cycling, weightlifting, yoga) **Skills:** Planning modification, target user adjustment, success criteria development |
|||||||
| 391 | ||||||||
| 392 | ### Activity 2: Data Collection Design |
|||||||
| 393 | ||||||||
| 394 | **Task:** Design 3 additional data collection methods for this scenario **Skills:** Methodology development, systematic data capture, professional feedback collection |
|||||||
| 395 | ||||||||
| 396 | ### Activity 3: User Selection Rationale |
|||||||
| 397 | ||||||||
| 398 | **Task:** Justify why Sarah was selected as a beta tester and identify 2 additional user types **Skills:** User representation analysis, diversity consideration, target audience understanding |
|||||||
| 399 | ||||||||
| 400 | ### Activity 4: Modification Recommendations |
|||||||
| 401 | ||||||||
| 402 | **Task:** Based on provided sample feedback, recommend 5 specific app improvements **Skills:** Evidence-based analysis, prioritisation, user-centred design thinking |
|||||||
| 403 | ||||||||
| 404 | --- |
|||||||
| 405 | ||||||||
| 406 | ## Assessment Connections |
|||||||
| 407 | ||||||||
| 408 | ### C9-1 Preparation Excellence |
|||||||
| 409 | ||||||||
| 410 | This case study exemplifies **comprehensive beta testing planning** that targets: |
|||||||
| 411 | ||||||||
| 412 | - **Appearance** (interface visibility during exercise) |
|||||||
| 413 | - **Functionality** (GPS tracking, data recording) |
|||||||
| 414 | - **User experience** (workout workflow, motivation impact) |
|||||||
| 415 | - **Requirements** (functional performance + non-functional usability) |
|||||||
| 416 | ||||||||
| 417 | ### Professional Standards |
|||||||
| 418 | ||||||||
| 419 | Demonstrates **industry-quality beta testing** with: |
|||||||
| 420 | ||||||||
| 421 | - **Clear objectives** and measurable outcomes |
|||||||
| 422 | - **Systematic methodology** with multiple data collection approaches |
|||||||
| 423 | - **Risk awareness** and mitigation planning |
|||||||
| 424 | - **User-centred focus** throughout testing process |
|||||||
| 425 | ||||||||
| 426 | ### Real-World Application |
|||||||
| 427 | ||||||||
| 428 | Shows students **authentic software development** practices used by professional teams for **user experience validation** and **product improvement**. |
|||||||
| 429 | ||||||||
| 430 | --- |
|||||||
| 431 | ||||||||
| 432 | _This case study provides a complete example of professional beta testing methodology that students can analyse, learn from, and adapt for their own C9 assessment preparation._ |
|||||||
