Master of Science in Software Engineering

Master of Science in Software Engineering is a joint curriculum of the University of Tartu and the Tallinn University of Technology. The current page contains information about the relevant courses given at the Tallinn University of Technology.

Campus information

To find your way around the TUT campus, please take a look at [1], there is also a map available there.

Access to TUT Study Information System

It is necessary to register to the courses given at TUT in TUT Study Information System (Õppeinfosüsteem, ÕIS for short). To access it you need to either

• Use your ID card or residence permit with a chip to log in at https://ois.ttu.ee
• If you do not have the chip card, you will need to go to the ÕIS admins in room SOC-132 to get a username and password.

Login to lab computers, submission of homeworks

To log in to labs and to submit homeworks in many courses you will need to know your Uni-ID. You are able to find it out and set a password at pass.ttu.ee by again using your ID card or residence permit with a chip. (You are also able to log into the lab computers with the chip card).

If you do not have the chip card, you will be able to find out your Uni-ID and set passwords in room ICT-410.

Timetables

It is possible to view the timetables by going to [2] and selecting "Timetables" from the left menu. Then look for your group (Autumn semester: IVSM11, IVSM12, IVSM31, IVSM32, Spring semester IVSM21, IVSM22).

1st semester

Core module

ITT8060 Advanced programming (Autumn semester)

IDY0204 Software Quality and Standards (Autumn semester)

Embedded and real-time software specialization

ITI8500 Foundations of embedded real-time systems (Lecture Fri 16:00-17:30 in room ICT-A1, Lab 17:45-19:15 in room ICT-404)

3rd semester

Embedded and real-time software specialization

ITI8510 Real-time operating systems and systems programming (Lecture Wed 10:00-11:30, ICT-405, lab Wed 12:00-13:30, ICT-405)

ITI8520 Real-Time Software Engineering (Access to Moodle web will be explained in the lecture), (Lecture Thu 12:00-11:30, room U03-308, labs by appointment with Risto Serg).

Electives

ITI8600 Methods of Knowledge Based Software Development (the Moodle course available at [3]).

IDY0201 Requirements Engineering (Enn Õunapuu, Lecture Thu 14:00-15:30, room U05-409, Lab Fri 10-11:30 ICT-404)

ITX8301 MSc seminar I, Wednesdays 16:00-17:30, ICT-411, check schedule on the seminar web page.

or ITX8302 MSc seminar II, Wednesdays 16:00-17:30, ICT-411, check schedule on the seminar web page.

Practical training

ITX8510 offers 6 ECTS for Internships & Practical trainings. ITX8511 offers 12 ECTS for Internships & Practical trainings.

If you are looking for a new internship place, please contact: Juhan Ernits.

If you have already work experience, the requirements to get this recognised are as follows:

The work that you have done must be in an IT-related field. You must have worked at least 4 weeks full-time, or 8 weeks part-time (at 50%).

Your supervisor will have to sign a form and evaluate your work progress. Internship regulations and supervisor form can be found on the Internship regulation and forms page (http://www.ttu.ee/public/i/infotehnoloogia-teaduskond/Praktikatoend2014_ENG.doc). This signed supervisor form needs to be given to the Dean's office and/or uploaded to OIS (e.g., do NOT give it to me directly, i might misplace your paper).

You will need to document what you have been working on and write a report about it. Guideline is about ~2 pages. This paper should be well structured AND in academic writing style, e.g., with introduction/overview, (work-)problem-statement, solution/methodology/achievements, and conclusion. See also the faculty guidelines for information on what questions to address in your report.

You will have to give a presentation about what you have done during your work/internship. This presentation should not only give an overview of what the company is/was doing, but also present some particular projects and problems that you have been working on. If you have worked in a team, also explain how this went and what your contribution was. The presentation should not be longer than 10-15 min, and you should expect questions at anytime.

This is NOT a regular course, you find it under "applications" in OIS. Please upload the signed supervisor form to OIS and/or give it to the Dean's office. E-mail Juhan Ernits, about your presentation. Note places for the seminar are assigned on a first-come-first-serve basis and might be full. You are welcome to attend any seminar as a listener/ask questions/participate in the discussions. If you have any issues with registering this course in OIS, please contact the study office/deans office on the 4th floor of the IT-building.

There will be roughly once a month a preassigned time-slot opportunity for your presentation. Please contact Juhan Ernits at least one week in advance, if you are planning to attend any of those sessions. Sessions resume at the beginning of next semester.

(TBA)

Note that If you presentation contains some confidential material, then we will arrange a private presentation for your presentation.

If you have any questions, please don't hesitate to contact: Juhan Ernits

Thesis

Deadlines for defence in June 2016

If you are following the MSc Seminar, there are some thesis related deadlines set within that seminar.

• December 1, 2015 January 31, 2016 (the extension is only valid for 2015/16 year only): Thesis problem statement submitted here. (You need to know your UniID at TUT to log in. You can find it out by logging in to [4] with your ID card or residence permit. You may also need to reset your password there.)
• 10 work days from problem statement submission: Feedback (unless you have already received feedback within the MSc seminar)
• May 1, 2016: Thesis submission deadline
• May: Reviews returned to students
• May: Final printed version of the thesis submitted.

Supervisors

• Jüri Vain
  • Topic areas: mode-based planner synthesis for non-deterministic and distributed systems.
  • Contact: juri.vain (a) ttu.ee
• Tanel Tammet
  • Topic areas: automated theorem proving, logic based methods in network software
  • Contact: tanel.tammet (a) ttu.ee
• Jaan Penjam
  • Topic areas: programming language syntax and semantics, evolutionary algorithms, algebraic automata theory
  • Contact: jaan (a) cs.ioc.ee
• Tarmo Uustalu
  • Topic areas: structured proof theory and type theory, algebraic and categorical logic, program language semantics, program logics, functional programming, methods of program transformation and construction, applications of modal logics in computer science
  • Contact: firstname (a) cs.ioc.ee
• Marko Kääramees
  • Topic areas: formal methods, model-based testing of software, algorithms, system administration.
  • Contact: marko.kaaramees (a) ttu.ee
• Sven Nõmm
  • Topic areas: non-linear control systems, modelling, analysis, synthesis
  • Contact: sven.nomm (a) ttu.ee
• Juhan Ernits
  • Topic areas: model-based testing (including for smart devices, IoT, server side software, robots), applications of functional programming technology (F#), model-based fault detection, 3D mapping using video streams
  • Contact: juhan.ernits (a) ttu.ee
• Gert Kanter
  • Topic areas: robot testing, robot software based on ROS, control of robotic manipulators.
  • Contact: gert.kanter (a) ttu.ee
• Ago Luberg
  • Topic areas: tourism recommender systems, software intensive systems.
  • Contact: ago.luberg (a) ttu.ee
• Evelin Halling
  • Topic areas: model-based testing, social robotics
  • Contact: evelin.halling (a) ttu.ee
• Maili Markvardt
  • Topic areas: software testing, e.g.
    • Software testing process, methods & tools in the example of company or organization The aim of this topic is to design and implement comprehensive testing process in an organization, including testing tasks and responsibilities, methods and supporting tools according to analysis of needs. The result (improvement) of implementing the new process must be measurable.
    • Choosing and/or developing test exectution tool/test management tool for a project or organization The aim of this topic is to analyse current situation or problem and choose most appropriate toolset for solving this problem. It can also be considered as implementing (programming) suitable test harness or tool for a specific project.
    • Practical solutions for measuring software test coverage (white and black box) and its relations to testing and development process costThis topic includes finding a way to measure test coverage, implement (additional) tests to increase the coverage and measure if achieved level of coverage is sufficient and if it is economically reasonable (not too expensive to achieve and manage in long term).
    • Survey on cost of software bugs in the example of Estonian public and private sector software systems This topic includes analysis of bugs and IT related problems and creating a framework that could be used in Estonia for assessing cost of live bugs and estimating necessary testing efforts.
  • Contact: maili.markvardt (a) ttu.ee
• Jaagup Irve
  • Topic area: Systems level software, user interfaces
  • Contact: jaagup.irve (a) ttu.ee

If you cannot find a supervisor matching your interests, please contact prof. Jüri Vain (juri.vain (a) ttu.ee) or Juhan Ernits (juhan.ernits (a) ttu.ee) for further information.