Alternative web page of the study program
Contact the lecturer in order to get information about the consultation hours. Contact information of the lecturer can be easily found by using the TTÜ personnel search engine.
It is possible to view the timetables by going OIS2 and selecting "Timetables" from the left menu. Then look for your group (Autumn semester: IVSM11, IVSM12, IVSM31, IVSM32, Spring semester IVSM21, IVSM22). Please note that there may be changes in the timetable until the beginning of September for Autumn semester / beginning of February for Spring semester.
For combining your electives and free choice courses, please check out the "condensed timetable" link.
|Agile Software Development||The course will take place in Tartu. If you choose the Embedded and real-time software specialization and stay in Tallinn, you will be able to reimburse your bus/train tickets for attending the core module courses in Tartu. Contact email@example.com for further information.|
|Systems Modelling||The course will take place in Tartu. If you choose the Embedded and real-time software specialization and stay in Tallinn, you will be able to reimburse your bus/train tickets for attending the core module courses in Tartu. Contact firstname.lastname@example.org for further information.|
|IDY0204 Software Quality and Standards||by Jaak Tepandi. Lectures on Wednesdays at 10-11.30 room U06-201, practical lessons on Wednesdays at 12-13.30 room ICT-401. |
|ITT8060 Advanced Programming||by Juhan-Peep Ernits. Lectures on Wednesdays at 14-15.30 room U06-201, practical lessons Wednesdays at 16-17.30 room ICT-401.|
|ITI8600 Methods of Knowledge Based Software Development||by Juhan- Peep Ernits. Lectures on Fridays at 8-9.30 room CYB-VEENUS, practical lessons on Fridays at 14-15.30 room ICT-121, ICT-122.|
|Embedded and real-time software specialization|
|ITI8510 Real-time Operating Systems and Systems Programming||by Jaagup Irve. Lectures on Fridays at 10-11.30 room ICT-A1, practical lessons on Fridays at 12-13.30 room ICT-401.|
|ITX8522 Software Entrepreneurship Project||by Juhan-Peep Ernits. Practical lessons on Tuesdays at 16-19.00 room ICT-312.|
|Embedded and real-time software specialization|
|ITX8302 Master seminar II||by Juhan-Peep Ernits. Practical lessons on Fridays at 12-13.30 room ICT-312.|
All the rest of the compulsory courses should be done by the 3rd semester. You will have the option to participate in a startup project or carry out your practical training in addition to the elective courses.
You will have a palette of MSc level courses to choose from as a free studies course that would support your personal interests and help you in making your skills set unique and attractive to potential employers.
|ITI8600 Methods of Knowledge Based Software Development||by Juhan- Peep Ernits. Lectures on Fridays at 8-9.30 room CYB-VEENUS, practical lessons on Fridays at 14-15.30 room ICT-121, ICT-122.Embedded and real-time software specialization|
|IDY0201 Requirements Engineering||by Enn Õunapuu. Lectures on Wednesday at 16-17.30 room U05-105, practical lessons on Wednesdays at 17.45-19.15 room U05-105.|
|Suggested courses that will count as electives|
|IDN0110 Data mining|
For students staying in Tartu a shuttle bus will be provided to take them to Tallinn on Wednesdays and back to Tartu in the evening. The bus will start at 7:15 from Raatuse 22, Tartu and return at 18:00 from Ehitajate tee 5 TTÜ main building.
The buildings of the TTÜ campus can be located by the help of the Campuse_map_2017.
|Course code||Course title||Link to ÕIS/ homepage|
|IAF0530||Dependability and Fault Tolerance||ÕIS|
|IDU8520||Software - project||ÕIS|
|IDY0202||Software Engineering Paradigms||ÕIS|
|IDY0203||Agent-Oriented Modelling and Multiagent Systems||ÕIS|
|IDY0204||Software Quality and Standards||ÕIS|
|ITI8590||Advanced Algorithms and Data Structures||ÕIS|
|ITI8600||Methods of Knowledge Based Software Development||ÕIS|
|ITX8301||Master seminar I||ÕIS|
|ITX8302||Master seminar II||ÕIS|
|ITX8511||Practical Training in Information Technology||ÕIS|
|ITX8522||Software Entrepreneurship Project||ÕIS|
|MTAT.03.243||Software Engineering Management||ÕIS|
|MTAT.03.262||Mobile Application Development||ÕIS|
|MTAT.03.270||Seminar on Enterprise Software||ÕIS|
|MTAT.03.295||Agile Software Development||ÕIS|
|MTAT.03.307||Principles of Secure Software Design||ÕIS|
|MTAT.07.015||Secure Programming Techniques||ÕIS|
|MTAT.07.016||Secure Programming Techniques: Project Work||ÕIS|
|TMJ3331||Entrepreneurship and Business Planning||ÕIS|
|Speciality 1: Embedded and real-time software engineering|
|ITI8500||Foundations of Embedded Real-Time Systems||ÕIS|
|ITI8510||Real-time Operating Systems and Systems Programming||ÕIS|
|ITI8520||Real-Time Software Engineering||ÕIS|
|ITI8531||Software Synthesis and Verification||ÕIS|
|Speciality 2: Enterprise software engineering|
|MTAT.03.229||Enterprise System Integration||ÕIS|
|MTAT.03.231||Business Process Management||ÕIS|
Tüüpõpingukava leiad Õppeinfosüsteemist.
In software engineering you need to complete 18 ECTS worth of practical training. You can choose between getting credit for internships or doing project courses listed under the practical training module. The below information currently concerns only the credit for internships. Please note that starting with the 2016 cohort, the students choosing the Enterprise Software specialization will need to choose from the two course codes below (or both) to get credit for internships at companies. The embedded and real time software engineering students will need register their internships in University of Tartu.
To get your practical training assessed, you will need to complete a 4 step process and pick from the two intership credit codes:
- ITX8510 offers 6 ECTS for Internships & Practical trainings. (4 weeks of full time work)
- ITX8511 offers 12 ECTS for Internships & Practical trainings. (8 weeks of full time work)
If you have found the company or government agency where you want to carry out your internship and have an idea about the duration of the internship, then you should contact the representative at the company and sign the follwing internship form:
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. For every 6 ECTS you must have worked at least 4 weeks full-time, or 8 weeks part-time (at 50%). You will still be asked to complete the practical training plan to be sure that the internship / practical training gets accepted.
Sign the form, have it signed by the supervisor at the company and then enrol yourself to the IVSM internships and practical training course and upload it to the appropriate assignment.
NB! No forms should be forwarded by e-mails!
2) Your supervisor at the legal entity where you carry out your internship 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. This signed supervisor form needs to be scanned and uploaded to the appropriate assignment in ained.ttu.ee.
You can give the paper copy to the member of staff during your practical training seminar.
3) You will need to write a report about your internship. The guidelines of what the report should contain is given in the following document: Internship report guidelines.pdf. That needs to be submitted together with the supervisor form mentioned in the previous point.
4) 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 be 8-10 min, and you should expect questions at any time.
The slots are listed in the ained.ttu.ee under an appropriate course. Please write your name (by not exceeding the maximum student count) under the appropriate date. Please note that there are meetings in Tartu and Tallinn listed.
Before the seminar, you should file the application to register practical training under the appropriate course code (ITX8510 and/or ITX8511) in TTÜ ÕIS. NB! Please press the "submit" button as well!
|Juhan-Peep Ernits||Department of Software Scieneemail@example.com|
Internship coordinator is an advisor, who, if necessary, recommends a place for internship, and explains and specifies the requirements for an internship
When writing the thesis you should follow the TTÜ School of IT thesis formatting guidelines
Deadlines for defence in May/June 2018
December 1, 2017: Thesis problem statement submission
May 7, 2018: Thesis pdf-file submission
May 14, 2018: Bring one paper copy of the theses to Siiri Taveter in ICT-429 at 10:00-12:00 and 13:00-16.30
End of May / beginning of June, 2018: Thesis defence
|mode-based planner synthesis for non-deterministic and distributed systems|
|automated theorem proving, logic based methods in network software|
|programming language syntax and semantics, evolutionary algorithms, algebraic automata theory|
|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|
|formal methods, model-based testing of software, algorithms, system administration|
|non-linear control systems, modelling, analysis, synthesis|
|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|
|robot testing, robot software based on ROS, control of robotic manipulators, software engineering in robotics|
|tourism recommender systems, software intensive systems|
|model-based testing, social robotics|
|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.
|Jaagup Irve |
|Systems level software, user interfaces|
|Integrating verification methods and tools for complex real-time systems, possible case studies include: heating, ventilation and air-conditioning (HVAC), autonomic feeding tractor, or a Nanosatellite. |
Implementing model transformation between Event-B and Uppaal Timed Automata.
Implementing tool support for Model-Based Testing workflow.
Verification of hard real-time scheduling on multi-core platforms for mixed-critical applications.
If you cannot find a supervisor matching your interests, please check the topics offered in other MSc curricula at TTÜ.
If you still could not find a suitable topic, please contact prof. Jüri Vain (firstname.lastname@example.org) or Juhan Ernits (email@example.com) for further information.
|Juhan-Peep Ernits ||Siiri Taveter |
|Program Manager||Assistant to Program Manager|