Unit 11 - Databases and Software Development Flashcards
Define entity
A category of object, person, event or thing of interest about which data needs to be recorded
Define attribute
A component of an entity
Define primary key
An identifier for a specific record
Define composite primary key
An identifier for a specific record that requires two or more attributes to uniquely identify it
What are the three types of relationships that entities can have with each other?
- One-to-one
- One-to-many
- Many-to-many
What two relationships are not used in databases?
One-to-one and many-to-many
Define foreign key
An attribute that is made to join two tables
Why aren’t many-to-many and one-to-one relationships used within databases?
One-to-one relationships are not used because they are redundant
Many-to-many relationships are not used because they will screw up the database causing problems with data redundancy, data insertion, deletion and updating which means that using them would make the system impossible to operate or navigate
Define relationship
A link between two entities
Define relation
A visual representation of entities within a database
Define field
An item of data
Define record
A row of data within a relationship
How is a relation organised?
A relation contains information about a single topic and is the entity with rows holding records relating to specific sections of information and each field in a row representing an attribute
Define a flat file
When all of the data is held in one table so there are no relationships and only one entity (therefore it is often just information about one entity)
Define normalisation
A process which enables programmers to come up with the best possible design for a database by reducing data duplication and improving data integrity
Describe first normal form
All of the attributes are atomic and there are no repeating attributes or groups of attribute
Describe second normal form
There are no partial dependencies within the relation which is acheived by using a composite primary key and ensuring that all of the attributes are dependent on all parts of the composite key (this means if you change the key or part of the key you change every attribute in that entity)
Describe third normal form
There are no non-key dependencies which means that there are no non-key dependencies (meaning that one non-key attribute changes and nothing else should change)