University of Oulu Software Engineering and Information Systems Master's Thesis Guide: 813613S, 30 ECTS, Mandatory Seminar, II00BC92 Maturity Test and Laturi

Quick answer: what standalone SEIS students need to know

For the current 2026-2027 University of Oulu standalone Master’s programme in Software Engineering and Information Systems, the exact thesis is 813613S Master’s Thesis, course object 9470, worth 30 ECTS and graded 1-5/FAIL. The current realization is 813613S-3003. The same mandatory Common Studies block also contains 813627S Master’s Thesis Seminar, 2 ECTS, and the exact maturity course is II00BC92 Maturity test for Master’s Degree, Software Engineering and Information Systems, 0 ECTS, with current realization II00BC92-3001. This is not the Business Analytics SEIS route, where the thesis code and seminar placement are different.

Two operational details are especially important. First, the exact 813613S course says ordinary Peppi enrollment is not possible; thesis work starts by agreeing supervision with a qualified supervisor. Second, the current course says the main supervisor and a second independent reviewer evaluate the thesis according to programme-specific criteria. These are current 2026-2027 rules and objects, so students working under the 2027-2030 curriculum must recheck the live official sources.

1. Confirm that you are in the standalone SEIS programme

The standalone programme is programme object 51470, code IMP2026SEISTOL. It is a two-year international Master of Science programme with an official student-facing scope of 120 ECTS. The public programme page describes its focus as software-defined products and human-centred information systems.

Do not identify the programme only from the words “Software Engineering and Information Systems.” The Business Analytics programme also has an SEIS degree path, but it uses a different programme object and a different thesis course. Before following any thesis instruction, confirm that your PSP belongs to standalone programme 51470.

2. Understand the Peppi structure without misreading the credit total

The current Peppi accomplishment plan shows a root minimum and maximum of 100-140 ECTS because it represents orientation, specialisation and optional-study choices structurally. That accounting must not be read as changing the official Master’s degree from 120 ECTS.

For student planning, use the 120 ECTS programme scope published by the University and use Peppi to understand how the required and elective blocks combine. This distinction prevents a common error where internal accomplishment-plan ranges are treated as the advertised degree size.

3. The programme has two orientations

The 2026-2027 programme structure has two main orientations: Software Engineering and Information Systems. The programme description says the selection is normally made when the Master’s studies begin and confirmed through the personal study plan, although students may initially explore both before making the final decision.

Software Engineering emphasises a systematic and quantifiable approach to producing reliable and efficient software. Information Systems emphasises the use of information technology in organisations, everyday contexts and work practices. Both routes still share the same exact thesis object 813613S.

4. The mandatory Common Studies block matters

Programme 51470 contains a 60 ECTS Common Studies block with ALL_OF optionality, meaning its listed components are required under the current structure. This block includes Research Methods, the 30 ECTS thesis, the 2 ECTS thesis seminar, a 10 ECTS Research and Development Project, a 3 ECTS Project Seminar, a 0 ECTS maturity test, and the current preparatory/Finnish components.

This structure explains why standalone SEIS differs from Business Analytics SEIS. The same 813627S seminar can have a different status depending on which programme object you are actually in.

5. The exact thesis is 813613S and it is 30 ECTS

The exact current standalone SEIS thesis is 813613S Master’s Thesis, course object 9470, worth 30 ECTS. It is classified as Advanced Studies in Information Processing Science and uses the grading scale 1-5/FAIL. The course language may be English or Finnish according to the student’s decision.

The course learning outcomes require a focused problem in Software Engineering or Information Systems, use of a scientific method, synthesis of research results, evaluation of validity, and scientific reporting according to programme guidelines. This means a thesis is more than a working software artefact or organisational report.

6. The current thesis realization is 813613S-3003

For the present 2026-2027 cycle, the current realization is 813613S-3003. The course object and realization should both be checked when a student is working with registration, Laturi metadata or the study plan, because realization codes change more frequently than the underlying course identity.

Do not copy an implementation code from an earlier thesis, screenshot or another programme. The course code identifies the study unit, while the realization identifies the current delivery period.

7. Ordinary Peppi enrollment is not the thesis-start route

The exact 813613S course states that enrollment to the course in Peppi is not possible. The student starts the work by agreeing supervision with a qualified supervisor. This is a programme-specific operational rule and should not be replaced by generic advice to “register for the thesis in Peppi.”

Peppi still matters for the degree structure and later records, but the actual thesis-start step is supervision agreement followed by the programme and Laturi process. If the interface or rule changes in a later curriculum, use the live course page as the controlling source.

8. Research Methods is a real prerequisite, not only a recommendation

The exact thesis course lists Research Methods as the required prerequisite. Current 813621S Research Methods covers scientific principles, research ethics, methodological quality, qualitative research, quantitative research and design science research.

Treat this course as part of thesis preparation. If your research question is still vague, use the methods framework to decide what evidence is actually needed before data collection or artefact development begins.

9. Start the thesis at the right time

Current SEIS guidance says the typical time to start the Master’s thesis is late spring of the first Master’s year or early autumn of the second year. The degree programme organises thesis information events in spring and autumn and announces them through student channels.

The student remains responsible for initiating the process. Do not wait until every course is finished before looking for a topic, especially if the thesis requires company access, software repositories, participants, interviews, usability testing or development infrastructure.

10. The thesis topic must belong to the scientific field

The current programme guidance says the thesis must address a problem in Software Engineering or Information Systems. A topic may come from the student, a supervisor or a company, but the supervisor helps align it with the scientific field.

A company request such as “build a dashboard” or “improve our workflow” is therefore only a starting point. The thesis needs a researchable problem, defensible method and evidence that can support the final conclusions.

11. Find a qualified supervisor before formalising the project

The exact thesis course tells students to look for a supervisor among researchers and teachers in the SEIS research area who meet the programme’s supervision criteria. The public thesis page also maintains a programme-specific list of eligible staff.

Choose based on topic fit, not only availability. A supervisor familiar with your method and domain can help narrow the scope, identify realistic data access and prevent an attractive but unassessable project from moving too far.

12. Evaluation uses the main supervisor and a second independent reviewer

The exact 813613S assessment criteria state that the main supervisor and a second independent reviewer evaluate the thesis according to programme criteria. This reviewer wording is stronger and more precise than importing a role description from another programme.

Use the programme-specific evaluation criteria from the start. Discuss the target quality level with the supervisor before the manuscript is nearly finished, because evaluation criteria are most useful when they guide design, analysis and reporting choices early.

13. Do not import the CSE score mapping

Standalone SEIS uses a 1-5/FAIL thesis scale and its own programme-specific criteria. The numeric 10-42 score mapping used in the CSE route is not established for this programme and must not be copied into the guide or a student’s planning documents.

When comparing old theses or advice from friends, always separate University-wide rules from programme-specific evaluation systems. Similar administrative systems do not make grading rubrics interchangeable.

14. The 813627S thesis seminar is mandatory here

A major boundary is 813627S Master’s Thesis Seminar, 2 ECTS. In standalone programme 51470 it sits inside the mandatory 60 ECTS Common Studies block. Therefore it is a required component under the current structure.

This is different from Business Analytics SEIS programme 52632, where the same 813627S course is placed under optional studies. The seminar’s status follows the programme structure, not the course name by itself.

15. The seminar follows the thesis from question to final presentation

The seminar is organised around three phases: formulating the topic and questions, reviewing literature and selecting methods; collecting and analysing data; and discussing results, writing conclusions and presenting the final thesis. Students also act as peer reviewers or audience members before presenting their own work.

The current course uses Moodle, peer review, written feedback, rebuttals and seminar or video presentations. Total workload is 54 hours, and students may begin the course during the academic year according to the current description.

16. Research and Development Project is a separate mandatory 10 ECTS study

The Common Studies block also includes 817612S Research and Development Project, 10 ECTS. It develops professional ICT project work, project planning, customer communication, progress reporting and evaluation of software or project-process choices.

This project may strengthen skills relevant to the thesis, but it is not part of the 30 ECTS thesis object. Keep its credits and assessment separate when explaining degree requirements.

17. Project Seminar is another separate mandatory 3 ECTS study

Programme 51470 also includes 817609S Project Seminar, 3 ECTS as mandatory Common Studies. The course links practical project experience to research literature, asks students to analyse and report experience-based data, and evaluates written and oral dissemination.

The course requires the Research and Development Project to be taken at the same time. Again, this is a degree component, not an extra three credits attached to the thesis course.

18. Keep thesis credits separate from surrounding degree requirements

The thesis itself remains 30 ECTS. The mandatory 2 ECTS thesis seminar, 10 ECTS R&D Project and 3 ECTS Project Seminar are separate studies in the degree structure. Combining them into a single “45 ECTS thesis” would be inaccurate.

For planning, it is useful to see them as an ecosystem around research and professional project work. For reporting official thesis size, however, use the exact 813613S value of 30 ECTS.

19. The exact maturity course is II00BC92, 0 ECTS

The current maturity course is II00BC92 Maturity test for Master’s Degree, Software Engineering and Information Systems, worth 0 ECTS and assessed PASS/FAIL. The current realization is II00BC92-3001.

Do not import the CSE maturity code 521009S. The standalone SEIS programme and Business Analytics SEIS share II00BC92, but the controlling source is still the exact current course object in your own programme structure.

20. The maturity essay is about 500 words

The exact course describes a self-paced maturity essay of approximately 500 words. The title is determined by the Master’s thesis supervisor, who also evaluates the text. The essay should be analytical and coherent and should present and analyse the research material, methods and results.

The maturity test is completed when the thesis is finalised, and the stated qualification is that the thesis is accepted or almost finished. Plan it near the end of the thesis rather than treating it as an unrelated early course.

21. Some students may use the thesis abstract instead

If the student does not need to demonstrate Finnish or Swedish language competence in the maturity test, the exact course allows the required Master’s thesis abstract to demonstrate the competence instead of a separate essay. The abstract still needs to demonstrate knowledge of the field.

Language obligations depend on the student’s educational and statutory background. The exact course lists Finnish or English, but that does not mean every student may simply choose either language without checking the applicable rule.

22. Use Laturi as the thesis workflow system

The University uses Laturi for thesis starting, supervision, monitoring, evaluation, plagiarism checking and publication workflow. For standalone SEIS, the thesis begins with supervision agreement rather than ordinary Peppi enrollment, then proceeds through the programme’s Laturi process.

Do not treat Laturi as only a final upload box. Set up the thesis process early enough that supervisor, metadata, research plan or other required approvals can be handled before the manuscript is complete.

23. Follow the current SEIS template and structure

Current SEIS guidance says the thesis can be accepted only when its style follows the given template and its structure follows programme guidelines. Students should also read the evaluation criteria at the beginning and discuss quality targets with the supervisor.

Use the current official template instead of copying an old thesis. Old theses can be useful examples of topic and argument, but they are not a reliable source for current course codes, formatting rules or administrative steps.

24. Public thesis rules affect company projects

Current programme guidance warns that theses are publicly available, while Laturi guidance states that the final thesis itself must not contain secret trade or professional information. Confidential background material therefore needs an agreed handling arrangement before final submission.

For company work, define early what can appear in the public manuscript and what must stay outside it. A thesis still needs enough public evidence and reasoning to be academically assessable after confidential details are removed.

25. Graduation is a separate administrative stage

Thesis completion is not identical to graduation. After required studies, thesis-related components and records are complete, degree application proceeds through Peppi according to the current University graduation process.

Use the live graduation timetable when planning a target date. Committee schedules, recording delays and degree-application steps can affect the practical graduation date even when the manuscript itself is finished.

26. Choose the method from the research problem

SEIS explicitly teaches qualitative, quantitative and design science approaches. The right method depends on the research problem, the kind of evidence available and the claim the thesis needs to support. There is no single “SEIS method.”

Start by writing the research question in a form that can be answered with evidence. Then decide whether you need interviews, observations, surveys, repository data, experiments, usability tests, artefact evaluation, statistical analysis, or a justified combination.

27. Qualitative studies need an explicit analysis process

A qualitative thesis should explain why particular cases or participants were selected, how data were collected, how coding or thematic analysis was conducted and how interpretations were checked. Simply reporting interview quotations is not an analysis method.

Keep a traceable path from raw material to codes, categories, themes or theoretical interpretation. State the limitations of participant selection and context so that readers understand where the findings can and cannot be transferred.

28. Quantitative studies need measurement and validity planning

A quantitative thesis should define variables, sampling, measurement procedures and the statistical analysis before interpreting results. Reliability, validity and generalisability claims must match the actual data-generating process.

Avoid selecting tests only after looking at the outcome. If multiple models or comparisons are explored, report that process transparently. A statistically significant result is not automatically practically important, causal or generalisable.

29. Design science needs construction and evaluation

A design-science thesis may produce software, a framework, method, prototype or other artefact, but construction alone is not enough. The thesis should explain the problem context, design objectives, design decisions and the evaluation evidence used to judge the artefact.

Choose evaluation methods that match the intended contribution. Depending on the work, this may include controlled tests, expert review, user evaluation, benchmark comparison, field deployment or another justified method.

30. Empirical software engineering needs reproducible evidence

Software Engineering Research emphasises empirical research design and critical analysis of scientific work. A thesis studying software development should therefore document its unit of analysis, data source, extraction method, variables and evaluation procedure.

If the study concerns commits, pull requests, defects, CI logs or developer behaviour, preserve enough provenance that another researcher could understand exactly which repository state and records were analysed.

31. Mining software repositories requires data provenance

Current Software Development, Maintenance and Operations coursework includes software metrics, mining software repositories and data-driven software engineering. A repository-mining thesis should record repository selection, extraction date, branches, filters, bot handling, preprocessing and metric definitions.

Repository data may look objective, but it is still shaped by project practices and tooling. A “commit” or “defect” can mean different things across projects, so define operational measures carefully before comparing teams or systems.

32. Software quality and security need measurable criteria

Advanced Software Quality and Security covers test automation, code review, static analysis, TDD, exploratory testing, search-based testing and security testing. A thesis using these techniques should define what counts as a defect, vulnerability, failure or improvement.

Report software version, environment, baseline and test configuration when these can influence results. A tool finding is not automatically a confirmed security vulnerability, and a reduction in warnings is not automatically a quality improvement.

33. UX and usability theses need participant and task design

UX and Usability Evaluation teaches participant selection, test scenarios, tasks, methods, metrics, lab or field execution, analysis and reporting. A usability thesis should therefore make the tested population, product version, tasks and success measures explicit.

Do not generalise from a small convenience sample to all users without justification. Distinguish usability observations, user preferences and product-value claims, because they answer different questions.

34. Digitalisation topics need organisational evidence

Digitalisation and Innovation provides concepts for digital transformation strategy, organisational change and innovation. A thesis on digital transformation should therefore avoid treating technology adoption as an outcome by itself.

Define whose process or decision is expected to change, what evidence would show that change, and what alternative explanations exist. Strategy recommendations should be grounded in the studied organisation, data and literature rather than presented as universal rules.

35. Information Systems Strategy can shape management-facing questions

Information Systems Strategy and Leadership covers strategic IS planning, alignment with business objectives and analysis of uncertain organisational environments. This is useful for theses about platform decisions, digital capability, governance, sourcing or information-system portfolios.

A management recommendation should show how evidence connects to the recommendation. Separate descriptive findings from causal or predictive claims, and state whose objectives are being optimised.

36. Societal and behavioural effects need careful interpretation

Current IS studies also address societal impacts, communication, influence, behaviour change and digital interventions. A thesis in this area may use interviews, surveys, experiments, trace data or design evaluation, but the interpretation must match the design.

Do not infer psychological or social effects from platform usage alone unless the design supports that inference. If the study involves people, also consider personal-data and ethics requirements before collecting data.

37. Data-value claims need a clear mechanism

Creating Domain Value with Data links analytics architecture and technology to organisational value creation and analytics maturity. If a thesis claims that data or analytics creates value, it should explain the mechanism connecting the technical output to a decision, process or measurable outcome.

A dashboard, model or data pipeline can be a useful artefact, but the existence of the artefact does not by itself prove business value. Evaluate the relevant use, decision or performance effect at the level your study can support.

38. Human factors in software teams require a clear unit of analysis

Professional Software Engineering Processes and Human Factors examines development processes, team behaviour and process improvement. A thesis on teams, agile practices or developer experience should define whether the unit of analysis is the individual, team, project or organisation.

Self-report data, process metrics and delivery outcomes measure different things. Avoid combining them into one broad conclusion without a clear conceptual model and appropriate evidence.

39. Build a research data-management plan early

University responsible-research guidance expects data management to be planned from the research-planning stage and updated during the project. The plan should cover collection, storage, access, sharing, preservation and reproducibility.

SEIS data can include interview recordings, transcripts, survey exports, repository snapshots, scripts, model files, logs, screenshots and company documents. Agree ownership, access rights and long-term handling before the project becomes dependent on data that cannot later be shared or retained.

40. Personal-data planning must happen before processing

If the thesis processes personal data, the University expects the processing lifecycle to be recorded before processing begins. Data protection and information security must be addressed, and a privacy notice, risk assessment or DPIA may be required depending on the case.

Minimise the personal data collected and anonymise or pseudonymise where appropriate. Remember that pseudonymised data are still personal data when re-identification remains possible.

41. Ethics review depends on the actual study design

Ethics committee review is not automatic for every SEIS thesis. It becomes relevant when the actual research design meets the University’s applicable human-sciences criteria or another governing requirement.

Discuss ethics before recruitment or data collection. If review is required, a Master’s student must involve the supervisor according to current guidance. Approval cannot be treated as something to obtain after the study has already been conducted.

42. Research integrity includes code, datasets and AI-assisted work

Research integrity applies to references, code, datasets, figures, repository data, participant material and AI-assisted work. If AI tools are used for coding, language editing, brainstorming or analysis, follow current University and supervisor instructions and document the use where required.

The student remains responsible for every claim. Verify generated references, code behaviour, statistics and technical descriptions. AI-generated fluency does not make unverified content academically acceptable.

43. A realistic thesis timeline starts before writing

A practical sequence is to identify the scientific problem, secure supervision, confirm that Research Methods preparation is complete, and agree the thesis start. Then set up the Laturi process, refine research questions, plan data management and ethics/privacy requirements, and only then collect data or build the artefact at full scale.

Reserve time for analysis, seminar milestones, supervisor feedback, revision, maturity-test completion and final administrative steps. A 30 ECTS thesis should not be treated as a few weeks of end-stage writing.

44. Common mistakes are usually boundary mistakes

Common errors include using II00BD01 because a Business Analytics SEIS student used it, treating 813627S as optional because it is optional in another programme, adding R&D Project credits to the thesis itself, or trying to start 813613S through ordinary Peppi enrollment.

Methodological mistakes are equally serious: building software without evaluation, collecting interviews without an analysis plan, mining repositories without provenance, or making organisational value claims without evidence of the decision or process effect.

45. What not to import from other Oulu programmes

Do not import the Business Analytics SEIS thesis II00BD01, the standalone CSE thesis 521993S, the CSE maturity code 521009S, or the CSE 10-42 score mapping. Do not assume that seminar status is the same across programmes just because the course code is identical.

The controlling standalone-SEIS objects are 51470 / IMP2026SEISTOL, 813613S, 813627S, and II00BC92. Programme object first, then exact course object, then current realization is the safest verification order.

46. Recheck everything for the 2027-2030 curriculum

This guide is bounded to the current 2026-2027 programme and sources checked during preparation. The University is moving to the 2027-2030 curriculum period from academic year 2027-2028, with transition arrangements for continuing students.

Students starting, registering or submitting under the new period should perform a fresh official recheck. Course codes, programme objects, realization codes, responsible persons, seminar placement or administrative workflows can change even when the programme name stays similar.

47. Final practical workflow and checklist

Confirm 51470 / IMP2026SEISTOL and your orientation. Complete the required Research Methods preparation, find a qualified supervisor and agree the thesis start rather than trying ordinary Peppi enrollment. Use 813613S / 9470 / 30 ECTS and check that 813613S-3003 is still the current realization for your period.

Use Laturi for the formal workflow, follow the current SEIS template and programme evaluation criteria, complete the mandatory 813627S / 2 ECTS thesis seminar, keep the separate 817612S / 10 ECTS R&D Project and 817609S / 3 ECTS Project Seminar distinct from thesis credits, and complete II00BC92 / II00BC92-3001 / 0 ECTS maturity requirements. Before final submission, verify data management, privacy, ethics, public-thesis/confidentiality boundaries, reviewer setup and live graduation timing. If your studies cross into the next curriculum, perform the 2027-2030 recheck first.