Application specialization

Application specialization techniques with Pega software present a method to create bespoke versions of applications for specific business units or departments. This tailoring process is akin to crafting a made-to-measure suit, ensuring an optimal fit for the wearer. However, it is crucial to consider the factors of performance and maintenance when deciding on the appropriate specialization techniques to use.

Understanding the distinction between framework and implementation structures is also essential. A framework can be seen as the bedrock upon which work-processing is built. It is not always the primary choice for application specialization, but when employed correctly, it can significantly enhance the process. It is imperative, however, to be aware of both its benefits and limitations. In many instances, an implementation structure can effectively build business scenarios without the need for a framework structure.

Designing a framework requires knowledge of how more than one implementation uses it. Without this information, abstracting a model common to many implementations is difficult. The creation of a framework is not always the best solution for application specialization. The purpose of a framework is to abstract the business process that can be extended by implementation applications. However, there is overhead in maintaining the framework.

Pega LSAs should carefully consider the pros and cons of the framework structure. Most business scenarios can be built using an implementation structure without abstracting the framework structure. Focus on the implementation at the beginning while watching for future specialization. Using a framework structure solely for reusable code, without abstracting the business process, is not a good design choice. An application at the enterprise layer of an implementation structure is always a good choice for any concrete or executable reuse code.

The decision to use application specialization is often situation-dependent. For example, if a new business unit or user role is added to an existing application, and this addition operates independently without disrupting other units or roles, application specialization emerges as the optimal solution.

Consider a scenario where business operations are expanding into Japan, necessitating an application to be available in Japanese. In such a case, the most effective solution would be to specialize the existing application by localizing it in Japanese. Similarly, if a new set of user roles is introduced with a different work context, it would be advantageous to establish a separate application, making application specialization the preferred choice.

Before opting for application specialization, it is advisable to explore other specialization techniques, such as circumstance, class, and ruleset specialization. Depending on the specific requirements, these alternatives might provide a better fit for the application.

As an LSA, your objective is to discover what works best for specialized business needs.

Check your knowledge with the following interaction: