Home page of the course
Introduction to Databases

News

All announcements and up-to-date information about the course will be given on the 2024/25 - Introduction to Databases MS Team set up for the course.

Content

1. Course description
2. General information
3. Information about the exam
4. Information about the project
5. For students who have to take the 8CFU exam

Course Description

• Introduction to Databases (Course Slides). Diego Calvanese, Giuseppe De Giacomo, Maurizio Lenzerini. 2021.
  The slides will be made available during the course and can be downloaded in MS Teams from the Class Materials folder in the 2023/24 - Introduction to Databases MS Team.
• Esercises solved in class.
  The exercises are assigned for the lab hours, and the solutions are made available in the week after the lab in the same Class Materials folder in the 2022/23 - Introduction to Databases MS Team.
• Database Management Systems (3rd edition). Raghu Ramakrishnan, Johannes Gehrke. McGraw-Hill, 2005.
  Available at University Library Bozen: 13-Textbook Collection (ST 271).
  The textbook is suggested, but not strictly necessary.

General Information

• Office hours

• Tutor: Francesco Di Cosmo

• Schedule: The course is taught online via MS Teams in the 1st semester: from 1 October 2024 to 24 January 2025.
  • Lectures:
    • Tuesday, 10:30-12:30, Lecture Room NOI B1.2.16 (usually)
    • Thursday, 8:30-10:30, Lecture Room NOI B1.2.03 (usually)
  • Labs: Tuesday, 13:30-15:30, Lecture RoomB1.2.16 (usually)

  See also the on-line timetable page for changes.

• Additional teaching material
  • Past exams (in part with solutions)

Information about the Exam

• Exam Mark The final mark is based on:
  1. a project [30% of mark] (see below for more information about the project), and
  2. a final written exam [70% of mark].
  The final mark is computed as a weighted average of the exam mark (70%) and the project mark (30%).
• Written Exam
  1. To be admitted to the written exam (2), the student must have discussed the project (1), and the project must have been evaluated positively. In other words, without having passed the project, the written exam cannot be taken.
  2. In case of a positive mark, the project mark will count for all 3 regular exam sessions of the Academic Year (i.e., if the student fails or does not take the written exam, they keep the project mark and only need to retake the final written exam).
  3. To pass the exam, the student has to pass also the written exam (2), in addition to the project (1).
  4. At the written exam, which lasts at least 2 hours, the student will have to carry out the design of a small database, following a given specification. Moreover they will have to write down some SQL queries, and possibly answer in written form some questions about the topics covered in the course.
  5. The written exam is a closed-book exam, meaning that the only allowed resources are blank paper and pens (in addition to one's own brain, of course). However, each student may use a single handwritten A4 page that contains information they consider useful for solving the exam exercises. These notes should be personal, and not notes that one obtains from others. Note that creating one's own notes is an integral part of the learning process and, as such, it is way more useful than just copying someone else's notes.

Information about the Project

• Rules for the Project
  1. The project can be developed either alone, or in a group of two.
  2. When the project is developed in a group of two, the numbers given below as upper bounds should be considered as lower bounds.
  3. The project is based on the design of a simple database, following a specification of the requirements that the students provide on their own, and that must be discussed and agreed upon with the lecturer/TA. As a starting point for the discussion, the student should ideally provide an initial written description of the application domain (the specification of the requirements) and a draft of the ER schema that is as complete as possible (with respect to the specification). By "draft" we intend the schema with the entities and relationships and just the main attributes, typically the identifiers. The diagram can be drawn by hand and does not need to be fancy, but should be readable. Typically, in the initial discussion and also in the initial desing phases, the diagram gets revised, so initially it is not worth spending too much time on the layout or graphical appearance. Alternatively, for the discussion, the students can also present just the draft of the ER diagram, and describe the application domain in the meeting. However, trying to write up the specification of the application domain is a good exercise to better understand which information the database should store. And this specification is in any case required as part of the project documentation.
  4. Students are strongly encouraged to confirm with the lecturer/TA also the final version of the ER diagram, before they start working on the subsequent phases of the design of their database. They are also encouraged to use the office hours to clarify any doubts they might have about the various design phases. This helps to avoid that serious problems with their design get discovered only when the project is discussed as part of the exam. This could cause the project to be evaluated negatively, which would prevent the student from taking the written exam.
  5. Roughly speaking, the specification of the requirements should satisfy the following criteria:
     1. It should be based on a domain containing between 6 and 10 main conceptual entities (i.e., without counting sub-entities that appear in ISAs or generalizations).
     2. There should be some structure in the set of entities, i.e., the ER schema should in addition contain at least one ISA and at least one generalization.
     3. There should be sufficient structure in the relationships, which usually means that the representation of the ER schema as a graph (where the nodes are given by the entities and relationships, and the edges are given by the participation of entities in relationships) should contain some cycles.
     4. The schema should contain cardinality constraints on the participation of entities to relationships that are different from the default (0,n). In particular, there should be at least one relationship with a cardinality (1,n) on a role.
     5. The schema should contain some identifiers made of multiple attributes, and at least one external identification for some entity.
     6. The schema should contain at least one optional attribute and at least one multi-valued attribute.
     7. There should be some external constraints, that cannot be represented in the ER model.
     8. The specification should include an indication about the volumes for the various entities and relationships (pay attention to the coherence between the volumes and the cardinality constraints of the ER schema).
     9. The specification should include a workload of the most common queries and operations (between 5 and 10) that are of interest in the modeled domain, with an indication of their frequency.
  6. The student should carry out the design of the database according to the requirements, following the methodology presented in the course, and consisting of the following phases:
     1. Conceptual design, producing the following documents:
        1. structured and organized requirements;
        2. glossary of terms (typically optional, but required for this project);
        3. diagram of the conceptual schema;
        4. data dictionary of the conceptual schema (listing the entities, relationships, and external constraints - the data dictionary for the attributes can be omitted);
        5. table of volumes and table of operations according to the foreseen application load.
     2. Restructuring of the conceptual schema, producing the restructured conceptual schema (diagram and data dictionary), the corresponding table of volumes, and the access tables to assess the cost of the various operations.
     3. Direct translation to the relational model, producing the relational schema with external constraints and the specification of the application load in terms of the relational schema.
     4. Restructuring of the relational schema taking into account the application load, producing the restructured relational schema with external constraints and the specification of the application load in terms of the restructured relational schema. The reasons for the restructuring steps on the relational schema should be stated explicitly, by referring to the operations and the corresponding access tables.
     5. Specification of the database in SQL, by defining relations with suitable constraints (capturing keys, foreign keys, and tuple constraints) and stored procedures with triggers to implement additional constraints (inclusions, external constraints).
  7. The student should also develop a simple application (typically in Java) that implements some interaction with the database via a textual or graphical user interface.
     The application should:
     • allow the user to answer the queries that are part of the workload (typically by instantiating some parameters with values provided as input);
     • allow the user to perform some basic insertions and/or updates of (some of) the data in the database, asking the user for input;
     • catch the exceptions that might be generated by JDBC due to possible mistakes in the interaction with the database, so that the application does not terminate prematurely with an error.
  8. The documentation produced for the project should include:
     1. a single pdf file containing a textual description of the requirements (of roughly a page) and the documents for phases 1-4 above.
        Remember to include at the beginning of the pdf file a header or a title page with your name, student number, the title of your project, and the date.
        Remember also to number the pages of the pdf file (the page numbers are important for the evaluation, so that we can refer to them for comments);
     2. one or more SQL files containing the specification of the database (phase 5 above);
     3. one or more files (typically in Java) containing the application that interacts with the database. The functionality of the application will be reviewed when the students discuss their project.
  9. All documents have to be bundled in a single ZIP file and have to be uploaded to MS Teams within the "Introduction to Databases Project" assignment.
  10. The deadline for submitting the project is, unless announced otherwise, at 23:59 two days before the day set for the discussion of the projects (see below).
• Rules for the Project Discussion
  1. The discussion of the IDB projects typically takes place one or two days before the date set for the written exam, and will be announced on MS Teams before each exam session.
  2. One or two days before the project discussion, we will post in MS Teams a schedule that assigns a specific time slot to the discussion of each project. Specifically, the discussion of the projects will be scheduled in the order in which they have been submitted to MS Teams (considering the last modification time), where projects submitted first will be discussed first. The discussion of each project will last between 15 and 30 minutes.
  3. In the case of a face-to-face discussion:
     • To ease the discussion, students may bring a printout of the following parts of the project documentation:
       • the requirements,
       • the conceptual schema (diagram and constraints),
       • the restructured conceptual schema (diagram and constraints),
       • the relational schema (with constraints) resulting from the direct translation,
       • the restuctured relational schema (with constraints).
       The remaining documentation can be consulted from the pdf file, and does not need to be printed out.
       It is preferred if the sheets of paper with the documentation above are not bound but are kept loose, since this facilitates the assessment of the correctness of the various design phases. To avoid confusion, please don't forget to number the pages.
     • Alternatively, we can also discuss the project by consulting on screen the pdf file that has been handed-in on Teams.
     • Students should also bring a laptop with a functioning version of the application they have developed for the project, so that we can verify its funtionality during the project discussion.
  4. In the case of an online discussion via MS Teams:
     • Students should be ready to share their screen on MS Teams in order to show the different parts of the project documentation:
       • the requirements,
       • the conceptual schema (diagram and constraints),
       • the restructured conceptual schema (diagram and constraints),
       • the relational schema (with constraints) resulting from the direct translation,
       • the restuctured relational schema (with constraints).
     • In order to discuss the various phases of the development of the database design, and illustrate how the output of one phase is used to generate the output of the next phase, it is convenient if the two outputs can be visualized at the same time on the screen. Therefore, for the purpose of the discussion, each part should be saved on a separate pdf file, so that two different parts can be visualized on the screen at the same time (e.g., the restructured ER schema and the relational schema resulting from the direct translation).
     • The laptop used to connect to MS Teams should contain a functioning version of the application they have developed for the project, so that we can verify its funtionality during the project discussion.

For Students who Have to Take the 8CFU Exam

For students enrolled in the old BSc in Computer Science and Engineering, who still have to take the 8 CFU Exam for the Database Systems course, the written exam will include also questions that cover the additional topics for 2 credit points of "Physical Data Storage" (covered in Chapter 6 of Database System Concepts) and of "Transaction Management", "Recovery", and "Multi-User Synchronization" (covered in Chapters 8-10 of Database System Concepts).

The reference textbook for Chapters 6 and 8-10 is:

Database System Concepts (4th edition). Silberschatz, Korth, Sudarshan. McGraw Hill, 2002.
Available at University Library Bozen: 13-General Collection (ST 271)

The material for Chapters 6 and 8-10 is covered at the proper level of detail necessary for the preparation of the exam also in the slides that Prof. Sven Helmer used when teaching the Database Systems course until Academic Year 2017/2018. These slides are not available anymore on the Web, but students who would like to receive an electronic copy can contact me on Teams.