Computer Science

Question

Draw a class hierarchy diagram for the following scenario. Indicate which class is the super class, and which classes are the extended child classes. Indicate in which classes you would locate each data field and method. You may draw the diagram on paper and take a photo of it to upload, or you may use software such as MS Word or Visio, or a tool of your choice.

A major league baseball team is implementing a Human Resources Payroll System.

The team has the following categories of employees:

1. full-time
2. part-time
3. volunteers
4. athletes
5. staff
6. executives
7. contractors

Data fields include:

1. SSN number
2. first name
3. last name
4. home address
5. hire date
6. rehire date
7. termination date
8. employment status (active / inactive)
9. batting average
10. team history

Methods include:

1. Output team history (other teams the athletes have played for)
2. Display personal info
3. Process salaried payroll
4. Process part-time payroll

Be sure to determine the best classes into which to locate the various data fields and methods.

Answer 1

I would start by identifying what belongs where to see what makes sense for a superclass for subclasses to inherit from. Here's one way to work that out in a table with categories of employees and fields and methods, making some assumptions about how staff, contractors, and volunteers fit in (sorry the table got cut off in the display because of Wyzant's width limit):

__________________________ full-time | part-time | volunteers | athletes | staff | executives | contractors

SSN number | √ √ X √ √ √ √

first name | √ √ √ √ √ √ √

last name | √ √ √ √ √ √ √

home address | √ √ X √ √ √ √

hire date | √ √ X √ √ √ √

rehire date | √ √ X √ √ √ √

termination date | √ √ X √ √ √ √

employment status | √ √ X √ √ √ √

batting average | X X X √ X X X

team history | X X X √ X X X

Output team history | X X X √ X X X

Display personal info | √ √ √ √ √ √ √

Process salaried payroll | √ X X √ √ √ X

Process part-time payroll | X √ X X X X √

__________________________ staff | executives | contractors

SSN number | √ √ √

first name | √ √ √

last name | √ √ √

home address | √ √ √

hire date | √ √ √

rehire date | √ √ √

termination date | √ √ √

employment status | √ √ √

batting average | X X X

team history | X X X

Output team history | X X X

Display personal info | √ √ √

Process salaried payroll | √ √ X

Process part-time payroll | X X √

Based on the table, I see that I have decided that first name, last name, and display personal info are common for all categories. This would be the upper-most class and I would probably call it Person. A volunteer would be represented as a Person object. For non-volunteers, the common fields in the table are SSN number, home address, hire date, rehire date, termination date, and employment status. I would probably put that in an Employee class that is a subclass of Person. Subclasses of Employee could be Full-Time and Part-Time, with Full-Time having the "process salaried payroll" method and Part-time having the "process part-time payroll" method. Based on the way I made decisions in the table, it looks like I would have a subclass of Full-Time called Athlete that would have all of the athlete fields and methods: batting average, team history, and output team history. Staff and executives could be represented as Full-Time objects, and contractors could be represented by Part-Time objects.

Please note that my answer is subject to my interpretation of the question, without having additional explanation about the categories people in the payroll system.