The lecture materials state that one of the primary reasons to use interfaces is to achieve "loose coupling" within a software architecture. If an OrderProcessor class and a PaymentGateway class are loosely coupled via an interface, what is the practical, everyday benefit of this design?

Question

Answer

It completely eliminates the need for the Java garbage collector to monitor the communication between the two objects.

Answer

It guarantees that both classes will be compiled into machine code simultaneously, bypassing the standard bytecode interpretation.

Answer

It allows the developer to store both classes in the same physical java file, reducing project clutter.

Answer

It allows both classes to share private instance variables securely without risking external interference from other packages.

Answer

It ensures that modifying the internal workings of the PaymentGateway does not force the developer to rewrite the OrderProcessor.

Crowdly

The lecture materials state that one of the primary reasons to use interfaces is...

Want instant access to all verified answers on learning.monash.edu?