CS-300 / 6 credits

Teacher(s): Ailamaki Anastasia, Kashyap Sanidhya

Language: English


Summary

The purpose of this course is to discuss the design of database and operating systems concepts using a hands-on approach.

Content

Learning Prerequisites

Required courses

CS-202 Computer Systems

CS-302 Parallelism and concurrency in software (from 2024-2025)

Recommended courses

CS-200 Computer architecture

Important concepts to start the course

Algorithms and data structures, programming, parallelism

Learning Outcomes

By the end of the course, the student must be able to:

  • Identify and manage key components of database and operating systems
  • Choose or critique design choices for DB and OS system software
  • Express application information requirements and model the data of an application
  • Create and design a database with a practical application in mind while justifying choices
  • Explore how a DBMS and/or an OS performs work
  • Report performance and possible optimizations for applications

Teaching methods

Lectures, exercices,  and projects

Expected student activities

  • Attend the lectures in order to ask questions and interact with the professor
  • Attend the exercises session to solve and discuss exercises about the recently taught material
  • Work on a team project which covers the practical side of the course, e.g. build a key component of an OS or build an application for using a database system
  • Take a midterm and a final exam

Assessment methods

Labs (30%)

Midterm (25%)

Final exam (45%)

Supervision

Office hours Yes
Assistants Yes

Resources

Moodle Link

In the programs

  • Semester: Spring
  • Exam form: Written (summer session)
  • Subject examined: Data-intensive systems
  • Lecture: 2 Hour(s) per week x 14 weeks
  • Exercises: 1 Hour(s) per week x 14 weeks
  • Project: 2 Hour(s) per week x 14 weeks
  • Semester: Spring
  • Exam form: Written (summer session)
  • Subject examined: Data-intensive systems
  • Lecture: 2 Hour(s) per week x 14 weeks
  • Exercises: 1 Hour(s) per week x 14 weeks
  • Project: 2 Hour(s) per week x 14 weeks
  • Semester: Spring
  • Exam form: Written (summer session)
  • Subject examined: Data-intensive systems
  • Lecture: 2 Hour(s) per week x 14 weeks
  • Exercises: 1 Hour(s) per week x 14 weeks
  • Project: 2 Hour(s) per week x 14 weeks
  • Semester: Spring
  • Exam form: Written (summer session)
  • Subject examined: Data-intensive systems
  • Lecture: 2 Hour(s) per week x 14 weeks
  • Exercises: 1 Hour(s) per week x 14 weeks
  • Project: 2 Hour(s) per week x 14 weeks
  • Semester: Spring
  • Exam form: Written (summer session)
  • Subject examined: Data-intensive systems
  • Lecture: 2 Hour(s) per week x 14 weeks
  • Exercises: 1 Hour(s) per week x 14 weeks
  • Project: 2 Hour(s) per week x 14 weeks

Reference week

 MoTuWeThFr
8-9     
9-10     
10-11     
11-12CE4    
12-13    
13-14     
14-15     
15-16     
16-17  CE3  
17-18  CE3  
18-19    
19-20     
20-21     
21-22     

Monday, 11h - 13h: Lecture CE4

Wednesday, 16h - 17h: Exercise, TP CE3

Wednesday, 17h - 19h: Project, other CE3

Related courses

Results from graphsearch.epfl.ch.