Approving software changes — Non-technical — Bachelor’s https://thesis.uya.no/proposals/from-promise-to-proof/?degree=bachelor#nontechnical-track FINAL RESULT A practical approval checklist and responsibility map. WHAT TO DO Document what a reviewer checks before accepting a software change. DATA 12 paper change packets (planned) 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. HOW TO TEST IT Use patch/evidence packs in scenario interviews; group acceptance criteria and requests for missing evidence. Plan 4 participant sessions. STEPS Study and improve 1. Read the starting sources and write the exact information problem. 2. Prepare 12 paper change packets 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 a practical approval checklist and responsibility map. List the three most useful changes. EXAMPLE TOOLS LibreOffice Writer/Calc, audio recorder with consent; no programming required. Equivalent tools are fine. ACCESS OR PEOPLE Recruit IS students; no code writing or execution required.