Investigating changes in an existing codebase
Find which parts of an existing codebase would be affected by a requested change.
Technical
Bachelor’s · applied project
Final result
A code-navigation tool with known limitations and onboarding instructions.
Dataset + material
Flask 3.1.0 + 20 change-investigation questions
Use version-matched source, tests and docs. Write routing/session/error questions and independently review files worth inspecting; accept justified alternative files.
What to do
- Build a static call/dependency map for the pinned Flask checkout.
How it is tested
Validate sampled edges manually; observe students locating files for the specified maintenance tasks. Plan 4 participant sessions.
Before you start
Example tools · Python, ast, NetworkX, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Recruit developers and a second answer-key reviewer.
Research method · Build and test · 6 steps
- Read the starting sources and choose one established implementation method.
- Write the requirements, data fields, system diagram and test cases.
- Prepare Flask 3.1.0 + 20 change-investigation questions. Make the answer key and pass criteria before testing.
- Build a working version of a code-navigation tool with known limitations and onboarding instructions.
- Run function, integration and failure-case tests. Record each result.
- Run the practical evaluation and list the changes the system still needs.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Dependency viewer, answer key and comparison results.
Dataset + material
Flask 3.1.0 + 20 change-investigation questions
Use version-matched source, tests and docs. Write routing/session/error questions and independently review files worth inspecting; accept justified alternative files.
What to do
- Parse pinned Flask 3.1.0 with Python ast into modules, symbols, imports, direct calls, routes and test references; mark unresolved dynamic edges explicitly.
- Compare NetworkX graph-plus-search with identical ripgrep/documentation search on an independently reviewed lookup/impact question set.
- Verify parser fixtures, sampled-edge precision and fact parity; report necessary-file precision/recall, first-relevant rank, incorrect files, time and test choices.
How it is tested
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.
Before you start
Example tools · Python, ast, NetworkX, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Recruit developers and a second answer-key reviewer.
Start with these three actions
- Check out Flask tag 3.1.0 and run its tests in an isolated development environment.
- Trace one question each on routing, sessions and errors manually; get a second reviewer to check answers.
- Parse imports first and document dynamic behaviour the graph cannot represent.
Files, questions and sources
Pilot question: Does a dependency graph improve developers’ ability to identify files affected by a change?
Literature search: software maintenance change impact knowledge documentation information systems
Empty CSV templates: data-plan.csv · evaluation.csv · literature-matrix.csv
Download starter instructionsResearch method · Design, build and test (DSR) · 7 steps
- Read the newest papers and list the closest existing systems.
- Write down the versions, fields, data split, case assignment, random seeds and correct answers for Flask 3.1.0 + 20 change-investigation questions.
- Draw the user workflow, data model and system architecture. List the requirements and pass criteria.
- Build a working version of dependency viewer, answer key and comparison results.
- Test every function, connection and failure case. Save the failed tests as well as the passed tests.
- Compare the system with the named alternative. Then run the user task or decision task in the assignment.
- Report the measured result, the failed cases and the design lessons another team can reuse.
Research question and sources
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.
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
Studies how practitioners comprehend large unfamiliar programs in realistic maintenance work. - Translations Alone Do Not Help Programmers Work With Unfamiliar Abstractions (2024) research report
Provides a 98-participant evaluation of support for work with unfamiliar code abstractions.
IS theory starting points
- Vessey & Galletta (1991) — Cognitive Fit — Test whether a representation helps one kind of task more than another.
- Wang & Strong (1996) — Beyond Accuracy — 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.
Search terms: software maintenance change impact knowledge documentation information systems
Non-technical
Bachelor’s · applied project
Final result
An onboarding guide and code-documentation improvements.
Dataset
Flask 3.1.0 + 12 change-request cards
Prepare 4 cards per topic and a checked affected-file list.
What to do
- Find where developers get stuck when investigating unfamiliar code.
How it is tested
Use the pinned Flask documentation and maintenance-task cards; map search steps and missing information. Plan 4 participant sessions.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit developers; code reading required, no implementation.
Research method · Study and improve · 6 steps
- Read the starting sources and write the exact information problem.
- Prepare Flask 3.1.0 + 12 change-request cards and a separate answer sheet or coding sheet.
- Run one pilot and fix unclear questions.
- Collect the named evidence with consent.
- Group the findings with the stated categories and check the answer sheet.
- Produce an onboarding guide and code-documentation improvements. List the three most useful changes.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
A table of failed code-navigation tasks and a checklist for updating repository documentation.
Dataset
Flask 3.1.0 + 12 change-request cards
Prepare 4 cards per topic and a checked affected-file list. Recruit 8 Python developers for 45-minute sessions.
What to do
- Prepare 12 change cards for the fixed Flask version.
- Compare code/tests-only investigations with code/tests plus version-matched documentation.
How it is tested
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.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit developers; code reading required, no implementation.
Start with these three actions
- Prepare a pilot with 2 examples from: Flask 3.1.0 + 12 change-request cards. Write the task questions and a reference answer sheet.
- Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact.
- Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample.
Files, questions and sources
Pilot question: Where do source code and documentation fail to support a maintainer’s change-impact explanation?
Literature search: software maintenance change impact knowledge documentation information systems qualitative scenario study
Interview prompts
- Which files would this change affect?
- Show the evidence behind your answer.
- Where did documentation or search fail to help?
Empty CSV templates: study-plan.csv · coding-sheet.csv · literature-matrix.csv
Download starter instructionsResearch method · Study, compare and explain · 7 steps
- Read the newest papers and write one exact research question.
- State which people, cases or documents you will study and what you will compare.
- Write the selection rules, questions and analysis steps for Flask 3.1.0 + 12 change-request cards.
- Run one pilot. Fix unclear questions or categories, then keep the guide unchanged.
- Collect the named interviews, cases or documents with consent.
- Analyse them with the stated comparison or coding method. Keep disagreements and missing data.
- Report the answer, the evidence and the practical output named in the assignment.
Research question and sources
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.
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
Studies how practitioners comprehend large unfamiliar programs in realistic maintenance work. - Translations Alone Do Not Help Programmers Work With Unfamiliar Abstractions (2024) research report
Provides a 98-participant evaluation of support for work with unfamiliar code abstractions.
IS theory starting points
- Vessey & Galletta (1991) — Cognitive Fit — Test whether a representation helps one kind of task more than another.
- Orlikowski & Gash (1994) — Technological Frames — 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.
Search terms: software maintenance change impact knowledge documentation information systems qualitative scenario study
Your degree, track and shortlist are saved in this browser.