Review the scenario below, then answer the questions which follow, using the UML diagram below.

Employee class in package employee with private fields name:String, employeeId:int, hourlyRate:double and methods Employee(string,int, double), getName():String, getEmployeeId():int, getHourlyRate():double,weeklyPay():double,equals(Object):boolean with two child classes PartTimeEmployee class with private field hours:int and methods PartTimeEmployee(String,int,double,int), getHoursWorked():int,weeklyPay():double and ExternalContractor class with methods ExternalContractor(String,int,double), getHourlyRate(char):double,weeklyPay(int,char):double

This UML may represent the partial design for an Employee Management System (sometimes referred to as an Employee Information System or Human Resources Information System) for a business or organization.
Such systems are often used to support tracking and managing of employee information and related process.
This may including recruitment and applicant tracking, payroll administration, vacation and benefits administration, time and attendance management, training, and performance management.
An Employee Management System would need the ability to track and manage many different instances of the Employee objects (as well as many instances of Employee subclasses, such as ExternalContractor, PartTimeEmployee).

To accommodate this requirement the design should be amended to include:

An appropriate data structure (or structures) for organizing, processing, retrieving and storing Employee data
  • Nothing else is needed, the design is perfect as is!

There are no hints for this question