levo

Databases, Normalisation and Entity Modelling

  • 8 subtopics
  • 24 things to know
  • Component 2

What Databases, Normalisation and Entity Modelling covers

Databases, Normalisation and Entity Modelling is examined in Component 2, Computer Architecture, Data, Communication and Applications. It covers data consistency, redundancy and independence, relational databases and other database models, primary keys, foreign keys and indexes, first normal form, second normal form, third normal form, entity relationship modelling and user views and turning data into information.

Where it is assessed

Component 2

Computer Architecture, Data, Communication and Applications.

Check the Eduqas specification ↗

The 8 subtopics

Each one has its own page.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Key term

What is an index, and what does having one cost?

Key term

Define an entity and an attribute, with an example of each.

Key term

Define data redundancy.

Key term

What is a relational database?

Key term

What does normalisation aim to achieve?

Key term

State the rule for second normal form.

Key term

State the rule for third normal form.

Key term

What is a user view of a database?

Key term

Define data consistency.

Key term

Define the terms relation, tuple and attribute.

Key term

What is a primary key?

Key term

What is an unnormalised table?

Key term

What is a partial dependency?

Key term

What is a transitive dependency?

Key term

What is an entity?

Evaluation

Give two advantages of different users having different views.

Key term

Define data independence.

Key term

Give three benefits of a relational database.

Key term

What is a foreign key?

Key term

State the rule for first normal form.

Key term

Why can a table with a single-attribute primary key never break second normal form?

Key term

Identify the transitive dependency in COURSE(CourseCode, CourseTitle, TeacherID, TeacherName).

Key term

What is an attribute of an entity?

Key term

How does a view improve security in a hospital database?

Take Databases, Normalisation and Entity Modelling further

The same content, four other ways.

Commonly confused

Pairs that lose marks when they are blurred together.

  • Partial dependency vs Transitive dependency

    Partial dependency: resting on part of a composite key and breaking second normal form. Transitive dependency: resting on another non-key attribute and breaking third normal form.

  • Primary key vs Foreign key

    Primary key: identifying rows in its own table. Foreign key: pointing at that identifier in a different table.

  • Index vs Primary key

    Index: a separate lookup structure that speeds up searching on a field. Primary key: a uniqueness rule on the stored values.

Questions from this topic

Each one with the model answer underneath.

  1. 1

    Define data redundancy.

    Model answer

    Data redundancy is the unnecessary storage of the same data item in more than one place. A customer address repeated in three tables is redundant.

  2. 2

    Define data consistency.

    Model answer

    Data consistency means every copy of a data item holds the same value throughout the system. A database is inconsistent if one table shows an old address and another shows the new one.

  3. 3

    Define data independence.

    Model answer

    Data independence means the stored data and the programs that use it are kept separate. The physical storage can change without any application program being rewritten.

  4. 4

    Why does redundancy threaten consistency?

    Model answer

    An update must reach every copy of the repeated item to keep them all in step. A single missed copy leaves the database holding two different values for the same fact.

  5. 5

    Give one situation where controlled redundancy is deliberately accepted.

    Model answer

    A foreign key repeats a key value in another table, which is necessary to link them. Some systems also duplicate data across sites to speed up reading.

  6. 6

    What is an update anomaly?

    Model answer

    An update anomaly occurs when a change has to be made in many rows and one row is missed. The table then holds contradictory versions of the same fact.

What is inside Levo

Six ways to work the same material.

1Closed book
2Open book
3Closed book

The 3-step method, run for you

Answer cold, learn it, then prove it stuck. Levo tracks the jump between your first attempt and your last.

Data Structures: Arrays, Records and Hash Tables
Stacks, Queues, Linked Lists and Trees
Boolean Logic and Simplification
Algorithms, Pseudo-Code and Programming Constructs

Cram a whole paper in one sitting

Sort every topic into what you know and what you do not, then drill only the weak ones.

KDW to HAT.
decryptsencryptscompresses

Blank Blitz makes facts automatic

Rapid timed gap-fills on the terms and numbers you need to recall without thinking.

AThe two are not the same.
BOpen source refers to the availability of the code.
CMuch open source software is free of charge.

Build It gets the exam shape right

Assemble a full-mark answer from its marking points, in the order an examiner wants them.

Backup means the copy of the data.
TrueFalse

Test It catches misconceptions

Spot the fault in a statement. The traps are the mistakes students actually make.

721941163128510

Brain Breaks between sessions

Short focus games to reset attention, so the next set lands better than the last.

Databases, Normalisation and Entity Modelling revision questions

What does Databases, Normalisation and Entity Modelling cover in Eduqas A-Level Computer Science?
8 subtopics: data consistency, redundancy and independence, relational databases and other database models, primary keys, foreign keys and indexes, first normal form, second normal form, third normal form, entity relationship modelling and user views and turning data into information. Each one has its own page with questions and model answers.
How is Databases, Normalisation and Entity Modelling organised?
By the Eduqas A500QS specification, subtopic by subtopic, so it matches the order you are taught it in.

Every question in Databases, Normalisation and Entity Modelling, on a schedule.

Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.

Or £46 a year, about £3.83 a month. Cancel anytime.