<!-- 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. -->
## 9-4 Software Modifications Mindmap

This mindmap shows you how to document software changes based on your beta testing results. Each branch represents a different assessment level.

How to use this mindmap:

1. Start with your beta test results (user feedback, bug reports, observations)
2. Follow the progression: IDENTIFY → OUTLINE → RECOMMEND → EXPLAIN → EVALUATE  
3. Use the 5 categories (🪲 Bugs, 💡 Features, 🔍 Usability, ⚡ Performance, 💬 Satisfaction) to organise your findings
4. Each level builds on the previous - aim for the highest level you can achieve

Remember: Every modification you suggest must be backed by evidence from your beta testing!

```plantuml
@startmindmap
* C9-4 Software Modifications

** C9-4-1 IDENTIFY
*** Bug Reports
**** List issues found
**** Count affected users
*** Feature Requests  
**** Top 3-5 requests
**** User demand level

** C9-4-3 OUTLINE
*** Organize by Category
**** 🪲 Bugs
**** 💡 Features  
**** 🔍 Usability
**** ⚡ Performance
**** 💬 Satisfaction
*** Set Priorities
**** High/Medium/Low

** C9-4-5 RECOMMEND
*** Link to Evidence
**** "X out of Y testers..."
**** User quotes
*** Formal Suggestions
**** Specific changes
**** Expected outcomes

** C9-4-7 EXPLAIN
*** WHY Needed
**** Solve user problems
**** Improve experience
*** Purpose & Impact
**** Expected benefits
**** Success measures

** C9-4-9 EVALUATE
*** Critical Analysis
**** Will it actually work?
**** Any implementation risks?
*** Success Criteria
**** How to measure improvement
**** Follow-up testing needed

@endmindmap
```