Question

7
Replies
7785
Views
srikh Member since 2013 4 posts
PEGA
Posted: May 16, 2017
Last activity: October 16, 2018
Closed

When do we need to create just a framework layer and and when do we create Framework layer and implementation layer?

When do we actually need to create Framework layer? I feel for any kind of automation we want to do we should start with creating Framework layer. Because we never know if there is or there is no chance of of a specific implementation for the problem we are trying to automate. Is this correct?

When do we actually need to create Implementation layer? What is the trigger point which forces us to create a implementation layer? If there are no specifics for an implementation should we still create implementation layer?

SSA content says 'One key aspect to the implementation layer is that this is where any of our work classes should be instantiated'. So regardless of whether there are specifics in terms of implementation we should create implementation layer on top of Framework layer?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Moderation Team has archived post
Share this page LinkedIn