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

Running your own one person company

Recently there was a post on PuneTech on mom's re-entering the IT work force after a break. Two of the biggest concerns mentioned were : Coping with vast advances (changes) in the IT landscape Balancing work and family responsibilities Since I have been running a one person company for a good amount of time, I suggested that as an option. In this post I will discuss various aspects of running a one person company. Advantages: You have full control of your time. You can choose to spend as much or as little time as you would like. There is also a good chance that you will be able to decide when you want to spend that time. You get to work on something that you enjoy doing. Tremendous work satisfaction. You have the option of working from home. Disadvantages: It can take a little while for the work to get set, so you may not be able to see revenues for some time. It takes a huge amount of discipline to work without a boss, and without deadlines. You will not get the benefits (insuranc...
10 comments
Read more

Testing Groovy domain classes

If you are trying to test Grails domain class constraints by putting your unit test cases in the 'test/unit' directory, then your tests will fail because the domain objects will not have the 'valdate' method. This can be resolved in two ways: Place the test cases inside test/integration (which will slow things down) Use the method 'mockForConstraintsTests(Trail)' to create mock method in your domain class and continue writing your test cases in 'test/unit' What follows is some example code around this finding. I am working on a Groovy on Grails project for a website to help programmers keep up and refresh their skills. I started with some domain classes and then moved on to write some unit tests. When we create a Grails project using grails create-app , it creates several directories, one of which is a directory called 'test' for holding unit tests. This directory contains two directories, 'unit', and 'integration' for unit and ...
11 comments
Read more

My first impressions of Python for the second time

I had worked a bit in Python many years back. Since then I have forgotten almost everything I learned back then. I think the phrase "Out of sight out of mind" applies perfectly to my mind. Since the last few days, I have started relearning Python, and this time I am recording my impressions of Python after having come to it from a Java background. Indentation: Python uses indentation to specify blocks of code, instead of curly braces. I like this, because we anyways indent code to increase readability, so why not achieve two tasks together. Code looks much cleaner without the curly braces. However there may be a little downside. Everyone in the team will have to set up their IDE's in the same way. Things might fall apart if some people use tabs and others use spaces for indentation. Access modifiers: Python does not have public, private, and protected keywords. Everything is public. However, private members can be specified with a leading single underscore. If we use do...
6 comments
Read more