Choose one track. Master’s proposals target Spring 2027. Final scope and programme approval are agreed with the supervisor; bachelor scopes are suggested adaptations.
TRACK 01 · IMPLEMENTATION INCLUDED
Technical track
Develop a working solution and test whether it addresses the problem.
Possible research question
Can source-linked process modelling improve stakeholder agreement and expose requirements errors in interview-derived models?
Suggested tasks
Read research on interview-based process modelling and compare existing solutions.
Identify one problem faced by stakeholders and requirements analysts.
Write a research question and define what the solution should do.
Prepare scripted interviews that describe one business process, including some conflicting accounts.
Build a tool that turns the interviews into a process diagram, links steps to their sources and flags unclear or conflicting statements.
Compare it with a generated diagram without source links. Test whether users spot errors and resolve disagreements.
Explain what worked, what did not, and how the results compare with earlier research.
Evaluation, degree scope and deliverables
Study and evaluation
Compare the implemented solution with a generated process model without source links or ambiguity handling. Combine reproducible technical tests with an appropriate empirical evaluation.
Requirements errors and unsupported model elements
Stakeholder agreement or recorded disagreement
Correction and verification effort
Degree scope
Bachelor’s
Build a process editor with source-linked steps from scripted interviews and a few structural checks. Evaluate model correction tasks.
Master’s
Study how traceability and disagreement handling affect shared understanding, compared with generation alone.
Background
Programming
Requirements engineering
Interest in process modelling
Possible deliverables
A focused literature review, justified problem and research question
A working prototype with source code and setup instructions
A reproducible comparison and an appropriate study of use
A report explaining design lessons, results and limitations
TRACK 02 · NO IMPLEMENTATION REQUIRED
Non-technical track
Study existing systems, information or work practices. You do not need to develop software.
Possible research question
How do source links and visible disagreement affect stakeholders’ interpretation of process models?
Suggested tasks
Read earlier studies of interview-based process modelling.
Choose one problem and write a research question the study can answer.
Use scripted interviews and existing or manually prepared process diagrams.
Ask stakeholders to trace model elements to evidence and identify ambiguous or conflicting accounts.
Analyse how disagreements are resolved or preserved during requirements discussions.
Analyse the interviews, observations or documents using a clearly described method. Look for disagreements as well as common patterns.
Explain the findings, compare them with earlier research and suggest practical improvements.
Evaluation, degree scope and deliverables
Study and evaluation
Use a bounded empirical study of interview-based process modelling. Justify case selection, recruitment and the analysis method. Distinguish observed behaviour from participants’ perceptions; use triangulation or a comparison where it serves the research question.
Unsupported assumptions and requirements misunderstandings
Stakeholder agreement, dissent and evidence use
Evidence for the findings, conflicting cases and limits of the study
Degree scope
Bachelor’s
Study one case or a small set of existing materials. Agree the interviews, documents or scenario tasks with the supervisor. Describe the method, analyse the findings and give practical recommendations.
Master’s
Use a clear research question and relevant IS theory. Justify the cases, participants and analysis method. Explain what the findings add to earlier research and where they may apply. No software development is required.
Background
Literature review and academic writing
Qualitative or quantitative research methods
Interest in interview-based process modelling; no programming prerequisite
Possible deliverables
A literature review and research question
A study plan and approved research material
An analysis supported by interviews, observations, documents or scenario results
A thesis with findings, recommendations and limitations
Scope and access
One process family and a modest set of interviews. Do not erase disagreement by forcing a single consensus model. These implementation-related limits apply when developing or testing a technical solution. For a non-technical study, agree access to participants or existing materials early, use approved or fictional cases where appropriate, and distinguish perceptions from observed outcomes.
Agree access to data, participants or existing materials and any required ethics or privacy review before committing. A non-technical track needs a systematic study, not a working prototype.
Full academic proposal
Working topic
From Stakeholder Interviews to Checkable Process Models
Brief outline
This proposal examines interview-based process modelling in the work and information needs of stakeholders and requirements analysts. The technical track combines a literature review and justified gap with requirements, design, implementation and evaluation of a bounded solution. The non-technical track investigates practices, experiences or organisational conditions through a systematic study of existing systems, documents or scenarios, without requiring implementation. Choose one track and agree the final research question, degree scope and contribution with the supervisor.
Programme fit
Information Systems. These are suggested research approaches, not a statement of confirmed programme policy. Agree the final title, track, degree scope and contribution with the supervisor and programme.
Shared research foundation
Review the literature; identify and justify a gap; formulate research questions; conduct a systematic study; analyse the evidence; explain the contribution relative to prior research and discuss limitations. The technical track additionally includes requirements, design, implementation and evaluation of an artifact.
