Architectural flexibility refers to the ability of a system to adapt to changing requirements and to be easily modified or extended without major redesigns. System encapsulation, on the other hand, refers to the process of hiding the implementation details of a system from its users, so that they only have access to the public interfaces.
Architectural flexibility supports system encapsulation by allowing changes to be made to the system without compromising its encapsulation. For example, if a new requirement comes up that requires a change in the system's functionality, the system's encapsulation can be maintained by adding new modules or interfaces without disrupting the existing ones. This ensures that the users of the system are shielded from the implementation details, while also allowing for the system to evolve and adapt over time.
In short, by providing flexibility, architects can maintain system encapsulation by allowing changes to be made to the system without disrupting its core functionality or exposing its implementation details.
Publication date: