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 | ## 9-4 Software Modifications Mindmap |
|||||||
| 3 | ||||||||
| 4 | This mindmap shows you how to document software changes based on your beta testing results. Each branch represents a different assessment level. |
|||||||
| 5 | ||||||||
| 6 | How to use this mindmap: |
|||||||
| 7 | ||||||||
| 8 | 1. Start with your beta test results (user feedback, bug reports, observations) |
|||||||
| 9 | 2. Follow the progression: IDENTIFY → OUTLINE → RECOMMEND → EXPLAIN → EVALUATE |
|||||||
| 10 | 3. Use the 5 categories (🪲 Bugs, 💡 Features, 🔍 Usability, ⚡ Performance, 💬 Satisfaction) to organise your findings |
|||||||
| 11 | 4. Each level builds on the previous - aim for the highest level you can achieve |
|||||||
| 12 | ||||||||
| 13 | Remember: Every modification you suggest must be backed by evidence from your beta testing! |
|||||||
| 14 | ||||||||
| 15 | ```plantuml |
|||||||
| 16 | @startmindmap |
|||||||
| 17 | * C9-4 Software Modifications |
|||||||
| 18 | ||||||||
| 19 | ** C9-4-1 IDENTIFY |
|||||||
| 20 | *** Bug Reports |
|||||||
| 21 | **** List issues found |
|||||||
| 22 | **** Count affected users |
|||||||
| 23 | *** Feature Requests |
|||||||
| 24 | **** Top 3-5 requests |
|||||||
| 25 | **** User demand level |
|||||||
| 26 | ||||||||
| 27 | ** C9-4-3 OUTLINE |
|||||||
| 28 | *** Organize by Category |
|||||||
| 29 | **** 🪲 Bugs |
|||||||
| 30 | **** 💡 Features |
|||||||
| 31 | **** 🔍 Usability |
|||||||
| 32 | **** ⚡ Performance |
|||||||
| 33 | **** 💬 Satisfaction |
|||||||
| 34 | *** Set Priorities |
|||||||
| 35 | **** High/Medium/Low |
|||||||
| 36 | ||||||||
| 37 | ** C9-4-5 RECOMMEND |
|||||||
| 38 | *** Link to Evidence |
|||||||
| 39 | **** "X out of Y testers..." |
|||||||
| 40 | **** User quotes |
|||||||
| 41 | *** Formal Suggestions |
|||||||
| 42 | **** Specific changes |
|||||||
| 43 | **** Expected outcomes |
|||||||
| 44 | ||||||||
| 45 | ** C9-4-7 EXPLAIN |
|||||||
| 46 | *** WHY Needed |
|||||||
| 47 | **** Solve user problems |
|||||||
| 48 | **** Improve experience |
|||||||
| 49 | *** Purpose & Impact |
|||||||
| 50 | **** Expected benefits |
|||||||
| 51 | **** Success measures |
|||||||
| 52 | ||||||||
| 53 | ** C9-4-9 EVALUATE |
|||||||
| 54 | *** Critical Analysis |
|||||||
| 55 | **** Will it actually work? |
|||||||
| 56 | **** Any implementation risks? |
|||||||
| 57 | *** Success Criteria |
|||||||
| 58 | **** How to measure improvement |
|||||||
| 59 | **** Follow-up testing needed |
|||||||
| 60 | ||||||||
| 61 | @endmindmap |
|||||||
| 62 | ``` |
|||||||
| 63 | ||||||||
