This document outlines three tables containing student, course, and payment information for a college. The student table includes details like name, ID number, contact info, and address. The course table lists course codes, names, teachers, formats, and hours. The payment table shows the amount due and total payment for each student based on their enrolled courses. Linking these tables together through primary and foreign keys would reduce redundancy and make it easier to query specific information as needed, such as a student's schedule or balance.

1. Abdullah Alqahtani<br />Case study 2<br />Student information and payment <br />Table 1 <br />StudentStudentIDFirst NameLast NameDOBcontactAddress1JamesBond01/07/1979(613) 225-23452301 Kelly st, Ottawa. ON K2H 6H52DanLore12/10/1982(613) 334-2130209 Baseline st, Ottawa. ON K1G 8V73KimJohns23/09/1980(613) 304-88763210 carling, Quebec. QB B2C 4Y64WillMcarty30/12/1978(613) 904-6654412 Orleans, Montreal. QB C2H 4J65KarimAl qahtani10/08/1984(613) 137-3333432 Park, Vancouver. BC T3H 0V8<br /> <br />Creating a pool of students that we will look for their courses and amount due, the first table includes all the information needed, while can be expanded if needed. The second table is for courses that might be taken by any students in Algonquin College, both tables will help us to determine the student information and what course he is taking, furthermore, the second table can let us know if the course is an online or Hybrid version, how many hours in total, and what professor is giving this course. <br />The third table is showing us what amount is due from each student, when paying tuition, some students use deferment payment to be able to pay the whole amount, therefore, the college will need to track this payment, any duplicate of names or an error will cause lot of trouble for the college. Also linking the tables is another hard thing without the use of a program, the redundancy will be huge since each student may be enrolled more than one course (most cases is 6 courses) therefore we have to repeat the student name more 4 times to include which course he is taking, and what amount is due from each course <br />Table 2<br />Course table<br />Course TableCourse CodeCourse nameTeacherRoomCourse TypeTotal Hours1Accounting Bill Arthur WB 110Hybrid602TechnologyTyler McGyllWT366Online453EconomyOmer SherWP 214Hybrid454QuantitativeCynthia PowelWP 210Hybrid605MarketingMary Hamilton WT 211Online90<br />Table 3 <br />Payment table <br />Payment TableStudentIDLast nameFirst nameCourse CodePayment dueTotal payment1JamesBond1$450.00$1,500.002DanLore2$350.00$1,500.003KimJohns3$350.00$3,000.004WillMcarty4$0.00$3,000.005KarimAl qahtani5$100.00$6,000.00<br />The best solution to reduce these repetition and redundancy is to create all the tables in an Access (2007) and try to make a good link between them, using a primary key (student ID) and a foreign key course code, these links are called Relationship and to make my search very easy without pooling up all the information that I might not need I will create Queries in separate tables (automatically) that will show me only what I need. <br />