Small apps built with AI — Non-technical https://thesis.uya.no/proposals/build-it-with-guardrails/#nontechnical-track BACHELOR Final result: A practical acceptance checklist and handover template. Task: Assess whether an AI-built administrative app can be handed over to its owner. Data: 3 fictional apps (planned) Leave, equipment and expenses; recruit 4 administrative users and 4 IT staff. Each packet names data fields, roles and support tasks. Requires: Recruit both roles; use document examples only. Method: Use the fictional handover packs and task scenarios; list missing ownership, support and access information. Plan 4 participant sessions. STEPS Study and improve 1. Read the starting sources and write the exact information problem. 2. Prepare 3 fictional apps 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 acceptance checklist and handover template. List the three most useful changes. MASTER Final result: Ownership matrix and a handover checklist. Research question: Explain why a working demonstration may still be unacceptable to its future owner. Compare developer and administrator expectations about support, permissions and responsibility across fixed handover packs. Research result: A theory-based model of acceptance and ownership gaps in AI-built apps. 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 3 fictional apps + 8 interviews. 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 A systematic literature review on the impact of AI models on the security of code generation (2024, systematic review): https://doi.org/10.3389/fdata.2024.1386720 Synthesizes current security risks and review needs for AI-generated code. Balancing Security and Correctness in Code Generation: An Empirical Study on Commercial Large Language Models (2025, peer-reviewed): https://doi.org/10.1109/TETCI.2024.3446695 Separates functional correctness from vulnerability outcomes in generated code. IS THEORY STARTING POINTS 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. Nissenbaum (2004) — Privacy as Contextual Integrity: https://digitalcommons.law.uw.edu/wlr/vol79/iss1/10/ Analyse recipient, purpose and information flow rather than treating privacy as a role label. 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 Where do administrative users and IT staff disagree about ownership of a small app? 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: 3 fictional apps + 8 interviews. 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 - Who owns this app after delivery? - Who approves access changes and tests releases? - What must be documented before a colleague can maintain it? LITERATURE SEARCH end user development AI generated applications governance maintenance qualitative scenario study DATA 3 fictional apps + 8 interviews (planned) Leave, equipment and expenses; recruit 4 administrative users and 4 IT staff. Each packet names data fields, roles and support tasks. HOW TO TEST IT Interview 4 administrative users and 4 IT staff using non-overlapping packs with clear or missing ownership. Compare deployment conditions and responsibility gaps; code access, testing and maintenance disagreements. FINAL RESULT Ownership matrix and a handover checklist. ACCESS OR PEOPLE Recruit both roles; use document examples only. TEMPLATES https://thesis.uya.no/starters/build-it-with-guardrails/nontechnical/study-plan.csv https://thesis.uya.no/starters/build-it-with-guardrails/nontechnical/coding-sheet.csv https://thesis.uya.no/starters/build-it-with-guardrails/nontechnical/literature-matrix.csv Use participant codes instead of names or email addresses.