Override Adding to Superclass Result

One of the most common override patterns in AP CSA: a subclass overrides a method that returns a value, calls super.method() to get the parent's result, and then adds to or modifies that result before returning.

This pattern keeps subclass code DRY — you reuse the superclass logic instead of duplicating it — and remains correct even if the superclass implementation later changes.

On the AP exam, this is the dominant inheritance pattern in FRQ #3 and #4 of inheritance-style problems.

The template

public class Subclass extends Superclass {
    @Override
    public ReturnType method(args) {
        ReturnType base = super.method(args);
        // modify or extend base
        return base + subclassExtra;
    }
}

Concrete example

public class Employee {
    private double base;
    public Employee(double base) { this.base = base; }
    public double getSalary() { return base; }
}

public class Manager extends Employee {
    private double bonus;
    public Manager(double base, double bonus) {
        super(base);
        this.bonus = bonus;
    }
    @Override
    public double getSalary() {
        return super.getSalary() + bonus;
    }
}

Manager.getSalary() reuses the Employee logic for the base salary and adds the manager-specific bonus. If the Employee class later adds tax handling, the Manager picks it up automatically.

Why not just access fields directly?

In AP CSA, superclass instance variables are private — the subclass cannot read them directly. super.getSalary() goes through the public accessor and respects encapsulation.