For example, if your SOA entry point is business centric, you can defer loose coupling via the ESB, even though the ESB is included in your reference architecture.

Afferent coupling represents the count of how many other classes reference the current class, via either fields or parameters.

Reference cycles between classes in different packages or projects are generally considered to be a bad programming practice (they introduce tighter coupling between components).