Approving software changes — Technical https://thesis.uya.no/proposals/from-promise-to-proof/#technical-track BACHELOR Final result: A release-review prototype and checklist evaluation. Task: Build a release dashboard showing tests, changed files and a manual approval checklist. Data: HumanEval/0–29 + clean/mutated variants (mixed) Derive checkable requirements from prompts. Create one demonstrably faulty edge-case mutation per task; retain clean controls and independently checked hidden witness tests. Requires: Recruit developers; run code in an isolated test environment. Method: Use the fixed code patches and independent test keys; verify displayed results and observe approval 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 HumanEval/0–29 + clean/mutated variants. Make the answer key and pass criteria before testing. 4. Build a working version of a release-review prototype and checklist evaluation. 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: Traceability tool, 30 labelled mutations and reviewer results. 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. 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 HumanEval/0–29 + clean/mutated variants. 3. Draw the user workflow, data model and system architecture. List the requirements and pass criteria. 4. Build a working version of traceability tool, 30 labelled mutations and reviewer 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 Why don't we trace? A study on the barriers to software traceability in practice (2023, peer-reviewed): https://doi.org/10.1007/s00766-023-00408-9 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): https://doi.org/10.1007/s00766-024-00419-0 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?: https://proceedings.neurips.cc/paper_files/paper/2023/file/43e9d647ccd3e4b7b5baab53f0368686-Paper-Conference.pdf Distinguish passing a public test suite from independently assessed correctness. Buçinca et al. (2021) — To Trust or to Think: https://doi.org/10.1145/3449287 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. PILOT QUESTION Does a requirement-to-test matrix improve evidence-based acceptance of a software change? EXAMPLE TOOLS Python, pytest, coverage.py, SQLite, HumanEval, Streamlit Equivalent tools are fine. FIRST THREE ACTIONS 1. Download HumanEval and record its revision; extract tasks 0–2 as a pilot. 2. Turn each docstring into checkable requirements and map reference solutions/tests to them. 3. Create and verify one edge-case fault per pilot task before building the review matrix. LITERATURE SEARCH requirements traceability acceptance evidence information systems DATA HumanEval/0–29 + clean/mutated variants (mixed) Derive checkable requirements from prompts. Create one demonstrably faulty edge-case mutation per task; retain clean controls and independently checked hidden witness tests. HumanEval: https://github.com/openai/human-eval HOW TO TEST IT 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. FINAL RESULT Traceability tool, 30 labelled mutations and reviewer results. ACCESS OR PEOPLE Recruit developers; run code in an isolated test environment. TEMPLATES https://thesis.uya.no/starters/from-promise-to-proof/technical/data-plan.csv https://thesis.uya.no/starters/from-promise-to-proof/technical/evaluation.csv https://thesis.uya.no/starters/from-promise-to-proof/technical/literature-matrix.csv Use participant codes instead of names or email addresses.