CS304 Object Oriented Programming GDB Solution Spring Semester July 2013

[Vuhelper]

View more random threads:

• "MGT502 GDB 2" July 2010
• ENG101 English Comprehension GDB Spring solution June 2012
• MGT502 Organizational Behaviour GDB No. 01 Solution Fall...
• CS201 Introduction to Programming GDB No.1 Solution Fall...
• mgmt630 GDB solution 2011
• MTH202 Discrete Mathematics GDB No. 1 Solution Fall...
• Mgt503 GDB Solution spring june 2011
• STA 630 Research Method Problems and Solution spring 2014
• CS507 GDB Spring 2011 IDEA SOLUTION
• MGT520 International Business GDB No.1 Solution Spring...

CS304 Object Oriented Programming GDB Solution Spring Semester July 2013


Suppose you are working as a software developer in a company. You have been given a task to develop a software system design for some real world scenario. One of the basic activities of any software system design is to establish relationships between classes. Suppose at the stage of creating relationships for some classes, you have to choose either inheritance or composition as these are two fundamental ways to relate classes by achieving feature of code re-usability. Being a developer, for what reasons, would you prefer one technique to the other keeping in mind the reusability factor? Support your answer with solid reasons.

Solution:

Inheritance is not well suited for code reuse. Inheriting for code reuse usually leads to:

Classes with inherited methods that must not be called on them (violating the Liskov substitution principle), which confuses programmers and leads to bugs.
Deep hierarchies where it takes inordinate amount of time to find the method you need when it can be declared anywhere in dozen or more classes.
Generally the inheritance tree should not get more than two or three levels deep and usually you should only inherit interfaces and abstract base classes.

Substitution
Coil Spring
Local Jobs
Linux operating system
Government Jobs

Sponsored Links

There is however no point in rewriting existing code just for sake of it. However when you need to modify, try to switch to composition where possible. That will usually allow you to modify the code in smaller pieces, since there will be less coupling between the classes.

[Vuhelper]

Solution:

Inheritance is not well suited for code reuse. Inheriting for code reuse usually leads to:

Classes with inherited methods that must not be called on them (violating the Liskov substitution principle), which confuses programmers and leads to bugs.
Deep hierarchies where it takes inordinate amount of time to find the method you need when it can be declared anywhere in dozen or more classes.
Generally the inheritance tree should not get more than two or three levels deep and usually you should only inherit interfaces and abstract base classes.

Substitution
Coil Spring
Local Jobs
Linux operating system
Government Jobs

There is however no point in rewriting existing code just for sake of it. However when you need to modify, try to switch to composition where possible.
That will usually allow you to modify the code in smaller pieces, since there will be less coupling between the classes.