Investigating changes in an existing codebase — Non-technical — Bachelor’s https://thesis.uya.no/proposals/find-your-way-through-legacy/?degree=bachelor#nontechnical-track FINAL RESULT An onboarding guide and code-documentation improvements. WHAT TO DO Find where developers get stuck when investigating unfamiliar code. DATA Flask 3.1.0 + 12 change-request cards (public) Prepare 4 cards per topic and a checked affected-file list. Flask 3.1.0: https://github.com/pallets/flask/releases/tag/3.1.0 HOW TO TEST IT Use the pinned Flask documentation and maintenance-task cards; map search steps and missing information. Plan 4 participant sessions. STEPS Study and improve 1. Read the starting sources and write the exact information problem. 2. Prepare Flask 3.1.0 + 12 change-request cards and a separate answer sheet or coding sheet. 3. Run one pilot and fix unclear questions. 4. Collect the named evidence with consent. 5. Group the findings with the stated categories and check the answer sheet. 6. Produce an onboarding guide and code-documentation improvements. List the three most useful changes. EXAMPLE TOOLS LibreOffice Writer/Calc, audio recorder with consent; no programming required. Equivalent tools are fine. ACCESS OR PEOPLE Recruit developers; code reading required, no implementation.