Approving software changes
Link a written software requirement to the code and tests that demonstrate it is satisfied.
Technical
Bachelor’s · applied project
Final result
A release-review prototype and checklist evaluation.
Dataset + material
HumanEval/0–29 + clean/mutated variants
Derive checkable requirements from prompts. Create one demonstrably faulty edge-case mutation per task; retain clean controls and independently checked hidden witness tests.
What to do
- Build a release dashboard showing tests, changed files and a manual approval checklist.
How it is tested
Use the fixed code patches and independent test keys; verify displayed results and observe approval tasks. Plan 4 participant sessions.
Before you start
Example tools · Python, pytest, coverage.py, SQLite, HumanEval, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Recruit developers; run code in an isolated test environment.
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 HumanEval/0–29 + clean/mutated variants. Make the answer key and pass criteria before testing.
- Build a working version of a release-review prototype and checklist evaluation.
- 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
Traceability tool, 30 labelled mutations and reviewer results.
Dataset + material
HumanEval/0–29 + clean/mutated variants
Derive checkable requirements from prompts. Create one demonstrably faulty edge-case mutation per task; retain clean controls and independently checked hidden witness tests.
What to do
- Build a Python/pytest/coverage.py pipeline and typed SQLite graph linking requirement, code span, test, mutant, run and decision nodes.
- Cross linked graph versus flat CI evidence with clean/mutant and full/partial evidence using independent witness tests and unchanged underlying results.
- Verify referential integrity, trace accuracy, deterministic imports and mutant non-equivalence; report false approval/rejection, missed violations, evidence requests and time.
How it is tested
8 Python-reading developers review 10 non-overlapping cases with a linked matrix or an unlinked checklist containing identical evidence. Count unjustified approvals, missed violations, time and requests for missing evidence.
Before you start
Example tools · Python, pytest, coverage.py, SQLite, HumanEval, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Recruit developers; run code in an isolated test environment.
Start with these three actions
- Download HumanEval and record its revision; extract tasks 0–2 as a pilot.
- Turn each docstring into checkable requirements and map reference solutions/tests to them.
- Create and verify one edge-case fault per pilot task before building the review matrix.
Files, questions and sources
Pilot question: Does a requirement-to-test matrix improve evidence-based acceptance of a software change?
Literature search: requirements traceability acceptance evidence 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 HumanEval/0–29 + clean/mutated variants.
- Draw the user workflow, data model and system architecture. List the requirements and pass criteria.
- Build a working version of traceability tool, 30 labelled mutations and reviewer 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 when green tests create unjustified release confidence. Vary fault presence and evidence completeness independently; compare a traceable approval view with ordinary logs against an independent correctness key.
Research result: Evidence about how software assurance evidence shapes release decisions.
Current project literature
- Why don't we trace? A study on the barriers to software traceability in practice (2023) peer-reviewed
Provides current organizational and technical barriers to maintaining useful traceability. - What you see is what you trace: a two-stage interview study on traceability practices (2024) peer-reviewed
Connects trace links to review, impact analysis and practitioner work.
IS theory starting points
- Liu et al. (2023) — Is Your Code Generated by ChatGPT Really Correct? — Distinguish passing a public test suite from independently assessed correctness.
- Buçinca et al. (2021) — To Trust or to Think — Derive a competing explanation based on verification effort and overreliance.
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: requirements traceability acceptance evidence information systems
Non-technical
Bachelor’s · applied project
Final result
A practical approval checklist and responsibility map.
Material to create
12 paper change packets
Three prose requirements per packet. Cross 6 faulty/6 correct cases with 6 incomplete/6 complete evidence sets; use pass/fail tables and a written acceptance rule.
What to do
- Document what a reviewer checks before accepting a software change.
How it is tested
Use patch/evidence packs in scenario interviews; group acceptance criteria and requests for missing evidence. 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 IS students; no code writing or execution required.
Research method · Study and improve · 6 steps
- Read the starting sources and write the exact information problem.
- Prepare 12 paper change packets 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 a practical approval checklist and responsibility map. List the three most useful changes.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Acceptance checklist and analysis of evidence gaps.
Material to create
12 paper change packets + 8 final-year IS students
Three prose requirements per packet. Cross 6 faulty/6 correct cases with 6 incomplete/6 complete evidence sets; use pass/fail tables and a written acceptance rule.
What to do
- Prepare requirement descriptions, test-result tables and acceptance checklists.
- Ask reviewers to accept or reject each change and explain which evidence is missing.
How it is tested
Compare matrices with identical unlinked materials on non-overlapping cases. Novice participants approve, reject or request evidence; count policy-unjustified approvals and code reasons about evidence and responsibility.
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 IS students; no code writing or execution required.
Start with these three actions
- Prepare a pilot with 2 examples from: 12 fictional change-request packets + 8 IS students. 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: What evidence do IS reviewers need before accepting a requirement as satisfied?
Literature search: requirements traceability acceptance evidence information systems qualitative scenario study
Interview prompts
- Which requirement has sufficient evidence?
- What evidence is still missing before acceptance?
- Would you accept or reject the change, and why?
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 12 paper change packets + 8 final-year IS students.
- 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 when novice IS reviewers approve, reject or request more evidence. Analyse test confidence, verification effort and decision ownership across matched evidence packs; examine exception cases.
Research result: A specific novice-review framework for approval under incomplete software evidence.
Current project literature
- Why don't we trace? A study on the barriers to software traceability in practice (2023) peer-reviewed
Provides current organizational and technical barriers to maintaining useful traceability. - What you see is what you trace: a two-stage interview study on traceability practices (2024) peer-reviewed
Connects trace links to review, impact analysis and practitioner work.
IS theory starting points
- Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance — Compare verification cost with trust as explanations of observed decisions.
- 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: requirements traceability acceptance evidence information systems qualitative scenario study
Your degree, track and shortlist are saved in this browser.