Object interaction in Java - Time & Space Complexity

Time Complexity: Object interaction

O(n)

Understanding Time Complexity

When objects talk to each other in a program, it takes time. We want to see how this time grows when we have more objects or more interactions.

How does the number of object interactions affect the program's speed?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Person {
    void greet(Person other) {
        System.out.println("Hello, " + other.getName());
    }
    String getName() {
        return "Friend";
    }
}

class Demo {
    static void greetAll(Person[] people) {
        for (Person p : people) {
            p.greet(p);
        }
    }
}
    

This code makes each person greet themselves by calling a method on each object in an array.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through the array of Person objects and calling greet on each.
• How many times: Once for each person in the array (n times).

How Execution Grows With Input

As the number of people grows, the number of greetings grows the same way.

Input Size (n)	Approx. Operations
10	10 greetings
100	100 greetings
1000	1000 greetings

Pattern observation: The work grows directly with the number of people.

Final Time Complexity

Time Complexity: O(n)

This means if you double the number of people, the time to greet doubles too.

Common Mistake

[X] Wrong: "Calling a method on an object inside a loop makes the time complexity more than linear."

[OK] Correct: Each method call here is simple and happens once per object, so it adds a fixed amount of work per item, keeping the growth linear.

Interview Connect

Understanding how objects interact and how that affects time helps you explain your code clearly and think about efficiency in real projects.

Self-Check

"What if greet called another method that loops over all people? How would the time complexity change?"

Practice

1.

What does it mean when two objects in Java interact?

Choose the best explanation.

easy

A. One object calls a method of another object to perform a task.

B. Two objects share the same memory location.

C. Objects are created using the same class.

D. Objects are stored in the same variable.

Solution

1. Step 1: Understand object interaction meaning

   Object interaction means objects communicate by calling each other's methods to work together.

2. Step 2: Evaluate options

   Only One object calls a method of another object to perform a task. describes calling methods between objects, which is how interaction happens.

3. Final Answer:

   One object calls a method of another object to perform a task. -> Option A

4. Quick Check:

   Object interaction = method calls between objects [OK]

Hint: Objects interact by calling methods on each other [OK]

Common Mistakes:

• Thinking objects share memory to interact
• Confusing object creation with interaction
• Assuming variables store multiple objects

2.

Which of the following is the correct syntax to call a method start() on an object car in Java?

easy

A. start(car);

B. car.start();

C. car->start();

D. start.car();

Solution

1. Step 1: Recall Java method call syntax

   In Java, to call a method on an object, use objectName.methodName();.

2. Step 2: Check each option

   car.start(); matches correct syntax. Options A, B, and C are invalid Java syntax.

3. Final Answer:

   car.start(); -> Option B

4. Quick Check:

   Method call = object.method() [OK]

Hint: Use objectName.methodName() to call methods [OK]

Common Mistakes:

• Using arrow (->) like in C++
• Reversing method and object order
• Calling method like a function with object as argument

3.

Consider the following Java code:

class Light {
    boolean isOn = false;
    void toggle() {
        isOn = !isOn;
    }
    boolean status() {
        return isOn;
    }
}

class Room {
    Light light = new Light();
    void switchLight() {
        light.toggle();
    }
    boolean lightStatus() {
        return light.status();
    }
}

public class Main {
    public static void main(String[] args) {
        Room room = new Room();
        System.out.println(room.lightStatus());
        room.switchLight();
        System.out.println(room.lightStatus());
    }
}

What is the output when this program runs?

medium

A. false
true

B. true
false

C. false
false

D. true
true

Solution

1. Step 1: Check initial light status

   Initially, isOn is false, so room.lightStatus() prints false.

2. Step 2: Toggle light and check status again

   Calling room.switchLight() toggles isOn to true. Then room.lightStatus() prints true.

3. Final Answer:

   false true -> Option A

4. Quick Check:

   Initial false, toggled true = false then true [OK]

Hint: Track boolean changes step-by-step [OK]

Common Mistakes:

• Assuming toggle sets true first without initial check
• Confusing method calls and variable values
• Ignoring initial value of isOn

4.

Find the error in this Java code snippet involving object interaction:

class Printer {
    void print(String message) {
        System.out.println(message);
    }
}

public class Main {
    public static void main(String[] args) {
        Printer printer;
        printer.print("Hello World");
    }
}

medium

A. The print statement syntax is incorrect.

B. The method 'print' is not defined in the Printer class.

C. The object 'printer' is declared but not initialized before use.

D. The class Printer should be public.

Solution

1. Step 1: Check object declaration and initialization

   The object 'printer' is declared but never assigned a new Printer instance.

2. Step 2: Understand consequences of uninitialized object

   Calling a method on an uninitialized object causes a NullPointerException at runtime.

3. Final Answer:

   The object 'printer' is declared but not initialized before use. -> Option C

4. Quick Check:

   Uninitialized object causes runtime error [OK]

Hint: Always initialize objects before calling methods [OK]

Common Mistakes:

• Assuming declaration equals initialization
• Thinking method absence causes error here
• Ignoring runtime NullPointerException

5.

You have two classes, BankAccount and Customer. A Customer has a BankAccount object. You want to add a method transferTo in BankAccount that transfers money to another BankAccount. Which of the following best shows how objects interact to perform this transfer?

class BankAccount {
    double balance;
    void deposit(double amount) { balance += amount; }
    void withdraw(double amount) { balance -= amount; }
    void transferTo(BankAccount other, double amount) {
        // Fill in this method
    }
}

class Customer {
    BankAccount account = new BankAccount();
}

hard

A. deposit(amount); withdraw(amount);

B. other.withdraw(amount); deposit(amount);

C. balance -= amount; other.balance += amount;

D. withdraw(amount); other.deposit(amount);

Solution

1. Step 1: Understand transfer logic

   To transfer money, withdraw from current account and deposit into the other account.

2. Step 2: Check method calls for interaction

   Calling withdraw(amount) on this object and deposit(amount) on the other object shows interaction.

3. Final Answer:

   withdraw(amount); other.deposit(amount); -> Option D

4. Quick Check:

   Transfer = withdraw from one, deposit to another [OK]

Hint: Transfer = withdraw from self, deposit to other [OK]

Common Mistakes:

• Withdrawing from the wrong account
• Directly changing balance without methods
• Depositing before withdrawing