Pega's Center-out business architecture

Traditionally, applications are designed either from the top down, meaning the application is based on the delivery Channels, or from the bottom up, meaning the application is designed around data storage and access systems.

Match the numbers to the following image to learn about the disadvantages of the top-down and bottom-up approaches to software design and development:

1. Top-down approach: The top-down approach designs applications that are specific to the presentation layer's delivery Channels, such as the web, mobile, digital messaging, or voice-AI. One of the most significant disadvantages of the top-down approach is having to implement the same business logic multiple times to deliver a consistent experience across the different Channels.
2. Bottom-up approach: The bottom-up approach to software design and development is focused around the data access layer. The risk with bottom-up is that each system has its view of the data used by its applications. Legacy systems built in silos result in duplicates of data held in multiple systems. Also, different pieces of data about a single business entity, for example a Customer, can be found in different data storage systems, with no one solution able to provide a single view of the complete entity.

By centering on business logic and outcomes, Pega’s Center-out workflows seamlessly connect front- and back-office operations, helping organizations meet customers wherever they are while improving operational efficiency.

Pega's Center-out approach puts the business logic layer at the center of application design. This business logic layer maintains all of the information needed to successfully achieve the business outcome. The presentation and data access layers are kept separate from the business logic, ensuring that delivery Channels and database access can be altered. This separation allows organizations to orchestrate end-to-end customer journeys across channels while keeping business rules consistent, reusable, and centrally managed.

Match the numbers to the following image to learn how Pega puts the business logic needed to avoid silos and duplication, delight the customer, and achieve the strategic outcome at the center of application design:

1. Presentation layer: The application's business logic is connected up into the Presentation layer in such a way that the delivery Channels dynamically respond to changes in the central business logic.
2. Application and business logic layer: The Application layer is the central hub, containing all of the business logic needed to achieve the desired strategic outcome for the organization.
3. Data access layer: Connections down into the Data access layer are made in such a way as to insulate them from the business logic so that changes in systems of record, such as going from on-premise to Cloud data storage, do not require changes in the application's business logic. 

There are five principles associated with the Center-out business architecture, all organized around the customer and the strategic outcome. Match the numbers to the following image to learn more about the five principles of Pega's Center-out business architecture:

1. Manage intelligence centrally: Start with the business logic. Business outcomes should be guided by real-time customer information; rules are consistently enforced, and every recommended action is on target. 
2. Focus on outcomes, align your process: Get the work done. Use Case Management to manage, automate, and improve work by applying a Microjourney™ approach that implements a part of the customer journey that is tied to a specific outcome.
3. Connect experiences up to your Channels: Provide a consistent user experience. Keep the front-end logic and back-end logic coordinated. Changes are dynamically reflected without recoding.
4. Connect down to your data, keep logic nimble: Access data without adding complexity. Pega allows users to quickly and easily define the data required to build the apps they need, then access that data in their running applications – all without worrying about how or where the data is stored or accessed.
5. Manage variations to be scale-ready: Start small and fast. Pega helps organizations adapt to different customer types, lines of business, geographies, and more. Scale big and broad, and stay future-proof by using Pega's Situational Layer Cake™.

The Center-out business architecture improves development efficiency, agility, governance, and scalability.

• Efficiency: Developers define business rules once in a central location, which eliminates duplication and reduces inconsistencies across channels and applications.
• Agility: When business requirements change, you update the central logic. The system applies those changes across all channel interfaces, making applications more responsive to evolving business needs.
• Governance: Centralized rules simplify auditing, monitoring, and policy enforcement across interfaces.
• Scalability: As your organization adds new channel interfaces or customer touchpoints, you reuse existing business logic to maintain consistency.

Together, these benefits help organizations improve operational efficiency, maintain governance, and scale consistent experiences across channels.

Model-driven user interface (UI) is an approach in which underlying data models and business rules generate the user interface. In the Center-out architecture, these models reside at the core, and the system dynamically generates the UI from them.

Pega applications use patterns as reusable templates for implementing model-driven UIs. You define the Data Model and business rules at the center, then select and configure patterns to render the interface. This approach maintains consistency and improves developer productivity while keeping business logic centralized and user experiences consistent across devices and channels. 

One key advantage of using patterns is the separation between business logic and presentation. When business rules change, the UI adapts automatically without manual updates. This separation keeps business logic at the center and allows the UI to dynamically reflect those rules. Pattern-based UIs also support responsive design across devices and channels.

Pega applications provide built-in patterns for common UI scenarios, such as forms, lists, dashboards, and Case management interfaces. You can customize and extend these patterns to meet specific business needs while maintaining the Center-out principle.