OOP & Design Patterns - Interface Segregation & Dependency Inversion - Fat Interfaces & IoC
Which design pattern or principle best matches the scenario where a client class depends on abstractions and receives its dependencies from an external source at runtime?
