Relational Data Model Issues - Assignment Example

M stands for “many”, m stands for “mandatory”, and o stands for “optional”.

Table Elector has a foreign key to the electorate this elector belongs to, to party this elector gives vote and to candidate this elector gives vote.

Table Party has a foreign key to its leader, a candidate who leads this party.

Table Candidate has a foreign key to the electorate this candidate is listed in, and to the party to which this candidate belongs to.

The first normal form (1NF) sets the very basic rules for an organized database:
- Eliminate duplicative columns from the same table.
- Create separate tables for each group of related data and identify each row with a unique column or set of columns (the primary key) (Chapple, 2005).

So, the field name (first, middle, last) should be replaced by a group of three fields: First_name, Middle_name, and Last_name.

The primary keys for each table are already identified.

There are no duplicate columns in the same table.

Here are tables of the relational database schema for the 1NF.

The second normal form (2NF) further addresses the concept of removing duplicative data:
- Meet all the requirements of the first normal form.
- Remove subsets of data that apply to multiple rows of a table and place them in separate tables.
- Create relationships between these new tables and their predecessors through the use of foreign keys (Chapple, 2005).

So, personal information, such as name (first, middle, last), address, gender, and date of birth can be taken apart into separate table Person. It also should have a primary key named Pk_id. Then tables Elector and Candidate should refer to it via secondary (foreign) key Fk_person.