Programmierpraktikum: Modelle Dynamischer SystemeModule description #40934 / Version 2
- 6 CP
- Portfolio examination
- Ungraded
- Winter and summer semester
- German
This module description is not valid in the current semester (Winter semester 2026/27).
Current version (v3)
| Module / Version | #40934 / #2 |
|---|---|
| Validity | Summer semester 2020 – Summer semester 2020 |
| Available language(s) | English, German |
| Credit points | 6 |
| Person responsible for the module | Nestmann, Uwe |
| Grading | Ungraded |
| Exam format | Portfolio examination |
| Language(s) of instruction | German |
Affiliation
| Faculty | Fakultät IV |
|---|---|
| Institute | Institut für Softwaretechnik und Theoretische Informatik |
| Academic chair | 34351900 FG Modelle und Theorie Verteilter Systeme (MTV) |
Contact
| Office | EN 24 |
|---|---|
| Contact person | Bisping, Benjamin |
| E-mail address | uwe.nestmann@tu-berlin.de |
| Website | https://www.tu.berlin/mtv/lehre/module-und-veranstaltungen/bachelormodule/modysy |
Learning outcomes
Successful participants of this module...
* have tried methods and tools of software engineering,
* have developed and reflected team working methods,
* got to know a modeling mechanism from the theory of distributed systems.
* have tried methods and tools of software engineering,
* have developed and reflected team working methods,
* got to know a modeling mechanism from the theory of distributed systems.
Content
* Practical software engineering, functional / object-oriented programming
* Agile project work
* Web and game development
* Quality control and DevOps
* Modeling mechanisms of distributed systems
* Agile project work
* Web and game development
* Quality control and DevOps
* Modeling mechanisms of distributed systems
Module components
Compulsory area
The following courses are mandatory for this module:
| Courses | Type | Number | Frequency | Language | Hours per week | Course catalog |
|---|---|---|---|---|---|---|
| Programmierpraktikum: Modelle Dynamischer Systeme | Internship | Winter and summer semester | [de] | 4 | ISIS |
Workload and credit points
Programmierpraktikum: Modelle Dynamischer Systeme (Internship)
| Workload description | Multiplier | Hours | Total |
|---|---|---|---|
| Presence | 15 | 4 h | 60 h |
| Project | 15 | 6 h | 90 h |
| Preparation for presentations, consultation | 5 | 6 h | 30 h |
| 180 h | |||
The workload of the module adds up to 180 hours. The module therefore comprises 6 credit points.
Description of teaching and learning methods
Project team and small group work, team meetings, presentations, milestones, project management and documentation maintenance.
Requirements for participation and examination
Desirable prerequisites for participation in the courses:
* Knowledge from the course software engineering and programming paradigms
* Good programming skills in any language, preferably Java / Scala / JavaScript.
* Good programming skills in any language, preferably Java / Scala / JavaScript.
Mandatory requirements for the module examination registration:
This module has no examination requirements.
Completion of the module
| Grading | Ungraded |
|---|---|
| Exam format | Portfolio examination |
| Type of portfolio examination | 100 points in total |
| Language | German |
Test elements
| Name | Points/Weight | Category | Duration/Extent |
|---|---|---|---|
| (Deliverable assessment) Software functionality and software quality | 30 | practical | approx. 4 milestones |
| (Deliverable assessment) Editing tickets | 50 | practical | approx. 12 weeks constantly |
| (Learning process review) Consultation | 20 | oral | 20 minutes |
Exam description
The exam is not graded, an overall grade according to § 47 (2) AllgStuPO is therefore not determined. The module exam is passed if at least 60 out of 100 portfolio points have been reached.
Software functionality and quality (30 points) is that each milestone achieves the targeted objectives and the software meets quality standards for code quality, testing and documentation.
The editing of tickets (50 points) records whether the participants have individually worked out a reasonable number of tickets (for example, two per week) at the beginning of the event.
In the oral consultation (20 points) the students show individually what they have learned and contributed to the project.
Software functionality and quality (30 points) is that each milestone achieves the targeted objectives and the software meets quality standards for code quality, testing and documentation.
The editing of tickets (50 points) records whether the participants have individually worked out a reasonable number of tickets (for example, two per week) at the beginning of the event.
In the oral consultation (20 points) the students show individually what they have learned and contributed to the project.
Duration of the module
The following number of semesters is estimated for taking and completing the module: 1 semester(s).
This module can be started in the following semesters: Winter and summer semester.
Maximum number of participants
The maximum capacity of participants is 30.
Registration procedures
Participation to the class (not to be confused with registration for the module exam) is run via a course within Moodle-platform ISIS.
The registration for the module examination takes place at the examination office or via the QISPOS platform.
POS examination number: 2348394
The registration for the module examination takes place at the examination office or via the QISPOS platform.
POS examination number: 2348394
Recommended reading, lecture notes
Lecture notes
unavailable
Electronic lecture notes
unavailable
Recommended literature
No recommended literature given
Assigned programs
This module is not used in any program.
Miscellaneous
Not specified