052500 VU Distributed Systems Engineering (2023S)
Prüfungsimmanente Lehrveranstaltung
Labels
An/Abmeldung
Hinweis: Ihr Anmeldezeitpunkt innerhalb der Frist hat keine Auswirkungen auf die Platzvergabe (kein "first come, first served").
- Anmeldung von Mo 13.02.2023 09:00 bis Do 23.02.2023 09:00
- Abmeldung bis Di 14.03.2023 23:59
Details
max. 50 Teilnehmer*innen
Sprache: Englisch
Lehrende
Termine (iCal) - nächster Termin ist mit N markiert
The preliminary talk will take place for all course groups during the first lecture session in lecture hall "Hörsaal 1, Währinger Straße 29 1.UG"
- Dienstag 07.03. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 14.03. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 21.03. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 21.03. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 24.03. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
- Dienstag 28.03. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 28.03. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 31.03. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
- Dienstag 18.04. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Freitag 21.04. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
- Dienstag 25.04. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 25.04. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Mittwoch 26.04. 20:15 - 21:30 Hörsaal 1 Oskar-Morgenstern-Platz 1 Erdgeschoß
- Dienstag 02.05. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 09.05. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 09.05. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 12.05. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
- Dienstag 16.05. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 23.05. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 23.05. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 26.05. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 02.06. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
- Dienstag 06.06. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
-
Dienstag
06.06.
15:00 - 16:30
Seminarraum 3, Währinger Straße 29 1.UG
Seminarraum 7, Währinger Straße 29 1.OG - Dienstag 13.06. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 13.06. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 16.06. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
-
Dienstag
20.06.
11:30 - 13:00
Hörsaal 1 Oskar-Morgenstern-Platz 1 Erdgeschoß
Hörsaal 1, Währinger Straße 29 1.UG - Dienstag 20.06. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 23.06. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
- Dienstag 27.06. 11:30 - 13:00 Hörsaal 1, Währinger Straße 29 1.UG
- Dienstag 27.06. 15:00 - 16:30 Seminarraum 7, Währinger Straße 29 1.OG
- Freitag 30.06. 13:15 - 14:45 Seminarraum 7, Währinger Straße 29 1.OG
Information
Ziele, Inhalte und Methode der Lehrveranstaltung
Art der Leistungskontrolle und erlaubte Hilfsmittel
* Several written examinations
* Practical project, to be tackled by a selected group of students (distributed software project: preparation/analysis, design, implementation, and presentation)
* Theoretical analysis of tasks and related literature studies
* Contribution during but also outside the course units (e.g., studying lectures, online, and written materials, taking part in self-assessment tasks, preparing programming tasks etc.)
* Working on the provided materials and presenting the results, ideas and conceptsAll submissions must be handed in due time via Moodle/GitLab or the respective relevant platform. The use of aids (unless explicitly permitted by the lecturers before the exam) during the exams is not permitted. All exams/quizzes and programming tasks are individual work. The practical assignment is a group project which must be worked on only by the respective group members. Any sources and third-party materials must be cited while working on the submissions.
* Practical project, to be tackled by a selected group of students (distributed software project: preparation/analysis, design, implementation, and presentation)
* Theoretical analysis of tasks and related literature studies
* Contribution during but also outside the course units (e.g., studying lectures, online, and written materials, taking part in self-assessment tasks, preparing programming tasks etc.)
* Working on the provided materials and presenting the results, ideas and conceptsAll submissions must be handed in due time via Moodle/GitLab or the respective relevant platform. The use of aids (unless explicitly permitted by the lecturers before the exam) during the exams is not permitted. All exams/quizzes and programming tasks are individual work. The practical assignment is a group project which must be worked on only by the respective group members. Any sources and third-party materials must be cited while working on the submissions.
Mindestanforderungen und Beurteilungsmaßstab
Core Course Work (“normal points”):
To pass the course, at least 44% of the possible normal 47 points for the theoretical part must be reached.
To pass the course, at least 44% of the possible normal 47 points for the practical part must be reached.
To pass the course, at least 50% of the overall normal 100 points must be reached. These 100 points also include points that can be earned by active participation in a hands-on task (5 points) and giving feedback (1 point).The maximum number of total points is 100 points. If the course is passed, the grade is determined from the total achieved points as follows:- >= 89 total points: Sehr Gut (1)
- >= 76 total points: Gut (2)
- >= 63 total points: Befriedigend (3)
- >= 50 total points: Genügend (4)
------------------------------------------
not passed: Nicht Genügend (5)Attendance and Participation:
Participation in the INTRO quiz on Moodle is mandatory (explained in the preliminary talk). Failing to do so in time will result in your deregistration from this course.After the preliminary lecture:
* Theoretical part: no compulsory attendance. Active participation in these units is recommended to support your exam preparations.
* Practical part: no compulsory attendance. Active participation is recommended to get feedback on your concepts and designs and to discuss questions related to the given assignment.
* Submission presentation: attendance on the dates assigned to the students is required to receive related points
* Hand-on task: attendance on the dates assigned to the students is required to receive related points
To pass the course, at least 44% of the possible normal 47 points for the theoretical part must be reached.
To pass the course, at least 44% of the possible normal 47 points for the practical part must be reached.
To pass the course, at least 50% of the overall normal 100 points must be reached. These 100 points also include points that can be earned by active participation in a hands-on task (5 points) and giving feedback (1 point).The maximum number of total points is 100 points. If the course is passed, the grade is determined from the total achieved points as follows:- >= 89 total points: Sehr Gut (1)
- >= 76 total points: Gut (2)
- >= 63 total points: Befriedigend (3)
- >= 50 total points: Genügend (4)
------------------------------------------
not passed: Nicht Genügend (5)Attendance and Participation:
Participation in the INTRO quiz on Moodle is mandatory (explained in the preliminary talk). Failing to do so in time will result in your deregistration from this course.After the preliminary lecture:
* Theoretical part: no compulsory attendance. Active participation in these units is recommended to support your exam preparations.
* Practical part: no compulsory attendance. Active participation is recommended to get feedback on your concepts and designs and to discuss questions related to the given assignment.
* Submission presentation: attendance on the dates assigned to the students is required to receive related points
* Hand-on task: attendance on the dates assigned to the students is required to receive related points
Prüfungsstoff
Object-oriented programming and UML modelling skills are required. You will also need to create software architectures while taking common best practices and patterns into account. Java experience and programming skills are expected. If you feel that you lack in these areas: Attend a software engineering focused course, like SE1 or SE2, before or while attending DSE.* Lecture notes (as slides) and exercise materials from Moodle
* Worksheets, self-evaluation quizzes, and programming tasks
* Lecture sessions, materials, and the practical assignment
* Literature/Web References on the Reading List, Provided Reading Materials, and referenced LiteratureQuality assurance:
All content submitted by students can be checked for plagiarism and/or cheating using automatic tools and individual inquiries. This can be done on concrete suspicion or on a random basis. Any (partial) performance obtained by fraud leads to an 'X' in your transcript, meaning that you have been caught cheating or plagiarizing.
* Worksheets, self-evaluation quizzes, and programming tasks
* Lecture sessions, materials, and the practical assignment
* Literature/Web References on the Reading List, Provided Reading Materials, and referenced LiteratureQuality assurance:
All content submitted by students can be checked for plagiarism and/or cheating using automatic tools and individual inquiries. This can be done on concrete suspicion or on a random basis. Any (partial) performance obtained by fraud leads to an 'X' in your transcript, meaning that you have been caught cheating or plagiarizing.
Literatur
M. Völter, M. Kircher, U. Zdun: Remoting Pattern. Wiley & Sons (2004)
G. Hohpe, B. Woolf: Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison Wesley (2003)
A. S. Tanenbaum, M. van Steen: Distributed Systems: Principles and Paradigms. CreateSpace (2016)
C. Kecher, A. Salvanos: UML 2.5: Das umfassende Handbuch. Rheinwerk Computing (2015)Further:
* Lecture slides and the accompanying course material.
* For each course unit, we provide additional recommended reading materials including Web references.
* For the practical assignment, we recommend studying different topics which are related to software design. One should read up on these topics if you are not already aware of them based on previous courses. For this, we provide a starting point, but depending on your skill level you might need to gather additional material.
G. Hohpe, B. Woolf: Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison Wesley (2003)
A. S. Tanenbaum, M. van Steen: Distributed Systems: Principles and Paradigms. CreateSpace (2016)
C. Kecher, A. Salvanos: UML 2.5: Das umfassende Handbuch. Rheinwerk Computing (2015)Further:
* Lecture slides and the accompanying course material.
* For each course unit, we provide additional recommended reading materials including Web references.
* For the practical assignment, we recommend studying different topics which are related to software design. One should read up on these topics if you are not already aware of them based on previous courses. For this, we provide a starting point, but depending on your skill level you might need to gather additional material.
Zuordnung im Vorlesungsverzeichnis
Module: DSE IST VMI VIN
Letzte Änderung: Di 09.05.2023 09:47
* Interactive discourse with your colleagues and lecturers
* Conception, planning and implementation of a simplified but realistic project
* Individual and group work on related practical and theoretical topics
* Students can present submissions and concepts to receive feedback
* Online self-evaluation and programming tasks
* Blended Learning