Higher Technician in Computer Network Systems Management

DATABASE MANAGEMENT
ORGANIZATION: Working in groups 1st CHALLENGE: Defining and Creating Databases.

Working-time
Duration: 15 hours 30’ Starting date:2024-10-09 / End date: 2025-03-14
Learning units: LU2-LU3-LU4-LU6

Aims / Learning Outcomes (related to OCD requirements).

RA1: Designs normalised logical models interpreting Entity/Relationship diagrams.

Learning Outcomes:

1. Identify the terminology of the Relational Model.

2. Identify the tables’ fields
3. Identify the relationships among tables.
4. Define the key fields.
5. Implement the integrity rules.
6. Identify and document the restrictions that couldn’t be translated into the logical design.

RA2: Performs the physical design of DBs using wizards, graphical tools and the data definition
language.

Learning Outcomes:

1. Create tables.
2. Choose the data type.
3. Define the tables’ key columns.
4. Apply all constraints arising from the logical design.
5. Use wizards and graphical environments.
6. Use languages to define data.

1. Challenge statement.
Estimated time:

A company usually handles a vast amount of data and wants to manage it in the best way
possible, and it has decided to hire 3 people in order to do this task.

As it is not so clear how to hire this working group, they have decided to organise a contest whose
name is “Define and create a Database” and your working group is taking part in this challenge.

Consequently, each group must develop only a database or schema and present it to the other
contestants.

1.-
2. Definition of the challenge.
2.1. Guidelines.
Estimated time:

1. Definition of the DB: each group member must define at least a DB which could be
interesting for the contest.

2. Selection of the DB: each group member must show their database and the group must
decide, among these three databases, which is going to be the database for the contest.

3. Making the queries: each group member must make at least 2 queries about what the final
user, or customers, wants to know, ask or retrieve from the database.

4. Selection of the queries: each group member must show their 2 queries, and the group
must select 4 queries among these 6.

5. Creation of the Relational Model: each group member must design the Relational
Model/Diagram of the selected DB or schema via MySQL Workbench. This model must
include at least the following:

o 8 tables of which one must be:

 a weak table.
 a hierarchy.

o 10 relationships of which

 2 must be1:N.
 2 must be N:M.
 a reflexive relationship.

o A multi-valued attribute.
o An optional attribute.

Apart from this you must do the following:

o Define the schema keys. In other words, the primary and foreign keys and their Referen-
tial Integrity (Cascade, Restrict, Set Null...).
o Every entity must have a minimum number of attributes depending on their nature, e.g.:
 A person: Name, surname, DNI, email, telephone, date of birth,…
 An office/company/shop: Name, address, city, postal code, email, telephone,…
 A product/item: Name, description, price, stock,…

o It is necessary to use the field type int, unsigned int, decimal, char, varchar, date, time,
boolean, enum, set...

6. Selection of the Relational Model: each group member must show its solution, and the
group must select the best one, or join the different solutions to create a new one.

7. Development of the physical design (DDL - Data Definition Language): each group
member must perform the physical design of the previously created database in MySQL
Server.

2.-
 8. Modification of the physical design: considering the statement and the defined E-R
model, each member should consider how to improve the physical design by applying the
following restrictions: UNIQUE, CHECK and DEFAULT.

9. Selection of the restrictions: it will be decided the more suitable UNIQUE, CHECK and
DEFAULT restrictions for the database among all group members.

10. Change the structure of a table or tables: check the created tables and modify, add and
delete those columns that are not correct.

11. Insertion of data: data will be inserted into the previously created tables. At least each
table must contain 5-6 records (rows or tuples).

12. Execution of the queries made in task 4: it should be shown that the questions raised in
section 4 can be executed in the DB designed.

It should be shown that they work correctly by a screenshot of the execution of the same on
the server. Besides, within those queries must be the following:
 Get the smallest or the highest value of an attribute.
 At least two tables are linked.
 Show some kind of statistical data.

13. Export the entire schema into a .sql file: the creation of tables, PKs and FKs and their
Referential Integrity, data and other must be included into the .sql file.

14. Migration to Oracle server: the DB created will be migrated from MySQL to Oracle.

15. A final document (pdf format): every group must create a unique document in which of all
the previous steps are explained.

2.2. Work planning.

Estimated time:
In order to develop this challenge students must do the following:

● Logical design – Relational Model: Look for information on

- Relational Model
- Table.
- Table’s column.
- Primary Key and Foreign Key. Referential integrity.
- Weak entityies depend on their dependence (identity or existence).
- 1:1 relationships.
- 1:N relationships.
- N:M relationshis.
- Specialization and Generalization: ISA relationships.
- Programs to design Relational Models.

● Physical design –Data Definition Language (DDL).

- Creation of DBs and other objects (indexes…).
- Creation of tables. Types of data or columns. Domains.
- Restrictions: avoid NULLs, unique values, primary keys.
- Validation restrictions.
- Modification and deletion of tables.

3.-
 ● DB migration: from MySQL Server to Oracle.

- Graphical display of the database schema: WorkBench and SQL Server

Management Studio.

● Communication with students.

● Communication with teachers.
● Documentation.

- Each group member will fulfil their project’s template.

- Each group must submit a single pdf document where it will be defined the
selected DB, the made queries, its Conceptual Design (E/R Model) and Logical
Model (Relational Model), Physical Design and the data.

Each group have its Drive folder where there are the documents to fulfil on the selected DB.
3. Achievements.
Estimated time:
Students achieve to implement a DB doing research and working in groups.

4. Working-time.
Estimated time:
Estimated
Task Time
Real End date

1. Definition of the DB. 15’

2. Selection of the DB. 15’

3. Making the queries. 30’

4. Selection of the queries 30’

5. Creation of the Relational Model. 4 h.

6. Selection of the Relational Model. 2 h.

7. Development of the physical design. 30’

8. Modification of the physical design. 30’

9. Selection of the restrictions. 30’

10. Change the structure of a table or tables. 1 h.

4.-
 11. Insertion of data. 2 h.

12. Execution of the queries made in task 4. 1 h.

13. Export the entire schema into a .sql file. 30’

14. Migration to Oracle server. 1h

15. A final document (pdf format). 1h

5. Assessment.
5.1. Guidelines.
Estimated time:

5.1 TECHNICAL COMPETENCES (70% of the project’s final mark)

The final document (70%) must show the following:

Group Task

1+2+3+4 Definition of the DB/schema + queries 10%

5+6 Relational Model. 30%

7 Development of the physical design. 5%

8 Modification of the physical design. 5%

9 Selection of the restrictions. 10%

10 Change the structure of a table or tables. 5%

11 Insertion of data. 10%

12 Execution of the queries made in task 4 10%

13 Export the entire schema into a .sql file. 5%

14 Migration to Oracle server. 10%

5.-
 5.2 TRANSVERSAL COMPETENCES (30% of the project’s final mark)

These are going to be assessed by the observation guide, self and peer assessment, the oral
presentation and the transversal section of the technical document (structure/format, suitable
description and spelling/grammar).

● Self and peer assessment – Individual mark (10%)

Each group member will evaluate himself or herself and the other members of his or her team.

List their names in the columns and assign a score of 0 (if they never meet the mentioned criteria),
1 (if partially meet) or 2 (if always meet) in the rows.

Students are asked to objectively analyse their performance, and reflect and be very honest when
assigning points. Please keep in mind that members of your group will receive only the total score.

Criteria Member 1: Member 2: Member 3:

In the project class hours she or he is dedicated

completely to it.

She/he takes an active part in group meetings.

She/he fulfils its part of the task within the time limits.

She/he executes its task with an optimal level of quality.

She/he proposes ideas to development the task.

She/he doesn’t impose its ideas on other group

members.

She/he meets the group agreements and rules.

Would you work with him or her again?

Considering the work done by the group, what is the

percentage of the same that has made by the partner
you are assessing? Remember that the sum of the
percentages of the members of the group must be
100%.

TOTAL

6.-
 ● Transversal requirements of the technical document – Group mark (10%)

Each section will be rated with 0 or 1. Every requirement must be 1 in order to pass this part.

Task Mark

Cover (identification of the challenge and team members). 0.5p.

Content index. 1p.

Page number. 0.5p.

Only a single design for the whole document. 1p.

Explanations of each section. 1p.

Without spelling and grammar mistakes. 0.5p.

5.3 FINAL MARK

Each group member will get the individual mark plus the group mark.

6. RETAKING

ATTENDANCE
It must meet 80% of attendance, that’s it the total amount of hours the project, otherwise it
will be considered FAIL.

CHALLENGE RETAKING:

● Group: If the group fail the challenge, they will have a new opportunity to review and submit
it before the end of the term. The challenge’s final mark will be its mark multiply by
70%. If they don’t meet the deadline, they will fail the procedural section.

- Technical Content: if the group fail this part, they should review it and correct all
errors remarked by the teacher.
- Requirements of the summited document: if the group fail this part, they should
review it and correct all errors remarked by the teacher.
- Oral presentation: the group will return to present and defend the project in a break
time on the date set by the teacher.

7.-
● If a group pass the challenge but not a member (individual): that team member will be
given a period of time to correct errors and study the group project that it will be defended
by him or her in a break time. The member must submit the corrected work before the end
of the 1stterm. If they don’t meet the deadline, they will fail the procedural section.

8.-