Prioritising IT service outages — Technical https://thesis.uya.no/proposals/protect-the-services-people-need/#technical-track BACHELOR Final result: A service-impact dashboard with correct graph calculations. Task: Build an IT-service dependency viewer with a fixed outage-priority rubric. Data: 12 services, 20 systems, 30 outage narratives (planned) Create required-dependency links, service criticality, outage duration and workarounds. Include shared identity/network/storage outages; exclude failover modelling. Requires: Recruit both roles and an independent key reviewer; comparable public-service organisations can participate. Method: Use the fictional service graph; test reachability and impact counts, then observe prioritisation 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 12 services, 20 systems, 30 outage narratives. Make the answer key and pass criteria before testing. 4. Build a working version of a service-impact dashboard with correct graph calculations. 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: Dependency viewer, incident set and ranking comparison. Research question: Test whether service graphs help dependency reasoning but hinder exact priority lookup. Derive task-specific predictions from cognitive-fit research; compare graph/table with identical facts and separate graph correctness from priority judgement. Research result: Evidence about which outage tasks benefit from dependency visualisation and why. 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 12 services, 20 systems, 30 outage narratives. 3. Draw the user workflow, data model and system architecture. List the requirements and pass criteria. 4. Build a working version of dependency viewer, incident set and ranking comparison. 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 A survey on intelligent management of alerts and incidents in IT services (2024, peer-reviewed): https://doi.org/10.1016/j.jnca.2024.103842 Synthesizes current incident data, dependencies, prioritization and intelligent support. Dependent Infrastructure Service Disruption Mapping (DISruptionMap): A method to assess cascading service disruptions in disaster scenarios (2025, peer-reviewed): https://doi.org/10.1038/s41598-025-89469-0 Provides a recent service-dependency approach for cascading disruption analysis. IS THEORY STARTING POINTS Vessey & Galletta (1991) — Cognitive Fit: https://pubsonline.informs.org/doi/10.1287/isre.2.1.63 Test whether a representation helps one kind of task more than another. 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 How does service-impact information change municipal incident priorities and the reasons given? EXAMPLE TOOLS Python, NetworkX, Streamlit Equivalent tools are fine. FIRST THREE ACTIONS 1. Draw the dependency graph and write 3 incidents with manually traced affected services. 2. Define the priority rubric and technical-severity scores independently of the ranking algorithm. 3. Validate graph traversal against the 3 answer keys before creating remaining incidents. LITERATURE SEARCH municipal cyber risk service impact decision support DATA 12 services, 20 systems, 30 outage narratives (planned) Create required-dependency links, service criticality, outage duration and workarounds. Include shared identity/network/storage outages; exclude failover modelling. HOW TO TEST IT 4 IT staff and 4 service owners review 10 non-overlapping incidents. Measure omitted service impacts, time and rank-change reasons. Verify affected-service sets against independent hand-traced answers; technical-severity ranking is a descriptive reference. FINAL RESULT Dependency viewer, incident set and ranking comparison. ACCESS OR PEOPLE Recruit both roles and an independent key reviewer; comparable public-service organisations can participate. TEMPLATES https://thesis.uya.no/starters/protect-the-services-people-need/technical/data-plan.csv https://thesis.uya.no/starters/protect-the-services-people-need/technical/evaluation.csv https://thesis.uya.no/starters/protect-the-services-people-need/technical/literature-matrix.csv Use participant codes instead of names or email addresses.