Investigating changes in an existing codebase — Technical https://thesis.uya.no/proposals/find-your-way-through-legacy/#technical-track BACHELOR Final result: A code-navigation tool with known limitations and onboarding instructions. Task: 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. Requires: Recruit developers and a second answer-key reviewer. Method: 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. MASTER Final result: Dependency viewer, answer key and comparison results. Research question: Investigate whether dependency views help impact analysis more than exact symbol lookup. Compare graph navigation with version-matched documentation; record unresolved dynamic edges and distinguish task-type effects from Flask familiarity. Research result: Design knowledge about static context, uncertainty and maintenance-task fit. STEPS Design, build and test (DSR) 1. Read the newest papers and list the closest existing systems. 2. Write down the versions, fields, data split, case assignment, random seeds and correct answers for Flask 3.1.0 + 20 change-investigation questions. 3. Draw the user workflow, data model and system architecture. List the requirements and pass criteria. 4. Build a working version of dependency viewer, answer key and comparison results. 5. Test every function, connection and failure case. Save the failed tests as well as the passed tests. 6. Compare the system with the named alternative. Then run the user task or decision task in the assignment. 7. Report the measured result, the failed cases and the design lessons another team can reuse. CURRENT PROJECT LITERATURE How Do Developers Approach Their First Bug in an Unfamiliar Code Base? An Exploratory Study of Large Program Comprehension (2024, peer-reviewed workshop): https://www.ppig.org/papers/2024-ppig-35th-bexell/ Studies how practitioners comprehend large unfamiliar programs in realistic maintenance work. Translations Alone Do Not Help Programmers Work With Unfamiliar Abstractions (2024, research report): https://www2.eecs.berkeley.edu/Pubs/TechRpts/2024/EECS-2024-224.html Provides a 98-participant evaluation of support for work with unfamiliar code abstractions. IS THEORY STARTING POINTS Vessey & Galletta (1991) — Cognitive Fit: https://pubsonline.informs.org/doi/10.1287/isre.2.1.63 Test whether a representation helps one kind of task more than another. Wang & Strong (1996) — Beyond Accuracy: https://www.tandfonline.com/doi/abs/10.1080/07421222.1996.11518099 Distinguish accuracy, completeness, representation and fitness for the task. Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points. PILOT QUESTION Does a dependency graph improve developers’ ability to identify files affected by a change? EXAMPLE TOOLS Python, ast, NetworkX, Streamlit Equivalent tools are fine. FIRST THREE ACTIONS 1. Check out Flask tag 3.1.0 and run its tests in an isolated development environment. 2. Trace one question each on routing, sessions and errors manually; get a second reviewer to check answers. 3. Parse imports first and document dynamic behaviour the graph cannot represent. LITERATURE SEARCH software maintenance change impact knowledge documentation information systems 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 8 Python developers answer 10 non-overlapping questions using graph-plus-search or the same search alone. Measure justified files found, incorrect files, time and regression-test choices; record Flask familiarity. FINAL RESULT Dependency viewer, answer key and comparison results. ACCESS OR PEOPLE Recruit developers and a second answer-key reviewer. TEMPLATES https://thesis.uya.no/starters/find-your-way-through-legacy/technical/data-plan.csv https://thesis.uya.no/starters/find-your-way-through-legacy/technical/evaluation.csv https://thesis.uya.no/starters/find-your-way-through-legacy/technical/literature-matrix.csv Use participant codes instead of names or email addresses.