Answer Posted / josh
Inheritance can lead to a combinatorial explosion of
classes. Composition should be somewhere in the code
oftentimes. For example, an Employee object can "contain" a
PaymentType object, a PaymentSchedule object, and a
PaymentMethod object. Each of those 3 objects are their own
classes. The Employee class creates instance of those
classes and "holds" on to them. From there, a higher class
such as a PayrollSystem can look at an Employee object and
query that Employee about that Employee's information
(namely its object contents). With composition, your code is
highly decoupled, meaning that those 3 object held by
Employee can easily be held by some other class (hence code
reuse). It is important to note that PaymentSchedule,
PaymentMethod, and PaymentType should be interfaces which
have multiple concrete implementations to them (ie. a
PaymentType interface could be implemented with an Hourly,
Salary, or SalaryWithCommission class for a given Employee).
Inheritance causes high coupling and reduces code
reusability. It helps to write a UML static(class) diagram
before typing up code
| Is This Answer Correct ? | 10 Yes | 5 No |
Post New Answer View All Answers
How to add menushortcut to menu item?
What is an 8 bit word?
What is immutable class in java?
What is classes in java?
Explain notify() method of object class ?
What is synchronization and why is it important in java programming?
How many bytes is a string?
Explain static nested classes ?
Can you call a method in a method?
Explain thread in java?
What is the impact of declaring a method as final?
What is downcasting?
What is lambda in java?
What's the purpose of static methods and static variables?
How will you load a specific locale?