Investigating changes in an existing codebase — Technical — Bachelor’s https://thesis.uya.no/proposals/find-your-way-through-legacy/?degree=bachelor#technical-track FINAL RESULT A code-navigation tool with known limitations and onboarding instructions. WHAT TO DO Build a static call/dependency map for the pinned Flask checkout. DATA Flask 3.1.0 + 20 change-investigation questions (mixed) Use version-matched source, tests and docs. Write routing/session/error questions and independently review files worth inspecting; accept justified alternative files. Flask 3.1.0: https://github.com/pallets/flask/releases/tag/3.1.0 HOW TO TEST IT Validate sampled edges manually; observe students locating files for the specified maintenance tasks. Plan 4 participant sessions. STEPS Build and test 1. Read the starting sources and choose one established implementation method. 2. Write the requirements, data fields, system diagram and test cases. 3. Prepare Flask 3.1.0 + 20 change-investigation questions. Make the answer key and pass criteria before testing. 4. Build a working version of a code-navigation tool with known limitations and onboarding instructions. 5. Run function, integration and failure-case tests. Record each result. 6. Run the practical evaluation and list the changes the system still needs. EXAMPLE TOOLS Python, ast, NetworkX, Streamlit Equivalent tools are fine. ACCESS OR PEOPLE Recruit developers and a second answer-key reviewer.