Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Designing Pega enterprise applications

Your job, as a lead system architect, is to take the digital transformation vision and transform business applications that perform real work for real people and drive business outcomes for even the largest of organizations. If you start with Pega in the middle and work your way out to all existing technologies, channels, integrations to legacy systems and systems of record, one application at a time, the vision becomes reality, release by release. The following video describes how to design the end-to-end Pega enterprise application, starting with Pega in the middle of your design.

For a more comprehensive demonstration of Pega Infinity™, see Pega Infinity: Transform without limits

An Enterprise Application should function efficiently and seamlessly by meeting the business objectives of an organization, integrate multiple systems of an organization, be secure, and yields a substantial return on investment (ROI). It should be flexible and scalable enough to adapt to changing models of a business.

A few important points to consider while designing enterprise applications:

  1. Design the architecture that meets the business objectives instead of deciding the architecture first and then trying to make an application fit within the architecture.
  2. Iteratively focus on the short-term goals based on the evaluation of the outcomes to achieve the business objectives.
  3. Business requirements change from time to time to meet consumer needs. Having a modular architecture ensures that changes in one system/application do not affect the other.
  4. Building an application that functions seamlessly irrespective of the communication channels would help to boost the consumers' productivity and leads to faster decision making.
  5. Based on the business needs, choose wisely how the application can be hosted (on-premise vs cloud).
  6. Application vulnerability should be assessed periodically.
  7. Secure the enterprise application by controlling the user access and resources of the application.
  8. Enterprise applications should be well-linked with each other for interoperability.
  9. Maintainability shouldn’t be a cumbersome job.
  10. Reduce the development efforts by building reusable components when needed.
  11. Identify the most relevant KPIs with respect to each business objective for the calculation of ROI.
Designing for pega enterprise 86
In this diagram we show Pega application layers in the middle managing intelligence centrally. The Pega applications connect up to the channels needed to complete a step while connecting down to the backend systems and data needed to, or updated by, completing a step.

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

40% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice