Question 4 (2 points) Saved Given a software program that needs to process accounts payable processing with very different objects for example Employee and Invoice objects what would be the best design strategy? Create interface "Payable" with method justPayAmount(), have each object implement Payable. Create abstract class "PayMe" with method justPayAmount(), re-write the existing inheritance hierarchies, and have each object extend PayMe. O Use an extensive if-else logic with lots of documentation telling the programmers what to do