Praktikum: Computer Systems Lab (IN0012, IN2106, IN2128)
Course 0000001690 in SS 2021
General Data
| Course Type | practical training |
|---|---|
| Semester Weekly Hours | 6 SWS |
| Organisational Unit | Informatics 1 - Chair of Engineering Software for Decentralized Systems (Prof. Bhatotia) |
| Lecturers |
Pramod Bhatotia Redha Gouicem Atsushi Koshiba |
| Dates |
1 singular or moved dates |
Assignment to Modules
-
IN2106: Master-Praktikum / Advanced Practical Course
This module is included in the following catalogs:- Further Modules from Other Disciplines
Further Information
Courses are together with exams the building blocks for modules. Please keep in mind that information on the contents, learning outcomes and, especially examination conditions are given on the module level only – see section "Assignment to Modules" above.
| additional remarks | The course strives to encourage students to do systems research: “Design, implementation, and analysis of complex software systems”. The focus is on learning the art of systems research by building, analyzing, reproducing, and breaking practical computer systems! The term computer systems covers a broad range of topics, including distributed systems, systems for machine learning/AI, systems security, large-scale data analytics systems, storage systems, operating systems, file-systems, databases, multicore architectures, synchronization/concurrency primitives, parallel systems, compiler-assisted systems, dependability, reliability, cloud/edge computing, IoT systems, etc. In short, we will focus on software systems that solve important practical problems! More specifically, the students will be given prominent open-source projects (research papers and associated software artifacts) covering the aforementioned research topics. The students (possibly in a team of three) will have to accomplish the following primary tasks: 1. Stage 1: Literature review -- To understand the system and associated research area. 2. Stage 2: Artifact evaluation -- Analyze the source code of the system artifact, and reproduce its experimental evaluation. 3. Stage 3: Proof-of-concept -- Build the core idea of the project on a smaller scale, and show the effectiveness of the core ideas or demonstrating the limitations to pave a way for future research. The students are encouraged to propose and implement new ideas based on their proof-of-concept. 4. Submit three reports after each stage covering: (a) the literature review, (b) artifact evaluation, (c) proof-of-concept. In terms of organization, there will be four mandatory meetings: Meeting #1: Kick-off: Paper selection and details on how to proceed. Meeting #2: Project selection and artifact evaluation plan: Presentation of the research project and plan for the artifact evaluation. (Report #1 for the literature review is due.) Meeting #3: Proof-of-concept: Report on the artifact evaluation and proof-of-concept evaluation. (Report #2 for the artifact evaluation is due.) Meeting #4: Final presentation and demo: Demo of proof-of-concept and results of reproduction. (Report #3 for the proof-of-concept is due.) Additionally, weekly office hours will be held each week during the course for consultation. IMPORTANT: The top students will be nominated/encouraged to participate in the artifact evaluation committee for the major computer systems conferences: OSDI, SOSP, ASPLOS, EuroSys, etc. It's prestigious to serve on the artifact evaluation committee of a conference. |
|---|---|
| Links |
Course documents TUMonline entry |
Equivalent Courses (e. g. in other semesters)
| Semester | Title | Lecturers | Dates |
|---|---|---|---|
| WS 2022/3 | Praktikum: Computer Systems Lab (IN2106, IN4340) |
Gouicem, R.
Koshiba, A.
Mainas, C.
Misono, M.
Okelmann, P. … (total 6)
Responsible/Coordination: Bhatotia, P. |
|
| WS 2021/2 | Praktikum: Computer Systems Lab (IN0012, IN2106, IN212811) |
Responsible/Coordination: Bhatotia, P. |