Tribunal titular

Cargo

Departamento

Profesor

Presidente

ING.ELECTR.DE SIST. Y AUTOMATI

RIESCO PELAEZ , FELIX

Secretario

ING.ELECTR.DE SIST. Y AUTOMATI

BLAZQUEZ QUINTANA , LUIS FELIPE

Vocal

ING.ELECTR.DE SIST. Y AUTOMATI

FUERTES MARTINEZ , JUAN JOSE

Tribunal suplente

Cargo

Departamento

Profesor

Presidente

ING.ELECTR.DE SIST. Y AUTOMATI

ALAIZ RODRIGUEZ , ROCIO

Secretario

ING.ELECTR.DE SIST. Y AUTOMATI

DIEZ DIEZ , ANGELA

Vocal

ING.ELECTR.DE SIST. Y AUTOMATI

MORAN ALVAREZ , ANTONIO

To pass the course on the first call, the student must obtain an average of 5 out of 10 points, taking into account the marks obtained in all the tests you have taken.

In addition, it is necessary to pass both (1) the Entity-Relationship and Relational diagrams exam, and (2) the project of the course obtaining 50% of the maximum mark in these exams, and also to obtain at least 35% of the mark in the exams of the other two parts of the course.

To pass the course in the second call, it is necessary to obtain an average of at least 5 out of 10 points, taking into account all the exams.
In addition, it is necessary to pass both (1) the Entity-Relationship and Relational Diagrams exam and (2) the course project, and to achieve at least 35% of the mark in the SQL exam.

Even if the average grade is higher than 5 out of 10 (or the established pass mark), the student will not pass if the above conditions are not met.
Students who do not pass an evaluation assessment during the continuous evaluation may sit for the recovery of this assessment in the first ordinary call.
Students who do not pass the course in the first ordinary call may sit for the parts that were not passed during the second ordinary call
In both the first and second calls, if a student does not present the PRACTICAL WORK on the established date, he/she will be able to present it later, within the corresponding call, but he/she will be penalized on the grade obtained. Each of the late submissions will also be penalized.

Code
A18104
A18105
A18121
B5618
B5619
B5626
B5627
B5628
C2	CMECES2 That students know how to apply their knowledge to their work or vocation in a professional manner and possess the skills that are usually demonstrated through the development and defense of arguments and the resolution of problems within their area of study.
C4	CMECES4 That students can transmit information, ideas, problems and solutions to both a specialised and non-specialised audience

	Competences
To understand and be able to use basic concepts related to databases. To be able to create an Entity-Relationship diagram from a database description problem and later to be able to translate it into a Relational diagram. To be able to implement a database using a graphical user interface. To understand and to use the primary SQL(Structured Query Language) sentences. To implement a database using SQL. To recover information from a database using SQL queries. To know and to understand the indexation concepts and to know how to apply them in a database implementation. To understand and to know how to use transactions, locks and concurrency concepts.	A18104 A18121	B5618 B5619 B5626	C2
	A18104 A18105 A18121	B5618 B5619 B5626 B5627 B5628	C2 C4
	A18104 A18121	B5618 B5619 B5626 B5627 B5628	C4
	A18104 A18105 A18121	B5618 B5619 B5626 B5627	C2 C4
	A18104 A18105 A18121	B5618 B5626	C2 C4

Topic	Sub-topic
Block I. CONCEPTS	Lesson I: BASIC CONCEPTS Interest of database management systems. Data vision. Data models. Database languages. Transaction management Users. General structure of the system. Lesson I: ENTITY-RELATIONSHIP MODEL Basic concepts. Design. Constrains. Keys. ER diagram. Weak entities set. Entity-relationship diagram. Lesson III: EXTENDED ENTITY-RELATIONSHIP MODEL Extended features. EER transformation to Relational. Restrictions. The student's problem. Lesson IV: STANDARDIZATION. Flat tables. Normal Forms. Advantages and disadvantages. Denormalization.
Block II. STRUCTURED QUERY LANGUAGE (SQL)	Lesson V: SQL Tools. Select. Where. Columns and functions. Aggregates. Totals and subtotals. Joins. Subqueries. Inserting and creating data. Stored Procedures. Triggers.
Block III. CONCURRENCY AND INDEXES	Lesson VI: INDEXES Introduction. Ordered indexes. Hashing functions. Lesson VII. TRANSACTIONS Introduction. Transactions. Transactions recovering. Lesson VIII. CONCURRENCY CONTROL Concurrency problems. Locks. Dead locks. Seriability.
Block IV. LABs	The practical sessions will take place in the F3 Lab using Microsoft SQL Server and Oracle DBMSs a) Using the graphical interface in SQL Server: Database design. Database implementation. Tables, index, views and constraints creation. b) Using SQL command line: (Both using M. SQL Server and Oracle) Database creation. Tables, indexes and views creation. Queries. Stored procedures and triggers

Methodologies :: Tests
	Class hours	Hours outside the classroom	Total hours
Laboratory practicals	22	33	55

Problem solving, classroom exercises	10	15	25
Personal tuition	2	3	5

Lecture	22	33	55

Mixed tests	10	0	10

(*)The information in the planning table is for guidance only and does not take into account the heterogeneity of the students.

	Description
Laboratory practicals	Will take place in the lab F3, using a computer in most cases for implementing and querying databases
Problem solving, classroom exercises	The instructor will resolve a set of problems during the lectures, interacting with the students for answering doubts and to clarify questions.
Personal tuition	Students attention will take place on person and on-line. The student will ask for an appointment using a specific agora forum prepared for this fact.
Lecture	Will take place in the classroom using slides and the blackboard.

	Description	Qualification
Laboratory practicals	It will be a exam to evaluate the learned concepts of SQL. To pass the course it is necessary to obtain at least 3.5 points out of 10 in the SQL exam. It will be necessary to submit the solutions for some practical sessions using a specific task in Agora.	15%
Lecture	The student will take a test to assess some of the theoretical concepts explained during the lectures related to basic databases concepts and also about indexes, concurrence and transactions.	10%
Problem solving, classroom exercises	The student will need to pass a test with two problems: a Entity-Relationship diagram and later a Relacional diagram created from a text proposed by the teacher. To pass the course it is mandatory to pass this part obtaining at least half the maximum grade.	50%
Others	All the students will carried out a practical project in groups of three. This project will have several deliverables with fixed dates. No presentation of one deliverable will means a 20% of penalty in the final grade of the project.	25%

Other comments and second call
To pass the course on the first call, the student must obtain an average of 5 out of 10 points, taking into account the marks obtained in all the tests you have taken. In addition, it is necessary to pass both (1) the Entity-Relationship and Relational diagrams exam, and (2) the project of the course obtaining 50% of the maximum mark in these exams, and also to obtain at least 35% of the mark in the exams of the other two parts of the course. To pass the course in the second call, it is necessary to obtain an average of at least 5 out of 10 points, taking into account all the exams. In addition, it is necessary to pass both (1) the Entity-Relationship and Relational Diagrams exam and (2) the course project, and to achieve at least 35% of the mark in the SQL exam. Even if the average grade is higher than 5 out of 10 (or the established pass mark), the student will not pass if the above conditions are not met. Students who do not pass an evaluation assessment during the continuous evaluation may sit for the recovery of this assessment in the first ordinary call. Students who do not pass the course in the first ordinary call may sit for the parts that were not passed during the second ordinary call In both the first and second calls, if a student does not present the PRACTICAL WORK on the established date, he/she will be able to present it later, within the corresponding call, but he/she will be penalized on the grade obtained. Each of the late submissions will also be penalized.

Basic
	D. Kronenke, D. Auer, S. Vandenberg, R. Yoder (2019). Database Concepts. 9th Edition, Pearson. C.J. Date (2019). Database Design and Relational Theory: Normal Forms and All That Jazz. 2nd edition, Apress Silberschatz, A. Korth, H.F. y Sudarshan, S. (2010). Database System Concepts, 6th edition, McGraw Hil. Alegre, E., Fernández, R.A. y Sánchez, L. (2003). Fundamentos y Prácticas de Bases de Datos. Secretariado de Publicaciones y Medios Audiovisuales de la Universidad de León. Silberschatz, A. Korth, H.F. y Sudarshan, S. (2006). Fundamentos de bases de datos, 5ª edición, McGraw Hil.
Complementary
	Date, C. J. (1999). An Introduction to Database Systems. Prentice-Hall. Elmasri, RA & Navathe S., (2003). Fundamentals of Database Systems (4th Edition). Addison Wesley Gary W. Hansen y J.V. Hansen (1997). Diseño y Administración de Bases de Datos, 2ª edición, Prentice Hall. de Miguel, A. y Piattini, M. (1997). Fundamentos y modelos de Bases de Datos, RA-MA. Beynon-Davies P. (2000). Database Systems, 2th edition, Macmillan Press Ltd.