Prioritising IT service outages
Show which municipal services would be affected by an IT incident.
Technical
Bachelor’s · applied project
Final result
A service-impact dashboard with correct graph calculations.
Material to create
12 services, 20 systems, 30 outage narratives
Create required-dependency links, service criticality, outage duration and workarounds. Include shared identity/network/storage outages; exclude failover modelling.
What to do
- Build an IT-service dependency viewer with a fixed outage-priority rubric.
How it is tested
Use the fictional service graph; test reachability and impact counts, then observe prioritisation tasks. Plan 4 participant sessions.
Before you start
Example tools · Python, NetworkX, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Recruit both roles and an independent key reviewer; comparable public-service organisations can participate.
Research method · Build and test · 6 steps
- Read the starting sources and choose one established implementation method.
- Write the requirements, data fields, system diagram and test cases.
- Prepare 12 services, 20 systems, 30 outage narratives. Make the answer key and pass criteria before testing.
- Build a working version of a service-impact dashboard with correct graph calculations.
- Run function, integration and failure-case tests. Record each result.
- Run the practical evaluation and list the changes the system still needs.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Dependency viewer, incident set and ranking comparison.
Material to create
12 services, 20 systems, 30 outage narratives
Create required-dependency links, service criticality, outage duration and workarounds. Include shared identity/network/storage outages; exclude failover modelling.
What to do
- Build a typed NetworkX graph with public-service and technical-component nodes, consumer→dependency edges, schema checks and cycle rejection.
- Compute reverse-reachability impacts and a fixed service-aware lexicographic rank; render the identical backend as graph and normalized table.
- Verify graph/table parity and affected sets against hand traces; report set precision/recall, exact lookup, omissions, time and Kendall tau-b.
How it is tested
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.
Before you start
Example tools · Python, NetworkX, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Recruit both roles and an independent key reviewer; comparable public-service organisations can participate.
Start with these three actions
- Draw the dependency graph and write 3 incidents with manually traced affected services.
- Define the priority rubric and technical-severity scores independently of the ranking algorithm.
- Validate graph traversal against the 3 answer keys before creating remaining incidents.
Files, questions and sources
Pilot question: How does service-impact information change municipal incident priorities and the reasons given?
Literature search: municipal cyber risk service impact decision support
Empty CSV templates: data-plan.csv · evaluation.csv · literature-matrix.csv
Download starter instructionsResearch method · Design, build and test (DSR) · 7 steps
- Read the newest papers and list the closest existing systems.
- Write down the versions, fields, data split, case assignment, random seeds and correct answers for 12 services, 20 systems, 30 outage narratives.
- Draw the user workflow, data model and system architecture. List the requirements and pass criteria.
- Build a working version of dependency viewer, incident set and ranking comparison.
- Test every function, connection and failure case. Save the failed tests as well as the passed tests.
- Compare the system with the named alternative. Then run the user task or decision task in the assignment.
- Report the measured result, the failed cases and the design lessons another team can reuse.
Research question and sources
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.
Current project literature
- A survey on intelligent management of alerts and incidents in IT services (2024) peer-reviewed
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
Provides a recent service-dependency approach for cascading disruption analysis.
IS theory starting points
- Vessey & Galletta (1991) — Cognitive Fit — Test whether a representation helps one kind of task more than another.
- Wang & Strong (1996) — Beyond Accuracy — 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.
Search terms: municipal cyber risk service impact decision support
Non-technical
Bachelor’s · applied project
Final result
A practical prioritisation rubric with unresolved decisions.
Material to create
10 incident cards
Give both groups the same fictional incidents and service descriptions.
What to do
- Document how staff currently decide which outage to handle first.
How it is tested
Discuss fictional outages with IT and service staff; collect criteria and disagreement points. Plan 4 participant sessions.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit both municipal roles.
Research method · Study and improve · 6 steps
- Read the starting sources and write the exact information problem.
- Prepare 10 incident cards and a separate answer sheet or coding sheet.
- Run one pilot and fix unclear questions.
- Collect the named evidence with consent.
- Group the findings with the stated categories and check the answer sheet.
- Produce a practical prioritisation rubric with unresolved decisions. List the three most useful changes.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Disagreement matrix and a shared prioritisation template.
Material to create
10 incident cards + 8 interviews
Recruit 4 municipal IT staff and 4 service managers. Give both groups the same fictional incidents and service descriptions.
What to do
- Create paper incident summaries with technical severity and service consequences.
- Ask IT staff and service managers to rank incidents independently.
How it is tested
Compare group rankings using rank correlation; code explanations for disagreements about service importance and response responsibility.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit both municipal roles.
Start with these three actions
- Prepare a pilot with 2 examples from: 10 incident cards + 8 interviews. Write the task questions and a reference answer sheet.
- Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact.
- Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample.
Files, questions and sources
Pilot question: Where do IT staff and service managers disagree about incident priority, and why?
Literature search: municipal cyber risk service impact decision support qualitative scenario study
Interview prompts
- Which incident should be handled first?
- Which affected service changes your ranking?
- Who should resolve disagreement about these priorities?
Empty CSV templates: study-plan.csv · coding-sheet.csv · literature-matrix.csv
Download starter instructionsResearch method · Study, compare and explain · 7 steps
- Read the newest papers and write one exact research question.
- State which people, cases or documents you will study and what you will compare.
- Write the selection rules, questions and analysis steps for 10 incident cards + 8 interviews.
- Run one pilot. Fix unclear questions or categories, then keep the guide unchanged.
- Collect the named interviews, cases or documents with consent.
- Analyse them with the stated comparison or coding method. Keep disagreements and missing data.
- Report the answer, the evidence and the practical output named in the assignment.
Research question and sources
Research question: Explain disagreement between IT and service owners on outage priority. Compare their interpretations of impact and responsibility using the same incidents; distinguish missing facts from different organisational objectives.
Research result: A role-based explanation of prioritisation conflicts and decision ownership.
Current project literature
- A survey on intelligent management of alerts and incidents in IT services (2024) peer-reviewed
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
Provides a recent service-dependency approach for cascading disruption analysis.
IS theory starting points
- Orlikowski & Gash (1994) — Technological Frames — Compare how roles interpret the purpose, operation and use of the same system.
- Wang & Strong (1996) — Beyond Accuracy — 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.
Search terms: municipal cyber risk service impact decision support qualitative scenario study
Your degree, track and shortlist are saved in this browser.