Murdoch University

• ICT 581

• Table of Contents Q1. NORMALISATION..................................................................................................................................................... 2 a. Problems with the existing design in terms of the potential modification anomalies that it might exhibit............................................................................................................................................................ 2 b. Explanation of candidate key(s) and its normal form in current relation..................................3 c. Conversion of relation from 1NF to 2NF and finally 3NF in detail.................................................4 d. Addressing the problems identified in (a) with our new design, preserving all the information in the original design...................................................................................................................5 Q2. CONCEPTUAL DESIGN........................................................................................................................................... 6 Legend........................................................................................................................................................................ 7 ER diagram................................................................................................................................................................ 8 REFLECTION...................................................................................................................................................................... 9 Q1. NORMALISATION a. Problems with the existing design in terms of the potential modification anomalies that it might exhibit. Data Redundancy is one of the significant issues with the current design of 'Grand Slam.' There seems to be much information in the single database table, making it difficult for the users. The table contains all the data relevant to the 'Grand Slam' tennis competitions and the game-winners for the past few years. When the same data is entered into the system repeatedly and excessively, redundancy arises. The table contains repetitive information and evidence attributes such as Location, Venue, and Surface, making a design very poor in this given design. When the database is updated regularly, they must replicate the whole data location for each tournament, resulting in data inconsistencies. For example, whenever a wrong location is recorded and stored, it needs to be reformed and then any redundant data must be updated. However, if they overlook even a single piece of data, the database will become inconsistent. Furthermore, it expands the database capacity and requires a long time, slowing down database processes. There is a risk of data replication and a possibility of loading numerous similar copies of identical data. Data such as location and surface could be extracted and placed within venue attributes inside the provided database table, even without a different location and surface attribute. In the given database table, data is stored separately, which results in database redundancy. The relation in this database table has duplicate data records, which creates inconsistencies where data needs to be changed because it is a worthless design and includes insufficient data.