Understanding the is-a Relationship in Inheritance
You'll learn: How inheritance creates an "is-a" relationship where every subclass instance is a type of its superclass.
What Is the Is-A Relationship?
When you use extends to create inheritance, you're declaring that the subclass is a more specialized version of the superclass. This isn't just a coding technique—it's a logical relationship that should mirror real-world categories.
If Dog extends Animal, then every Dog is an Animal. If Student extends Person, then every Student is a Person. This relationship is permanent and fundamental to how your objects work.
Why This Matters
The is-a relationship determines what's valid in your code. Because a Dog is an Animal, you can use a Dog anywhere an Animal is expected:
Animal myPet = new Dog(); // Valid: a Dog IS-AN Animal
This works because of the type compatibility you learned earlier—subclass instances can be referenced as superclass types.
The Is-A Test
Before creating inheritance, ask: "Is every instance of my subclass truly a type of the superclass?"
Circle extends Shape✓ (every circle is a shape)Manager extends Employee✓ (every manager is an employee)Square extends Rectangle? (geometrically true, but tricky in code)Car extends Engine✗ (a car has an engine, not is an engine)
That last example shows the difference between is-a (inheritance) and has-a (composition with fields).
Testing Your Understanding
The is-a relationship should feel natural. If you have to stretch logic to justify it ("Well, technically a User is a Database..."), you're probably misusing inheritance.
Key Takeaway: The is-a relationship means a subclass is a specialized type of its superclass, allowing subclass objects to be treated as superclass instances wherever that type is expected.