Checking procurement proposals — Technical https://thesis.uya.no/proposals/compare-the-evidence/#technical-track BACHELOR Final result: A comparison prototype and usability report. Task: Build a procurement comparison table with links to supporting bid paragraphs. Data: 3 fictional IT tenders × 4 supplier bids (planned) Each tender has 10 requirements. Vary 0–4 unsupported claims and 0–2 contradictions per bid, including clean bids. Keep a hidden, independently reviewed answer key. Requires: Recruit students and an independent answer-key reviewer. Method: Use fictional bids and the hidden issue key; test link correctness and observe reviewers completing comparison 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 3 fictional IT tenders × 4 supplier bids. Make the answer key and pass criteria before testing. 4. Build a working version of a comparison prototype and usability report. 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: Comparison screen, bid set and review results. Research question: Test whether source navigation helps reviewers distinguish documented evidence from persuasive claims. Compare identical bids with direct paragraph links versus equivalent document, page and paragraph references; separate clean bids and fault types. Research result: Measured effects of source links on missed claims, false alarms, review time and reviewer confidence. 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 3 fictional IT tenders × 4 supplier bids. 3. Draw the user workflow, data model and system architecture. List the requirements and pass criteria. 4. Build a working version of comparison screen, bid set and review 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 AI-based decision support system for public procurement (2023, peer-reviewed): https://doi.org/10.1016/j.is.2023.102284 Presents an IS artifact integrating tender text, semantic search and decision support. Enhancing transparency in public procurement: A data-driven analytics approach (2024, peer-reviewed): https://doi.org/10.1016/j.is.2024.102430 Evaluates a public-procurement information-system artifact for transparent analysis. 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. Wang & Strong (1996) — Beyond Accuracy: https://www.tandfonline.com/doi/abs/10.1080/07421222.1996.11518099 Distinguish accuracy, completeness, representation and fitness for the task. 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 Do direct source links help reviewers find unsupported supplier claims and contradictions? EXAMPLE TOOLS HTML/CSS/JavaScript, JSON, spreadsheet Equivalent tools are fine. FIRST THREE ACTIONS 1. Write one tender with 10 requirements and one clean bid. 2. Create clean and faulty bids with varied fault counts; independently review the hidden answer key. 3. Prepare non-overlapping matched bid sets and pilot a single review task before recruitment. LITERATURE SEARCH procurement decision support evidence traceability verification DATA 3 fictional IT tenders × 4 supplier bids (planned) Each tender has 10 requirements. Vary 0–4 unsupported claims and 0–2 contradictions per bid, including clean bids. Keep a hidden, independently reviewed answer key. HOW TO TEST IT 8 IS students review 6 non-overlapping bids, 3 per condition, with identical claims and accessible source packs. Balance order and bid difficulty; hide fault counts. Report per-person misses, false alarms, time, confidence and evidence-backed reasons. FINAL RESULT Comparison screen, bid set and review results. ACCESS OR PEOPLE Recruit 8 students and an independent answer-key reviewer. TEMPLATES https://thesis.uya.no/starters/compare-the-evidence/technical/data-plan.csv https://thesis.uya.no/starters/compare-the-evidence/technical/evaluation.csv https://thesis.uya.no/starters/compare-the-evidence/technical/literature-matrix.csv Use participant codes instead of names or email addresses.