Skip to main content

Designing Pega enterprise applications

Your job, as a lead system architect (LSA), 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. 

 An enterprise application should function efficiently and seamlessly by meeting the business objectives of an organization, integrating multiple systems in the organization, being secure, and yielding substantial return on investment (ROI). The application should be flexible and scalable enough to adapt to the changing models of the business. 

There are a few important points to consider when designing enterprise applications: 

  1. Understand the technical landscape of the enterprise for which you are building the new Pega application. The details of the technical landscape help you to design Pega projects that perfectly fit the organization's enterprise architecture. 

  1. Design an architecture that meets the business objectives, instead of building the application directly. 

  1. To achieve the business objectives, iteratively focus on short-term goals, based on evaluation of the outcomes. 

  1. Business requirements change from time to time to meet consumer needs. Having a modular architecture ensures that changes in one system or application do not affect other systems and applications. 

  1. Building an application that functions seamlessly, irrespective of communication channels, can help to boost the consumers' productivity and leads to faster decision making. 

  1. Based on business needs, choose wisely how the application can be hosted; whether on-premises or in the cloud. Having the Pega Platform™ support guide or Pega Cloud® services catalogue can help architects to choose the required infrastructure. 

  1. Pega’s industry-specific strategic applications can be used to build quick go-to-market and high-performing applications that use standard processes and data models of the particular industry in question.  

  1. Design the enterprise layer first and identify the reusable components that you can build to meet current and future business needs. 

  1. Your process automation design should use Process AI, Process Fabric, and Process Mining capabilities. 

  1. Plan Application Programming Interfaces (APIs) for better and easier communication with other technologies used in the organization. 

  1. Focus on Security design from day one of the project by using proper Authentication, Authorization, and Auditing strategies. Application vulnerability should be assessed periodically.  

  2. To calculate ROI, identify the most relevant key performance indicators (KPIs) with respect to each business objective. 

  3. Follow Pega Express methodology , read more about it here 

 

For more information about point 6, see: 

Check your knowledge with the following interaction:

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?

Yes
No

Want to help us improve this content?
Suggest an edit

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