COIT 20247 Term 1 “Database Design and Development” Assessment 1

Data Dictionary

  1. Client
Column NameData TypeSizeMinimum ValueMaximum ValuePrimary keyRequiredDescription
ClientIDInt1019999YYName of the client
ClientAddressVarchar30  NYAddress of the client
ClientNumberInt101 NYPhone number of client.
ClientEmailVarchar30  NYEmail id of client
DateOfBirthDate30  NYDate of client is recorded
  • Invoice
Column NameData TypeSizeMinimum ValueMaximum ValuePrimary keyRequiredDescription
InvoiceIDInt10  YYInvoice id is recorded.
InvoiceDateDate30  NYDate when the payment is made
InvoiceAmountVarchar30  NYPayment made by the client is recorded.
  • Employee
Column NameData TypeSizeMinimum ValueMaximum ValuePrimary keyRequiredDescription
EmployeeIDInt101500YesYEmployee who recorded the date must be recorded.
EmpNameChar30  NYName of the employee must be recorded.
EmpContactInt30  NNPhone number of employee.
EmpAddressVarchar30  NNAddress of employee
  • Branch
Column NameData TypeSizeMinimum ValueMaximum ValuePrimary keyRequiredDescription
BranchIDInt101 YYBranch id must be specified properly.
BranchNameChar30  NYThe name of the branch is specified
BranchAddressVarchar25  NNThe address of the branch is specified.
  •  Repair
Column NameData TypeSizeMinimum ValueMaximum ValuePrimaryRequiredDescription
RepairIDInt101 YYRepairID must be specified
BranchIDInt101 N (Foreign key)  YBranchID must be specified
ProblemChar50  NNThe problem of the customer must be noted properly.
CompletedChar50  NNWhether the installation is 40 percent complete or fully done.
  • Installation
Column NameData TypeSizeMinimum ValueMaximum ValuePrimaryRequiredDescription
InstallationIDInt1019999YYInstallation id must be provided.
HomePremisesChar25  NYHome address must be specified.
Investment UnitChar25  NYInvestment unit must be specified.
HousesChar25  NYInstallation might also be done on houses.
OfficesChar25  NYWhether he installation is t be done on offices must be specified.
  • WallMounted
Column NameData TypeSizeMinimum ValueMaximum ValuePrimaryRequiredDescription
InstallationIDInt10  N (Foreign Key)YInstallation id must be allocated
ModelVarchar15  NNModel must be defined
MakeYearVarchar15  NNThe make year must be written.
  • Ducted
Column NameData TypeSizeMinimum ValueMaximum ValuePrimaryRequiredDescription
InstallationIDInt101 N (Foreign Key)YInstallationID must be specified.
AirFilterChar10  NYAir filter if ducted should be written.
MotorizedVentChar10  NYMotorized vent if installed should be written.
  • Window Mounted
Column NameData TypeSizeMinimum ValueMaximum ValuePrimaryRequiredDescription
InstallationIDInt10  N (Foreign Key)YInstallationID of the product must be written
ModelVarchar15  NNThe model number of the product.
MakeYearVarchar15  NNThe make year of the product.

Business Rules

  1. Service allowed are installation and repair.
  2. Payment allowed are of two types i) advance and ii) remaining payment.
  3. The DateOfBirth of the person must be lesser than the system date or less than current date.
  4. CQAC collects personal details such as name, pho
  5. ne, and contact phone, DateOfBirth email-phone and address details.
  6. CQAC employee inspect the premises and provide installation option to the customer.
  7. The installation option is ducted, wall mounted and window mounted air conditioning.
  8. When the installation option is finalized a purchase, order is generated by them an a copy is generated by them and a copy is given to the customer.
  9. 40 percent of the total cost is calculated as advanced payment from customers. 
  10. After installing the air-conditioning units CQAC performs inspection and the remaining cost is collected.
  11. When CQAC receives a repair request from their customer, details are related to the problem and a possible date for a repair visit is informed to them.

Assumptions and Cardinality

  1. There are only three types of Installation (Supertype), WallMounted (Sub type), Ducted (Sub type) and window Installation (Subtype)
  2. Many customers invoice can be made by many customers so there exists man to many relationships, so we put a associative entity invoice/client.
  3. A branch can have many employee so there is 1 to many relationships among the entity.
  4. A branch can have many repair histories so there is 1 to many relationships.
  5. A branch can have many clients so there exits 1 to many relationships.
  6. A branch can have many installations so there exists ne to many relationships.
  7. Since, branch is dependent on many entities it acts as a weak entity.
  8. An invoice can be made through a single employee so there exists 1:1 reationship.