Degree | Type | Year |
---|---|---|
2503758 Data Engineering | OB | 2 |
You can view this information at the end of this document.
It is recommended that the student have the knowledge and skills of:
In this subject, the basic concepts of Relational Databases (BDR) necessary for both BD and user designers are introduced.
KNOWLEDGE: At the end of the course the student must be able to:
ABILITIES: It is intended that students acquire the following abilities:
BLOCk 1. DATABASE PARADIGMS
1. Introduction. Basic Concepts (2 hours)
2. Architecture of Relational Databases (2 hours)
BLOCK 2. RELACIONAL MODEL
3. RElational Model Relacional: Data Structure and Integrity Rules (2 hours)
4. Relacional Model: Data Manipulation (6 hourss)
BLOCK 3. DATABASE DESIGN
5. Conceptual Design (8 hours)
6. Logical Design (2 hours)
7. Normalization (2 hours)
BLOCK 4. PHYSICAL LEVEL
8. Physical Level (2 hours)
Title | Hours | ECTS | Learning Outcomes |
---|---|---|---|
Type: Directed | |||
Explicación y resolución de problemas | 26 | 1.04 | 3, 4, 6, 7 |
Master classes | 26 | 1.04 | 1, 2, 5 |
Type: Supervised | |||
Technical Rapport Feedback | 2 | 0.08 | 4, 6, 7 |
Type: Autonomous | |||
Estudi individual | 26 | 1.04 | 1, 2, 5 |
Realització problemes SQL i disseny de BDR | 52 | 2.08 | 1, 2, 3, 4, 6 |
Technical Rapport | 8 | 0.32 | 4, 6, 7 |
LEARNING MANAGEMENT SYSTEM (LMS): Caronte (http://caronte.uab.cat, degree in Enginyeria de Dades, subject Bases de Dades Relacionals, course BDR Curs 2024-25).
The student's learning process will be based on these two types of classroom activities: Theory and Seminars and an autonomous work activity, the Technical Report. Attendance at theory classes, and seminars IS NOT COMPULSORY, BUT YOU ARE VERY RECOMMENDED.
THEORY
The theory classes are taught through magisterial classes with transparencies and slate. All the material of the course will be accessible through the LMS. Some of the theory sessions will be devoted to solve exercises in the same classroom with the aim of deepening the most relevant concepts and teaching the student to identify and analyze the typical errors.
SEMINARS
It consists of two parts. In the first part the SQL language will be introduced and to practice an SQL script is provided on a BDR with content and a statement with 120 queries that the student must solve. The resulting tables are provided so that the student can practice outside the classroom. In the seminar sessions, consultations are proposed to be solved, which thestudents do with the teacher's tutoring. An account is provided to the Oracle server of the Engineering School and the link to download the Oracle sqlDeveloper client software so that students can send their queries to the Oracle server of the School. In a more local way, the link is provided to download a reduced version of the Oracle (Oracle Express Edition) engine, to be able to be installed on a PC or laptop in a local modus.
In the second part of the course, a statement with design problems is disproportionate, some of them, at the teacher's proposal, students solve in class with their support.
All documentation (statements of SQL and design, BD scripts, results of problems) of seminars is available to the LMS.
TECHNICAL RAPPORT
An autonomous and cooperative work activity is proposed: case of use in the design of a real database.
In this activity a real case of design of BD will be presented to the student so that the student performs all the phases of design: capture and analysis of requirements, design E / R, logical design and game of SQL queries. This activity will be done in groups of 5 people that must be registered via LMS. The different stages of the technical report will be monitored throughout the course. There will be two deliverables evaluable in LMS: a first delivery of the design E / R with which to obtain the teacher's feed-back and final delivery at the end of the semester with all stages.
Cooperative work is carried out both in the design activity of a BD in which the student will have to work in a group of 5 people and in carrying out the problems proposed in the seminar sessions.
Annotation: Within the schedule set by the centre or degree programme, 15 minutes of one class will be reserved for students to evaluate their lecturers and their courses or modules through questionnaires.
Title | Weighting | Hours | ECTS | Learning Outcomes |
---|---|---|---|---|
SQL Exam | 25% | 2 | 0.08 | 3 |
Technical Rapport | 25% | 2 | 0.08 | 4, 6, 7 |
Theory Exams | 50% | 4 | 0.16 | 1, 2, 5 |
Voluntary exercise delivery | +1,0 | 2 | 0.08 | 2, 3, 6 |
The evaluation of the subject will be carried out continuously, based on three indicators: Theory, SQL and the Technical Report.
THEORY
There will be two individual written exams, with a weight of 50% each on the Theory Note. The first test (Par1) will be done approximately halfway through the semester and will evaluate the theoretical concepts explained up to date and the ability to solve BDR queries in relational algebra. The second test (Par2) will be carried out at the end of the semester and will evaluate the concepts explained until the time of theory (design of BD, normalization, physical level) and the ability to solve assumptions of design E/R and step to relational model.
Recovery test: In case the theory note does not reach the approved, students may submit to a review of recovery on the contents of the partial examination suspended.
Seminar classes offer two voluntary deliveries valued each with 0.5 points to add to the partial exam mark (Par1 or Par2). The first delivery consists of SQL query exercises where the student's abilities are evaluated in the resolution of SQL BDR queries (NPrb1). The second consists of a design exercise of BD, where based on some requirements, the most appropriate E/R diagram must be designed (NPrb2).
SQL EXAM
Individual examination by computer where the student's abilities are evaluated in the resolution of SQL queries. A series of random SQL queries are proposed on the BD used in the seminars that the student must solve in a given time (SQL Note).
Recovery Test: If the SQL exam is not reached on 5, the student has a new opportunity with the same format and rules
TECHNICAL RAPPORT
The Technical Report is an assessable group activity consisting of 4 parts, corresponding to the 4 design phases of a BDR: Requirements, E / R Diagram, Logical Design in tables and Implementation of a set of SQL queries. A written document that contains the work carried out in the 4 phases, duly justified, will be presented. The document must have the appropriate format so that the diagrams of the E / R Diagram and the corresponding Relational Diagram can be read correctly. The Technical Report Note will be obtained from two deliveries: The first one, with the writing of the data requirements of the presented case and the E / R Diagram, resulting from the design of the BD. The second installment will contain the same points of the first one including the teacher's corrections by adding the Relational Diagram (resulting from the logical design) and the code of the SQL queries and their results in tables. The note of the Technical Report will be the weighted average of the note obtained from the two deliveries: Design E / R (60% of the note) and the Logical Design with SQL queries (40%).
If a diagram of the Technical Report could not be read clearly for reasons of resolution or quality, this part of the report will be suspended, as well as the parts that depend on it as it can not be evaluated.
QUALICATION INDICATORS
The final grade of the subject is calculated in the following way (between square brackets the minimum marks to make half):
EVALUATION CRITERIA
EVALUATION CALENDAR:
The dates of continuous evaluation will be published in Caronte and may be subject to changes of programming for reasons of adaptation to possible incidents. Charon will always be informed about these changes as it is understood to be the usual platform for the exchange of information between teachers and students outside the classroom.
Notwithstanding other disciplinary measures deemed appropriate, and in accordance with the current academic regulations, irregularities committed by a student that may lead to a variation of the qualification will be classified by zero (0). Assessment activities qualified in this way and by this procedure will not be recoverable. If it is necessary to pass any of these assessment activities to pass the subject, the aquatic will be suspended directly, without opportunity to recover itin the same course. These irregularities include, among others:
With the exceptions that the "non-evaluable" qualification will be awarded to students who do not participate in any of the assessment activities, and that the numerical note of the file will be the lowest value between 3.0 and the average Weighted notes in case the student has committed irregularities in an evaluation act (and therefore not approved for compensation).
SUMMING UP:: copying, copying, or plagiarizing in any of the assessment activities is equivalent to a SUSPENS with a score of less than 3.5.
SUBJECT MATERIALS (docs, slides, papers): In the LMS.
BASIC BIBLIOGRAPHY:
COMPLEMENTARY BIBLIOGRAPHY:
WEB LINKS:
MULTIUSER RELATIONAL DATABASES:
All the software that will be used is free access or they are servers of the School to which the students enrolled in the subject will be given access.
Name | Group | Language | Semester | Turn |
---|---|---|---|---|
(PAUL) Classroom practices | 81 | Catalan | first semester | morning-mixed |
(PAUL) Classroom practices | 82 | Catalan | first semester | morning-mixed |