University of Jyväskylä Information Systems Master's Thesis Guide: TJTS5005, Research Methods, IT Assessment and Vasara

Start with the current Information Systems research package

The current University of Jyväskylä Information Systems programme uses one clear 45 ECTS research module inside INSMP2024: TJTS5010 Research Frameworks in Information Systems Science, 2 ECTS; TJTS5011 Applying Research Methods in Information Systems Science, 3 ECTS; TJTS5002 Information Systems Theories, 5 ECTS; TJTS5033 Master’s Thesis Seminar (IS), 5 ECTS; TJTS5004 Maturity test, 0 ECTS; and TJTS5005 Thesis, 30 ECTS. The module matters because it separates thesis preparation, methods, theory, seminar work, maturity and the final thesis instead of treating them as one course.

1. The current degree is Master of Science (Economics and Business Administration)

The current degree object is INSMP2024, a 120 ECTS English-language Master’s Degree Programme in Information Systems coordinated and administered by the Faculty of Information Technology. The degree title is Master of Science (Economics and Business Administration). The current Study Guide applies to curriculum periods 2024-2025 through 2027-2028. Use the current Study Guide course objects when planning registration, because older Information Systems course codes or thesis instructions can describe a different curriculum regime.

2. TJTINS contains the research module inside advanced studies

TJTINS Advanced Studies in Information Systems is an 80 ECTS advanced-studies module. Its mandatory studies include a 15 ECTS core and the 45 ECTS research module. The programme also contains elective Information Systems studies and communication/language studies, but these should not be folded into the research module automatically. In particular, XENB0007 Master’s Thesis Support, 2 ECTS, is a separate support course under other/communication studies and is not one of the six objects in the compulsory 45 ECTS research chain.

3. Keep all six research-module objects separate

The six current objects have different functions and grading. TJTS5010 is 2 ECTS Pass/Fail, TJTS5011 is 3 ECTS graded 0-5, TJTS5002 is 5 ECTS graded 0-5, TJTS5033 is 5 ECTS Pass/Fail, TJTS5004 is 0 ECTS Pass/Fail, and TJTS5005 is the 30 ECTS thesis graded 0-5. A planning document that lists only the seminar and thesis misses 10 ECTS of research-method and theory preparation. A document that counts the seminar mini-thesis as the final thesis double-counts the work.

4. TJTS5010 turns a topic into a research framework

TJTS5010 Research Frameworks in Information Systems Science, 2 ECTS, Pass/Fail focuses on research planning and the relationship among research questions, theory, data and analysis methods. Its research-plan assignment is assessed for feasibility. The learning objective is practical: the student should be able to produce a feasible plan for the Master’s thesis and critically assess methodological choices. Take this course seriously as a design checkpoint. A promising topic is not yet a thesis until its question, theoretical framing, evidence and analysis can work together.

5. TJTS5011 gives several method routes, not one mandatory route

TJTS5011 Applying Research Methods in Information Systems Science, 3 ECTS, grade 0-5 currently offers method modules in qualitative research, quantitative research, design science and literature review. The qualitative module includes examples such as interviewing and thematic analysis. The quantitative module focuses on numerical data and statistics. Design science concerns developing IT artefacts or practices, while the literature-review module concentrates on theoretical and conceptual work. Students select the module or modules they need, so method choice should follow the planned thesis rather than a presumed programme-wide formula.

6. Method examples are options, not programme-wide thesis mandates

Current Information Systems sources support methodological plurality. Interviewing is not required simply because it appears in the qualitative module. Statistical analysis is not required simply because it appears in the quantitative module. Design science does not require all students to build an artefact, and the literature-review module does not make all theses reviews. The thesis course asks the student to master and critically evaluate the method actually used. Start from the research or development problem, then justify the design that can answer it convincingly.

7. TJTS5002 makes literature and theory part of the research foundation

TJTS5002 Information Systems Theories, 5 ECTS, grade 0-5 states that prior literature and theory are critical building blocks of an Information Systems Master’s thesis. The course introduces contemporary IS research, the role of reference disciplines, literature reviews and theoretical-background sections. It also asks students to analyse and criticize published IS research. This means the literature section should do more than summarize sources one by one. It should identify concepts, compare positions, establish what is already known and create a defensible foundation for the thesis question and interpretation.

8. TJTS5033 is the programme-specific Master’s Thesis Seminar

TJTS5033 Master’s Thesis Seminar (IS), 5 ECTS, Pass/Fail is the current seminar for Information Systems students in the international programme. It supports thesis work through small-group sessions, oral and written reporting and peer feedback. Typical work includes presenting the topic and research proposal, reporting a data-collection plan, producing an approximately 20-25-page seminar report described as a “mini-thesis”, and acting as an opponent for another student. The stated workload is 135 hours, including substantial preparation of the student’s own written and oral work.

9. The seminar mini-thesis is not TJTS5005

The 20-25-page seminar report is a TJTS5033 deliverable, not the separate 30 ECTS final thesis. The seminar is designed to help the project become systematic, defensible and communicable. Passing requires active participation and completion of the required assignments, proposals and seminar report. Use the mini-thesis to test the structure, literature base, research question, planned evidence and analysis. Then continue developing the project under TJTS5005 rather than treating the seminar report as a finished final submission.

10. A thesis topic can come from several places

The current thesis course allows a topic to be developed by the student, negotiated with a supervisor or based on a need in a company or organisation. IT Faculty guidance also recognises topics that arise from the student, a workplace/external party or faculty research. A company connection is therefore possible but not compulsory. Whatever the source, the topic must be agreed with the supervisor. A practical business problem becomes a thesis only when it can be transformed into a research or development problem with a scientific context and assessable evidence.

11. Find the responsible supervisor before the project becomes large

The IT Faculty process begins when a responsible supervisor is appointed and approves the topic. The responsible supervisor must hold a doctoral degree and be employed by the University of Jyväskylä. A thesis may have additional supervisors, including people with specialised or external expertise, but that does not replace the formal responsible-supervisor requirement. Agree the topic, research or development task, evidence, milestones, data responsibilities and feedback rhythm early. This is especially important for externally commissioned projects, where workplace priorities and academic assessment criteria can otherwise drift apart.

12. Use the Information Systems Science thesis template

The Faculty of Information Technology publishes a separate Information Systems Science thesis template. It should not be confused with the AI & HPC template or with templates used by other faculties. Template choice matters because programme-specific reporting conventions are part of the Faculty assessment framework. Start from the current Information Systems template before formatting becomes expensive to change. It also helps with accessibility because the university recommends using available thesis templates and proper heading styles rather than manually imitating document structure.

13. TJTS5005 is the controlling 30 ECTS thesis object

TJTS5005 Thesis, 30 ECTS, grade 0-5 is the current final Information Systems thesis course. It defines the work as an independent scientific thesis and permits independent or pair work. Students must demonstrate scientific thinking, familiarity with the topic, the ability to apply research methods, the ability to formulate research questions and the ability to report research in their discipline. Recommended prerequisites are TJTS5002, TJTS5010 and TJTS5011, which explains why theory, research design and method competence should be established before the final thesis process is far advanced.

14. The thesis can use a research or development design

The IT Faculty assessment matrix explicitly recognises a research problem or development task and an appropriate research or development method. It requires the chosen design to be justified and described. This is important for Information Systems, where some projects study organisations or users while others design or evaluate digital artefacts, practices or processes. The work still needs a scientific foundation, a clear problem, appropriate literature, defensible evidence and critical evaluation. A development output without a scholarly question and evaluation is not enough simply because it is technically useful.

15. Qualitative research is one supported route

A qualitative Information Systems thesis may use interviews, documents, observations, case materials or other appropriate evidence, depending on the question. TJTS5011 specifically uses interviewing and thematic analysis as examples in its qualitative module. Those examples show supported skills, not a fixed recipe. If interviews are appropriate, plan participant selection, interview design, consent, personal-data handling, transcription, coding and analytical logic in advance. The thesis should explain how the evidence supports the claims and what limitations follow from the chosen sample and analytical process.

16. Quantitative research is another supported route

The quantitative TJTS5011 module focuses on numerical data and statistics. A quantitative thesis might analyse survey data, system metrics, organisational records, experiments or another numerical dataset when the question calls for it. The course listing does not prescribe one statistical package, one dataset or one technique. Define variables and measures carefully, justify the analytical method, report data quality and limitations, and avoid treating statistical output as self-explanatory. The assessment matrix expects the chosen method and design to be appropriate to the research task and the interpretation to relate results back to prior knowledge.

17. Design science can support an artefact or practice

TJTS5011 includes design science for developing IT artefacts or practices, and the IT Faculty assessment language also recognises development tasks. In such a thesis, the artefact should be connected to a clearly framed problem and prior research, and the evaluation should show what the development contributes. Define design objectives, requirements, construction process and evaluation criteria before building too much. The academic contribution is not the existence of software alone. It is the defensible relationship among the problem, knowledge base, design choices, evidence, evaluation and conclusions.

18. A literature-review thesis needs a real review method

TJTS5011 includes a literature-review method module, while TJTS5002 explicitly teaches literature reviews and theoretical-background construction. A review-oriented thesis should therefore be designed systematically: define the review question, search sources, inclusion/exclusion logic, extraction process and synthesis method. The final contribution should go beyond a catalogue of papers. It may identify patterns, contradictions, gaps, conceptual structures or a new synthesis that answers the research question. The exact review method should be chosen and justified for the thesis rather than copied from an unrelated discipline.

19. Empirical work is conditional, not automatically required

The current IT Faculty assessment matrix discusses data collection and analysis where empirical work has been undertaken. That wording matters. It supports empirical theses, but it does not turn empirical data collection into a universal condition for all Information Systems theses. Method choice can include empirical, review, design/development or other justified forms supported by the programme’s research-method environment. The common requirement is stronger: the chosen research or development design must be appropriate, clearly reported, ethically conducted and capable of supporting the thesis claims.

20. Pair work is allowed, but individual contribution must remain assessable

TJTS5005 permits work independently or in pairs, and the University Degree Regulations also allow a Master’s thesis to have one author or two authors. In pair or larger-project settings, individual contributions must remain identifiable so they can be assessed appropriately. Agree division of labour, authorship, shared data, writing responsibilities and evidence of each student’s contribution early. Vasara also has a specific pair-submission flow in which the second author confirms the submission and openness/licensing choices.

21. TJTS5005 assessment looks at the whole research argument

The thesis course states that assessment considers the research design, use of literature, application of research methods, presentation and interpretation of results, structure and language. These dimensions should guide drafting from the start. A strong literature review cannot rescue an unjustified method, and a technically correct method cannot rescue a weak research problem or poorly interpreted results. Keep a live checklist that connects each chapter to the assessment dimensions: problem, prior research, method/design, evidence, analysis, interpretation, limitations and coherent scientific reporting.

22. IT Faculty grading is cumulative

The IT Faculty uses a cumulative assessment framework. Every evaluated criterion must reach at least the satisfactory grade-1 level for the thesis to pass. Higher overall grades require the characteristics of lower levels plus stronger performance, and grades 2 and 4 function as intermediate levels. The framework covers the research problem, familiarity with the topic, execution, reporting and the overall process. This makes thesis quality multidimensional: serious weakness in one core area cannot simply disappear because another area is excellent.

23. The final grade is not an arithmetic average

The Faculty explicitly states that the overall thesis grade is not an arithmetic mean of individual criterion scores. At least half of the evaluated criteria must reach the level proposed for the overall grade, while all criteria still need the minimum passing level. The Vice Dean determines the final grade based on examiner assessment under the IT Faculty process. Use the matrix to diagnose weaknesses before submission rather than trying to calculate a numeric average from isolated strengths.

24. The assessment matrix keeps empirical claims conditional

The current one-page IT Faculty matrix uses the headings research problem, familiarity with the topic, execution, reporting and process. It requires an appropriate method/design and recognises both research and development methods. It discusses data collection and analysis where empirical work has been undertaken and includes research-ethics expectations in applicable data work. This confirms a key boundary for Information Systems: assessment is rigorous, but the matrix does not prescribe one universal empirical architecture, programming language, software package or technical platform.

25. TJTS5004 is the exact maturity-test course object

TJTS5004 Maturity test, 0 ECTS, Pass/Fail is the current Information Systems maturity object. It lists English, Finnish and Swedish as course languages and sits inside the 45 ECTS research module. The course description says the maturity work is conducted after submitting the Master’s thesis. Keep the code separate from maturity objects used by other programmes. Registration matters because the general Vasara instructions require students to be registered for both the thesis and maturity-test implementation in Sisu before final submission.

26. The current maturity metadata contains a real format inconsistency

The current TJTS5004 descriptive text labels the product “Press Release” and explains that it should present the research essentials, main results and wider significance in a concise news style. Yet the currently published 2026-2027 implementation is labelled Essay and is listed in Finnish. The university-wide maturity page separately gives general essay guidance, including an approximately 700-word maturity essay. These current sources do not line up neatly enough to justify pretending that one descriptor tells the full operational story for every Information Systems student.

27. Handle the maturity requirement through current Sisu and supervisor instructions

The safest current workflow is procedural: enrol in TJTS5004, confirm the active implementation in Sisu, and follow the current Faculty/supervisor instructions that apply to your language and educational background. The Information Systems selector on the university return page says to follow the general instructions above, rather than publishing a separate IS-only return process. Do not borrow an abstract exception or maturity code from another programme. If the TJTS5004 Press Release description and active Essay implementation remain different, ask which form your implementation requires before completing it.

28. Complete Turnitin and Sisu prerequisites before Vasara

The university-wide return instructions require an originality check in Turnitin according to supervisor instructions before Vasara submission. They also require registration for both the thesis and maturity implementation in Sisu. Treat Turnitin as part of final quality control, not as a substitute for correct source use. Resolve citation, paraphrasing, permissions and confidential-material issues before the final submission. If a supervisor requests an earlier Turnitin checkpoint, use it to improve the manuscript while edits are still allowed.

29. Vasara submission means the thesis is final

All JYU faculties use Vasara for electronic Master’s thesis submission, evaluation and archiving. The general instructions state that the version submitted for evaluation must be final and cannot be changed after submission. Discuss readiness with the supervisor first. The final file should be an accessible PDF/A. The overall return/evaluation process can take up to around two months, so graduation planning should include assessment time rather than using the upload date as the expected completion date.

30. Two examiners, response rights and one interruption protect the process

University Degree Regulations require two examiners for a Master’s thesis, with at least one examiner holding a doctoral degree. The author has an opportunity to respond before the final grade is decided. The regulations also allow the author to interrupt the assessment process once before final grading and later resubmit after sufficient partial rewriting, subject to the formal conditions. These rights are different from revising an already approved thesis: once the thesis has been graded and approved, it cannot simply be rewritten to raise the grade.

31. The approved thesis becomes a public academic document

Master’s theses are public documents and are archived in JYX. Vasara sends the approved thesis to JYX automatically, so a separate modern JYX submission is not required. Confidential background material must not remain inside the public thesis; keep it outside the evaluated/public document as instructed. JYU generally publishes theses openly, although restricted-access arrangements can apply while bibliographic information remains public. After approval, the archived thesis cannot be silently replaced. Corrections use the university’s errata process.

32. AI tools do not become scientific sources

JYU permits AI-based applications in studies in principle, subject to teacher or unit instructions. Relevant generative-AI use in a thesis must be disclosed, and the student remains responsible for the accuracy, reasoning and final text. The university states that AI output is not a scientific source. If an AI system suggests a claim, locate and evaluate an appropriate original source before using the claim academically. Do not upload personal, confidential or restricted thesis data to an AI service unless the data-handling arrangement is explicitly appropriate and permitted.

33. Pseudonymised data can still be personal data

Information Systems projects often use interviews, surveys, organisational records, logs or platform identifiers. JYU treats information about an identified or identifiable living person as personal data, and pseudonymised information remains personal information when re-identification is possible. Plan controller roles, participant information, lawful processing, access, storage, retention and deletion before collection. Avoid describing a dataset as anonymous merely because names were replaced with codes. Consider combinations of timestamps, job roles, organisations and rare attributes that may still reveal identity.

34. Ethical review is conditional, but ethical responsibility is continuous

JYU human-sciences ethical review follows TENK principles. Formal prior committee review is required when the applicable criteria are met; participation by humans does not by itself create an automatic committee requirement. The researcher remains responsible for research ethics, and supervisors should ensure that thesis students understand applicable principles. Check review needs before data collection, especially where the design involves interventions, sensitive topics, vulnerable participants or other TENK triggers. A positive ethics statement does not transfer responsibility away from the thesis author.

35. Plan research-data management around the actual thesis data

JYU describes a Data Management Plan as a living document covering the lifecycle of research data: creation or collection, processing, storage, rights, security, publication, archiving or disposal. For an Information Systems thesis that creates or uses research data, make the plan proportionate to the project and compatible with privacy, contracts and supervisor/faculty requirements. Where formal ethical review is required, the DMP is a mandatory appendix to that review. Keep data-management language specific to the evidence you actually use rather than copying a generic plan from another project.

36. Cite consistently, but do not invent a universal Information Systems style

JYU requires writers to identify the sources they use when paraphrasing or quoting. The university notes that citation styles vary by field and that one chosen style should be used consistently. The current source does not establish APA, Chicago, MLA, Harvard or another style as universally mandatory for all Information Systems theses. Follow the Information Systems template, supervisor and programme-specific reporting guidance. Whatever style is used, make every source traceable and keep the reference list consistent with in-text citations.

37. Accessibility is part of final thesis quality

JYU requires digital theses to be accessible. Use structured heading styles, readable text, meaningful table structure and alternative text for relevant figures/images. The university provides instructions for producing an accessible PDF/A and the Vasara return page asks for an accessible PDF/A file. Starting from the correct Information Systems template reduces late-stage repair. Check accessibility before final submission, not after, because the Vasara version is final and the approved JYX record is not a workspace for silent replacement.

38. Build the timeline around research design, seminar and final review

A practical sequence is: confirm the current INSMP2024 structure; complete or plan TJTS5002, TJTS5010 and TJTS5011; agree a supervisor and topic; formulate the research or development problem; select a defensible method; enter TJTS5033 with a proposal; develop the mini-thesis and data plan; execute and document the research; draft TJTS5005; resolve ethics/data/citation/accessibility issues; complete supervisor review and Turnitin; confirm TJTS5004 instructions; register the thesis and maturity implementation in Sisu; create the final accessible PDF/A; then submit once in Vasara.

39. Final Information Systems checklist

Before submission, verify these exact points: INSMP2024 is still the active curriculum; TJTS5005 is the 30 ECTS thesis; TJTS5033 is the 5 ECTS seminar; TJTS5004 is the maturity object; the responsible supervisor meets the doctorate/JYU-employment rule; the Information Systems template is used; the method fits the question; literature/theory support the argument; data and ethics obligations are handled; AI use is disclosed if relevant; Turnitin is completed; Sisu registrations are active; the final file is accessible PDF/A; confidential background material is removed; and the Vasara upload is genuinely final. Recheck current JYU instructions at the point of submission because implementation details can change.