Skip to main content

Your feedback on goals of software design

Please take a couple of minutes to give your feedback on this section. Would you like to see any additions, subtractions, or changes? How did you like the audio and video descriptions used in this section? I know they are not optimal, and I hope to improve them, but it will really help me if I get feedback on exactly what should be improved to make the course more effective for you.



Note: This post was originally posted on my blog at http://www.adaptivelearningonline.net

You will find below comments from the original post


COMMENT:
AUTHOR: Rashmi
DATE: 10/18/2006 05:50:25 PM
Sir could you please explain the difference between inheritance and composition through an example code



COMMENT:
AUTHOR: Parag
DATE: 10/20/2006 01:16:47 PM
Thanks for the suggestion. I will add an example to the blog post. Till then, here is a quick code sample.

//this class uses inheritance. Guitar inherits
//from MusicalInstrument
public class Guitar extends MusicalInstrument {
//...
}

//this is an example of composition. The class
//Car is composed of several instances of the
//class Wheel
public class Car {
Wheel wheels[];
//...
}

When a class has other class(es) as instance or class variables then a composition relationship is established between them.
Composition also allows code reuse. In the above example the class Car can invode methods of Wheel thus acheiving functionality without impemented it in it's own class.

Notice the relationship between the classes in both the examples.
A Guitar IS-A MusicalInstrument.
We typically use inheritance when there is an IS-A relationship between two classes.
A Car HAS Wheel(s)
We typically use composition between classes that have a HAS-A or HAS relationship.

now before I wrap up, a couple of questions. Why is it incorrect to use inheritance when there is a HAS-A relationship between two classes. More specifically why should we avoid...
public class Car extends Wheel {}

Here is a very good link that explains the concept in detail:
http://www.artima.com/designtechniques/compoinh.html

--
Parag

Labels:

Comments

Post a Comment

Popular posts from this blog

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path
1 comment
Read more

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- prismnet.com As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a
Post a Comment
Read more

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other
3 comments
Read more