Based on the statement below, my question follows:
Cohesion and Coupling are very software engineering principles used. When we want to have a mature and sustainable architecture, we must take these two principles into account, since each of them has a specific purpose that aims to improve the design of the software. What happens is that many people do not know the difference between them and end up failing to get the benefits that put them into practice at the time of designing the architecture of a software.
Source: Understanding Cohesion and Coupling - DevMedia
When I'm in the software architecture phase, basing myself on best practices, when I can build a cohesive, low-coupling class, can I say that encapsulamento
targets coesão
?