Investigating changes in an existing codebase — Non-technical https://thesis.uya.no/proposals/find-your-way-through-legacy/#nontechnical-track BACHELOR Final result: An onboarding guide and code-documentation improvements. Task: 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. Requires: Recruit developers; code reading required, no implementation. Method: 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. MASTER Final result: A table of failed code-navigation tasks and a checklist for updating repository documentation. Research question: Explain how developers form and revise a mental model of an unfamiliar codebase. Compare evidence paths across lookup/impact tasks and analyse contradictory cases, rather than only listing documentation gaps. Research result: An account of how representation and prior experience shape maintenance investigation. STEPS Study, compare and explain 1. Read the newest papers and write one exact research question. 2. State which people, cases or documents you will study and what you will compare. 3. Write the selection rules, questions and analysis steps for Flask 3.1.0 + 12 change-request cards. 4. Run one pilot. Fix unclear questions or categories, then keep the guide unchanged. 5. Collect the named interviews, cases or documents with consent. 6. Analyse them with the stated comparison or coding method. Keep disagreements and missing data. 7. Report the answer, the evidence and the practical output named in the assignment. 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. Orlikowski & Gash (1994) — Technological Frames: https://dl.acm.org/doi/10.1145/196734.196745 Compare how roles interpret the purpose, operation and use of the same system. 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 Where do source code and documentation fail to support a maintainer’s change-impact explanation? EXAMPLE TOOLS LibreOffice Writer/Calc, audio recorder with consent; no programming required. Equivalent tools are fine. FIRST THREE ACTIONS 1. Prepare a pilot with 2 examples from: Flask 3.1.0 + 12 change-request cards. Write the task questions and a reference answer sheet. 2. Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact. 3. Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample. INTERVIEW QUESTIONS - Which files would this change affect? - Show the evidence behind your answer. - Where did documentation or search fail to help? LITERATURE SEARCH software maintenance change impact knowledge documentation information systems qualitative scenario study DATA Flask 3.1.0 + 12 change-request cards (public) Prepare 4 cards per topic and a checked affected-file list. Recruit 8 Python developers for 45-minute sessions. Flask 3.1.0: https://github.com/pallets/flask/releases/tag/3.1.0 HOW TO TEST IT 8 Python developers perform timed searches, then explain their path retrospectively. Compare justified inspection files and strategies; record Flask familiarity. No graph or parser is built. FINAL RESULT A table of failed code-navigation tasks and a checklist for updating repository documentation. ACCESS OR PEOPLE Recruit developers; code reading required, no implementation. TEMPLATES https://thesis.uya.no/starters/find-your-way-through-legacy/nontechnical/study-plan.csv https://thesis.uya.no/starters/find-your-way-through-legacy/nontechnical/coding-sheet.csv https://thesis.uya.no/starters/find-your-way-through-legacy/nontechnical/literature-matrix.csv Use participant codes instead of names or email addresses.