Encapsulation best practices in Java - Step-by-Step Execution

Concept Flow - Encapsulation best practices

Define private fields

↓

Create public getters/setters

↓

Control access to fields

↓

Use methods to validate or modify data

↓

Hide internal details from outside

↓

Allow safe interaction only

Encapsulation means keeping data private and controlling access through methods to protect and manage it safely.

Execution Sample

Java

public class Person {
  private String name;
  public String getName() { return name; }
  public void setName(String name) {
    if(name != null && !name.isEmpty()) this.name = name;
  }
}

This code shows a class with a private field and public methods to safely access and change it.

Execution Table

Step	Action	Field 'name' Value	Condition Checked	Result
1	Create Person object	null	N/A	Object created, name is null
2	Call setName("")	null	name != null && !name.isEmpty() is false	name not changed
3	Call setName("Alice")	null -> "Alice"	name != null && !name.isEmpty() is true	name set to "Alice"
4	Call getName()	"Alice"	N/A	Returns "Alice"

💡 No more actions, encapsulation protects 'name' from invalid values

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
name	null	null	"Alice"	"Alice"

Key Moments - 3 Insights

Why can't we access 'name' directly from outside the class?

Because 'name' is private, only methods inside the class can access it, as shown in step 1 and 2 of the execution_table.

What happens if we try to set 'name' to an empty string?

The setter method checks the condition and refuses to change 'name', so it stays null as seen in step 2.

How does the getter method help us?

It allows safe read access to 'name' without letting outside code change it directly, shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'name' after step 2?

A null

B "" (empty string)

C "Alice"

D undefined

💡 Hint

Check the 'Field name Value' column at step 2 in the execution_table

At which step does the condition in setName allow changing 'name'?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Condition Checked' column in the execution_table for step 3

If we remove the condition in setName, what would happen to 'name' after step 2?

A It would stay null

B It would become empty string ""

C It would become "Alice"

D It would cause an error

💡 Hint

Think about what setName does without the condition, referencing step 2 action

Concept Snapshot

Encapsulation means:
- Make fields private
- Use public getters/setters
- Validate data in setters
- Hide internal details
- Control how data changes
This protects data and keeps code safe.

Full Transcript

Encapsulation is a way to keep data safe inside a class by making fields private. We use public methods called getters and setters to read or change the data. The setter method can check if the new value is valid before changing it. For example, in the Person class, the name field is private. The setName method only changes name if the new value is not empty. The getName method returns the current name. This way, outside code cannot directly change name to something invalid. The execution table shows how name starts as null, stays null when setName is called with empty string, and changes to "Alice" when setName is called with a valid name. This protects the data and keeps the class in control of its own state.