2022. 2. 28. 14:45ㆍSoftware Architecture/Software design
- 목차
Facade pattern
Think about that we have several features such as Scanning, Parsing, and building node from program code. And each of them provides its own interface that can be used for activating their own feature. But, the client does not want to know and control each of interfaces, but just want to use aggregated interface that can be used as simple gateway interface controlling whole the other sub interfaces. In such a case, we can use 'facade' design pattern. and the meaning of the facade is denoting that a class can provide aggregated features and hide classes inside the system. Thus, a client just try to use this facade interface instead of using the interfaces provided by whole other sub classes.
'Software Architecture > Software design' 카테고리의 다른 글
Flyweight pattern (0) | 2022.02.28 |
---|---|
Factory method (0) | 2022.02.28 |
Decorator pattern (데코레이터 패턴) (0) | 2022.02.28 |
Composite pattern (컴포지트 패턴) (0) | 2022.02.28 |
Command pattern (커맨드 패턴) (0) | 2022.02.28 |