Discussion
Closed
Advantages of having a dedicated COE layer in the Enterprise Class Structure
Hi Everyone,
I wanted to discuss about the advantages of having a dedicated COE layer in the Enterprise Class Structure
Eg:
| Application Implementation (Org-App-) |
| Application Framework (if required) (Org-FW-App) |
| Org COE layer (Org-COE-Data, Org-COE-Work ..) |
| Org layer (Org-Data, Org-Int, Org ..) |
| Pega FrameWorks |
| Pega Platform |
The assets to be created in the Org-COE layer can also be created in the Org- layer. By adding the COE prefix, we are actually lengthening the class name and adding an extra layer of direct inheritance.
Having said that, one may argue that a dedicated COE layer may be a clear indicator of COE assets and access to creation of rules in COE layer can controlled better.
I may be overlooking some other design thoughts for having a dedicated COE layer and so would like to hear the opinions of other members of the community