Abstract vs concrete classes in Java

Introduction

Abstract and concrete classes help organize code by defining what things can do and how they do it. Abstract classes set rules, while concrete classes fill in the details.

When you want to create a general blueprint for related classes but don't want to create objects from it directly.

When you want to force certain methods to be implemented by all subclasses.

When you want to share common code among related classes but still allow specific details to differ.

When you want to create objects that have full behavior and can be used directly.

When you want to build a system with clear roles: some classes define rules, others do the actual work.

Syntax

Java

abstract class Animal {
    // Abstract method (no body)
    abstract void makeSound();

    // Concrete method (has body)
    void sleep() {
        System.out.println("This animal is sleeping.");
    }
}

class Dog extends Animal {
    // Must implement abstract method
    void makeSound() {
        System.out.println("Woof Woof");
    }
}

class Cat extends Animal {
    void makeSound() {
        System.out.println("Meow");
    }
}

An abstract class cannot be used to create objects directly.

Concrete classes must implement all abstract methods from their abstract parent.

Examples

Abstract class Vehicle defines a method without body. Car provides the actual method.

Java

abstract class Vehicle {
    abstract void startEngine();
}

class Car extends Vehicle {
    void startEngine() {
        System.out.println("Car engine started.");
    }
}

Shape is abstract with an abstract method area(). Circle implements area() with its own formula.

Java

abstract class Shape {
    abstract double area();
}

class Circle extends Shape {
    double radius;
    Circle(double radius) {
        this.radius = radius;
    }
    double area() {
        return Math.PI * radius * radius;
    }
}

Abstract class with no concrete subclass means no objects can be made yet.

Java

abstract class EmptyAbstract {
    abstract void doNothing();
}

// No concrete class yet, so no objects can be created.

Concrete class with full methods can be used to create objects and call methods.

Java

class ConcreteClass {
    void greet() {
        System.out.println("Hello!");
    }
}

// Concrete class can be used to create objects directly.

Sample Program

This program shows an abstract class Animal with an abstract method makeSound() and a concrete method sleep(). Dog and Cat are concrete classes that implement makeSound(). We create Dog and Cat objects and call their methods.

Java

abstract class Animal {
    abstract void makeSound();

    void sleep() {
        System.out.println("This animal is sleeping.");
    }
}

class Dog extends Animal {
    void makeSound() {
        System.out.println("Woof Woof");
    }
}

class Cat extends Animal {
    void makeSound() {
        System.out.println("Meow");
    }
}

public class Main {
    public static void main(String[] args) {
        // Animal animal = new Animal(); // Error: cannot instantiate abstract class

        Dog dog = new Dog();
        Cat cat = new Cat();

        System.out.println("Dog says:");
        dog.makeSound();
        dog.sleep();

        System.out.println("Cat says:");
        cat.makeSound();
        cat.sleep();
    }
}

Important Notes

Time complexity: Abstract vs concrete classes do not affect time complexity directly; they organize code structure.

Space complexity: No extra space cost; just class definitions.

Common mistake: Trying to create an object from an abstract class causes a compile error.

Use abstract classes when you want to define a common interface and share code but prevent direct instantiation.

Use concrete classes when you want to create usable objects with full behavior.

Summary

Abstract classes define methods without full details and cannot create objects directly.

Concrete classes provide full method details and can create objects.

Use abstract classes to set rules and concrete classes to do the actual work.

Practice

1. Which statement best describes an abstract class in Java?

easy

A. It is the same as an interface and cannot have any methods with code.

B. It must have all methods fully implemented and can be instantiated.

C. It can have methods without implementation and cannot be instantiated directly.

D. It is a class that can only contain static methods.

Solution

1. Step 1: Understand abstract class definition

   An abstract class can have methods without implementation (abstract methods) and cannot create objects directly.

2. Step 2: Compare with other options

   Concrete classes have full method implementations and can be instantiated. Interfaces differ from abstract classes. Static-only classes are unrelated.

3. Final Answer:

   It can have methods without implementation and cannot be instantiated directly. -> Option C

4. Quick Check:

   Abstract class = no direct objects [OK]

Hint: Abstract classes can't create objects directly [OK]

Common Mistakes:

• Thinking abstract classes can be instantiated
• Confusing abstract classes with interfaces
• Assuming all methods must be implemented

2. Which of the following is the correct way to declare an abstract class in Java?

easy

A. abstract class Vehicle {}

B. class abstract Vehicle {}

C. Vehicle abstract class {}

D. class Vehicle abstract {}

Solution

1. Step 1: Recall Java syntax for abstract classes

   The keyword 'abstract' comes before 'class' followed by the class name.

2. Step 2: Check each option

   Only 'abstract class Vehicle {}' matches correct syntax. The other options have incorrect keyword order.

3. Final Answer:

   abstract class Vehicle {} -> Option A

4. Quick Check:

   abstract keyword before class name [OK]

Hint: Put 'abstract' before 'class' keyword [OK]

Common Mistakes:

• Placing 'abstract' after 'class'
• Mixing keyword order
• Omitting 'abstract' keyword

3. What will be the output of the following Java code?

abstract class Animal {
    abstract void sound();
}

class Dog extends Animal {
    void sound() {
        System.out.println("Bark");
    }
}

public class Test {
    public static void main(String[] args) {
        Animal a = new Dog();
        a.sound();
    }
}

medium

A. Runtime error

B. Animal sound

C. Compilation error

D. Bark

Solution

1. Step 1: Understand class hierarchy and method overriding

   Animal is abstract with abstract method sound(). Dog extends Animal and implements sound() printing "Bark".

2. Step 2: Analyze main method execution

   Animal reference points to Dog object. Calling a.sound() runs Dog's sound(), printing "Bark".

3. Final Answer:

   Bark -> Option D

4. Quick Check:

   Abstract method overridden = Dog's output [OK]

Hint: Abstract method calls run subclass implementation [OK]

Common Mistakes:

• Expecting abstract class method to run
• Thinking abstract class can be instantiated
• Confusing compile and runtime errors

4. Identify the error in the following code snippet:

abstract class Shape {
    abstract void draw();
}

class Circle extends Shape {
    // No draw() method implemented
}

public class Test {
    public static void main(String[] args) {
        Circle c = new Circle();
        c.draw();
    }
}

medium

A. Circle must implement the abstract method draw() or be declared abstract.

B. Cannot create object of class Circle.

C. Abstract class Shape cannot have abstract methods.

D. No error, code runs fine.

Solution

1. Step 1: Check subclass implementation of abstract methods

   Circle extends Shape but does not implement abstract method draw().

2. Step 2: Understand Java rules for abstract methods

   A concrete class must implement all abstract methods or be declared abstract itself. Circle is concrete but missing draw().

3. Final Answer:

   Circle must implement the abstract method draw() or be declared abstract. -> Option A

4. Quick Check:

   Concrete subclass must implement all abstract methods [OK]

Hint: Concrete class must implement all abstract methods [OK]

Common Mistakes:

• Thinking abstract methods can be skipped
• Assuming abstract class can't have abstract methods
• Believing object creation is the error

5. You want to design a system where different types of employees calculate their salary differently. Which approach best uses abstract and concrete classes?

hard

A. Create only concrete classes for each employee type without any abstract class.

B. Create an abstract class Employee with an abstract method calculateSalary(), then create concrete subclasses like Manager and Developer implementing it.

C. Use an interface with no methods and concrete classes implementing it.

D. Create a concrete Employee class with a fixed calculateSalary() method used by all employees.

Solution

1. Step 1: Identify need for shared rules with different implementations

   Employee types share concept of salary calculation but differ in details.

2. Step 2: Use abstract class with abstract method

   Abstract class Employee defines calculateSalary() abstractly. Subclasses implement specific logic.

3. Step 3: Evaluate other options

   Create only concrete classes for each employee type without any abstract class. lacks shared abstraction. Use an interface with no methods and concrete classes implementing it. uses interface with no methods, so no contract. Create a concrete Employee class with a fixed calculateSalary() method used by all employees. fixes salary calculation, no variation.

4. Final Answer:

   Create an abstract class Employee with an abstract method calculateSalary(), then create concrete subclasses like Manager and Developer implementing it. -> Option B

5. Quick Check:

   Abstract class sets rules, subclasses do work [OK]

Hint: Abstract class for rules, concrete classes for details [OK]

Common Mistakes:

• Not using abstraction for shared behavior
• Using concrete class with fixed method only
• Interfaces without methods don't enforce contracts