Skip to content

Database Management

jfoot edited this page Oct 29, 2017 · 1 revision

Database Management

As previously stated, Transformations™ uses a Microsoft Access® Database, the application was designed with the intent that the end user should never need to directly access the database themselves or use any SQL commands. However, in extreme circumstances an IT administrator may wish to perform custom queries on the database. In this instance, a basic understanding of Access® is assumed. Below details the structuring of the database to help aid manual database manipulation. Top1

The fundamental cardinality of the database, is 5 tables: Teachers, Class, Users, ExamResults and Exams. Which are connected in one to many relationships as shown by the crowfoot notation.

  • Teachers: The teachers table is used to store all the teacher accounts.

  • Class: The class table is used to store all the classes created.

  • Users: The users table is used to store all the student accounts.

  • ExamResults: This table is used to store all the results from a student exam.

  • Exams: This table is used to state an exams characteristic; preventing the need for repeated data.

Advanced Database Topology

Below is an additional more detailed UML entity relationship diagram, detailing the fields of each table, and how each field is connected as either a primary or a secondary key. Field names are designed to be self-explanatory and the starting database will contain example data to help demonstrate a fields usage. top2

Using the diagram above, you should have an understanding of the overall database structure and design. Using this you can start querying the database, simply load up the Access® database and query it using your own methods/ knowledge.

Clone this wiki locally