In this practice lecture, there are two sets of questions. The first set is a spreadsheet on students living in dormitories with some sample data that was collected. It is important to note, in real situations, this limited number of rows would not be enough to spot all the anomalies. In fact, hundreds of records are usually analyzed, as well as a number of user interviews. So to get a better handle on not only the data, but the requirements of the proposed database. In this set three questions I posed.

As mentioned earlier, it is imperative we understand the concepts, concepts and terminology of databases. Many students would agree initially that this unfamiliar terminology is imposing, but as mentioned in the previous lecture, before long, you will be talking like a database geek. Keep your answers for the next session, where solutions are provided. Second set is a typical CRM or customer relationship management system, that is interactions with customers and potential buyers. CRM systems aid companies in making better connections with their customers streamline internal processes, and improve profitability. In our example, we have six rows of information to consider.

The steps in creating a database is always the same, it must start by identifying any repeating groups of data. Assume in this example, that the customer name is unique. However, in a live situation, never make assumptions until you have checked with the user. Here again, we are presented a spreadsheet and asked to analyze the data. There are many ways to collect data including an input form, output reports, user interviews, focus groups, The questions are one, create an E ID to satisfy the third NF requirements. Three, identify the functional dependencies for identify after the EOD, the next step in the process.

Keep your answers for the next session where solutions are provided.