Skip to main content

Pega's Center-out business architecture

 

Pega's Center-out™ approach to digitally transforming a business process puts the customer and the strategic outcome at the center of the application design.

In this topic, you compare the traditional software development approach to Pega's Center-out business architecture, and examine the influence of the Center-out philosophy on the Pega Business Architect's approach to application design.

Traditional software architecture

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

In the following image, click the + icons to learn more about the disadvantages of the top-down and bottom-up approaches to software design and development:

Pega's Center-out approach

Pega's Center-out business architecture is customer-centric and focused on delivering business outcomes. It gives meaningful results fast, and sustains the architecture into the future by avoiding the mistakes of both the top-down and bottom-up approaches. 

Note: For more information on Pega's Center-out approach to business architecture, see Center-out explained.

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 as necessary without disturbing the functionality of the application itself.

In the following image, click the + icons 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:

Center-out principle

There are five principles associated with the Center-out business architecture, all organized around the customer and the strategic outcome:

  1. Manage intelligence centrally: 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: 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: 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: Pega allows users to quickly and easily define the data required to build the apps they need and then access that data in their running application – all without having to worry about how and where the data is stored and accessed.
  5. Manage variations to be scale-ready: 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™.

In the following image, click on the + icons to learn more about the five principles of Pega's Center-out business architecture:

As a Pega Business Architect, you always keep Center-out and its five principles in mind as you work with the Business and IT project teams to develop applications. As you redesign the client organization's business process, your focus should always be on meeting the needs of the customer and achieving the strategic objective of the business in the most effective, efficient, and user-focused way possible. Decisions about how the application is presented are based on the needs of the application's end-users. Decisions about how data is stored and accessed focus on providing the right information at the right time to support end-to-end completion of the workflow. By keeping Center-out at the forefront of application design, you create applications that allow our client's to best support their customers.

Note: For more information on Pega's Center-out architecture, see Build from the center outCenter-out business architecture, and Center-out: Managing variation in layers.

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?

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