National Education Associates

This is the fifth of a multi-part case study for a company called National Education Associates. Part of your work over the course of the semester will be to design and build a database for this fictional company. Though fictitious, the narrative and issues discussed are very real for many companies. You must read these case studies carefully and thoroughly to fully understand their business and their needs. This is part of the requirement for building effective and efficient databases.
Case Study Part 5
It’s All Coming Together Nicely! In your previous assignment you created your database using SSMS. Now, you may have had to change your design once you started implementing the tables and the relationships, and that’s ok. Read that again—changes are OK! The process of developing a database is always an incremental one and subject to many revisions before your design goes into production.
One of the things that you need to remember is that when you encounter resistance (SSMS won’t let you do what you are trying to do, creating relationships is a struggle, etc.) this is a sign that you need to step back and think through your design decisions. Often, resistance is a sign that there might be issues with the design you are attempting to implement.
In several follow up meetings you wanted to know what the most important components of this new system are to the company and to its customers. As you learn more about the most important components you also learn about some elements that might be missing from your design. Here are your findings:
Most Important Components of New Database System
Students
You recognize that your design must include a ‘Students’ table. It doesn’t have to be named that, but the purpose is to record information about every student attending a specific institution.
You also just learned that buried in someone’s notes that they forgot to give to you that there is a general concensus by many of the NEA’s client’s that they would like to begin rolling in a note-taking component so that any administrator’s interactions with a particular student is recorded.
This feature must be linked to the students table by the student id column, and must–at a minimum–include the following columns or attributes:
Date and Time of the interaction with the student.
Notes field allowing unlimited number of characters to record the interaction.
The name of the person who interacted with the student.
Often, this feature will be used by advisors who meet with students to provide advice regarding classes, scheduling, financial aid, etc. But it could also be used by coordinators in departments, or by IT staff who help or assist a student, etc.
Grades

  1. Place this order or similar order and get an amazing discount. USE Discount code “GET20” for 20% discount