Unit 18 (P2): Designing a Relational Database

This database is for an IT Support company who helps their clients with IT related issues. The database will need a ticket system where the client can make a ticket on the problem that they have which is assigned to an employee to solve.

Relationships

Design a relational database for a specified user need (P2)

This relationship represents the connection between the tables. The ClientCompanyT has a one-to-one relationship with the client as each company is related to each individual client. The client can submit many tickets to our IT Support ticket system which is why ClientT has a one-to-many relationship with TicketT. There can only be one department code upon the many codes which can link to many different employees as each employee in the IT Support Company specialises in one department. For example, one employee might specialise in Internet Issues and if the client submits a ticket that has the department code related to internet issues, than that employee will be assigned to complete the ticket. Having said that, each individual employee has a one-to-many relationship with TicketT as the employee can be assigned to multiple tickets. Also, there only can be one department that a ticket is linked to so this means that it has to be a one-to-one relationship.


Tables

I will have five tables in my relational database which are the following:


ClientT


ClientCompanyT


EmployeeT


DepartmentT


TicketT

Data Entry Forms

These are the layouts of the forms that I will create in the database for each table so that users can easily add, delete and save records without tampering with the database itself.


ClientT

ClientCompanyT

EmployeeT

DepartmenT

TicketT


Design Documentation

Data Flow Diagram


Entity Relationship Diagram


0 views
  • White LinkedIn Icon
  • White Twitter Icon
  • YouTube
  • White Discord Icon

Privacy Policy

 © 2020 Jack Young (SirHandsomeJack). All rights reserved.