Think data hiding. Then think encapsulation with methods. Then cohesion, factoring classes out as early in the process as you can. If you do that, loose coupling and easier maintenance will come to you.

In this discussion forum, discuss data hiding, including minimizing/localizing variable scope, cohesion, loose coupling, and maintainability to explain what the statement means and its value in Java programming. Be sure to define or explain all relevant terms. At a minimum, the forum should address the following:

Why is the term data hiding not particularly good?

What does it mean to minimize scope?

Which is more desirable, high cohesion or low cohesion?

Whats the difference between public and private fields and methods?

What are monolithic programs? How might they develop? Are they desirable?

Should programmers be putting in extra work initially to benefit others later on?