Approving software changes — Non-technical https://thesis.uya.no/proposals/from-promise-to-proof/#nontechnical-track BACHELOR Final result: A practical approval checklist and responsibility map. Task: 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. Requires: Recruit IS students; no code writing or execution required. Method: 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. MASTER Final result: Acceptance checklist and analysis of evidence gaps. 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. 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 12 paper change packets + 8 final-year IS students. 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 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 Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance: https://doi.org/10.1145/3579605 Compare verification cost with trust as explanations of observed decisions. 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 What evidence do IS reviewers need before accepting a requirement as satisfied? 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: 12 fictional change-request packets + 8 IS students. 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 requirement has sufficient evidence? - What evidence is still missing before acceptance? - Would you accept or reject the change, and why? LITERATURE SEARCH requirements traceability acceptance evidence information systems qualitative scenario study DATA 12 paper change packets + 8 final-year IS students (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 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. FINAL RESULT Acceptance checklist and analysis of evidence gaps. ACCESS OR PEOPLE Recruit IS students; no code writing or execution required. TEMPLATES https://thesis.uya.no/starters/from-promise-to-proof/nontechnical/study-plan.csv https://thesis.uya.no/starters/from-promise-to-proof/nontechnical/coding-sheet.csv https://thesis.uya.no/starters/from-promise-to-proof/nontechnical/literature-matrix.csv Use participant codes instead of names or email addresses.