Academy

Pega Constellation
Application Development
Mastery
1
Contents

Chapter 1: Introduction to the Pega Constellation Project ......................................................... 3

Digital Citizen Services for Pandora ............................................................................................. 3
Chapter 2: Pega’s Best Practice for Modular and reusable application design ........................ 5
Chapter 3: Framework to Identify, Validate and Implement modular architecture ................ 6
Framework Step1: Analyse Business Requirement ................................................................... 6
1.1 Apply Stage (Persona: Parent / Applicant) ................................................................................ 7
1.2 Process Stage (Employee) ......................................................................................................... 7
1.3 Payment Stage (Finance Employee).......................................................................................... 8
Framework Step2: Identify common entities ............................................................................. 8
2.1 Reuseable Entities for the entire program ............................................................................... 9
Framework Step3: Identify common process .......................................................................... 10
3.1 Reuseable Processes for the entire program .......................................................................... 10
Framework Step4: Validate Modularity & Application design .............................................. 11
4.1 Collaboration Between Pega BA, LSA, and SSAs in Validating Modularity ............................. 11
4.2 Design project architecture..................................................................................................... 11
4.3 Establishing Governance access various Pega applications .................................................... 12

2
Chapter 1: Introduction to the Pega Constellation
Project

Digital Citizen Services for Pandora

The Government of Pandora is embarking on a transformative journey to digitize its citizen

services. The aim is to create a robust digital platform where citizens can apply for various
allowances, and government employees can efficiently process these applications,
ensuring timely support and transparency.

Key Objectives:
1. Streamlined Allowance Applications: Citizens can apply for a variety of benefits,
including:
o Child Care Benefit: Assisting parents with the costs of raising children
under 18.
o Child Budget: Providing financial support to unemployed individuals with
children.
o Rent Allowance: Helping individuals with low incomes afford rental
housing.
o Health Care Allowance: Supporting individuals with low incomes in
affording health care costs.

Phase 1: Child Care Benefit (This is the only process we will build)
The first phase of this project focuses on the Child Care Benefit. This process will be built
as a foundational module, incorporating reusable components that will later be extended
to the other services. The platform will demonstrate how automation can streamline
workflows, reduce processing time, and improve citizen satisfaction. Students
participating in this course will gain hands-on experience in designing and developing
scalable applications that adhere to industry standards and best practices.
3
2. Efficient Government Operations: Government employees will have access to a
unified system to manage applications, verify eligibility, and process payments,
enabling faster and more transparent decision-making.

3. Modular and Reusable Architecture: The system is being designed following

Pega's best practices, with a focus on modularity and reusability. This approach
ensures that components built for one service can be leveraged for others,
maximizing efficiency and minimizing redundancy.

4
Chapter 2: Pega’s Best Practice for Modular and
reusable application design

Source: Pegasystems

Source: Pegasystems

Source: Pegasystems

5
Chapter 3: Framework to Identify, Validate and
Implement modular architecture

To develop modular applications, start by analysing business requirements, breaking them

into smaller functional units, and documenting workflows, dependencies, and objectives.
Identify common entities within the data model, such as customers or payments, and
abstract data access using Data Pages and standardized data transforms. Recognize
shared processes like approvals, case management, and notifications, as well as reusable
integrations such as payment gateways and CRMs, storing them in a framework layer for
reusability. Validate modularity through design thinking workshops, showcasing designs to
stakeholders and refining them based on feedback. Finally, implement modular
applications by building foundational modules incrementally, testing and documenting
reusable components, and monitoring functionality and scalability.

Framework Step1: Analyse Business Requirement

Apply Process Payout Resolve

Parents will apply for Handlers will access

Finance will
Allowances in Gov the application and
arrange payouts
Website process

The Child Care Allowance Application Process has four stages. First, in the Application
stage, parents apply online. Next, in the Processing stage, government employees
review and verify the details. If approved, it moves to the Payout stage, where financial
employees schedule the payment. Finally, in the Resolution stage, the process is
completed and archived.

6
1.1 Apply Stage (Persona: Parent / Applicant)
The Front-End Portal allows applicants, typically parents, to submit their applications for
childcare allowances. The process begins with User Authentication & Verification, where
the applicant logs into the system, and their details are verified. Next, in the Income
Information Collection step, the applicant provides household income details and
specifies income sources. Moving forward to Child & Daycare Selection, the applicant
selects the child(ren) for whom they are requesting the allowance and chooses a daycare,
with daycare data being fetched from an external system. The applicant then proceeds to
the Review & Confirmation phase, where they carefully review all entered information
before submitting the application. Finally, in the Application Submission stage, the
completed application is sent to the Government System for processing.

1.2 Process Stage (Employee)

In the Application Processing stage, a government employee verifies the applicant’s
details, ensuring all information is accurate and complete. If everything matches, the
application is approved, and the allowance amount is calculated. If any details are missing
or incorrect, the system generates a request for additional information. The applicant
must provide corrections, which the government employee reviews before making a final
decision.

7
1.3 Payment Stage (Finance Employee)
In the Financial Employee Processing stage, only approved applications are sent for
payment scheduling. The financial employee verifies the payment details and schedules
the payment. Once confirmed, the payment is processed and issued to the applicant.

After payment the case goings to an archive stage (This is out of scope for our live app
build).

Framework Step2: Identify common entities

8
2.1 Reuseable Entities for the entire program
RED Marked items are in scope

Entity Health Care Rent Childcare Child

Allowance Allowance Allowance Budget

Applicant X X X X

Income X X X X

Insurance X

Employer X

Child X X

Childcare X
Provider

Transaction X X X X

Bank X X X X
Account

This table illustrates the reusability of core entities across multiple allowance programs,
ensuring data consistency, reduced duplication, and efficient case processing in a
Pega-based system. By leveraging shared data models and modular design principles,
the system can maintain a scalable and flexible architecture, improving overall
governance, compliance, and operational efficiency.

The table presents an overview of reusable entities across different allowance

programs, specifically Health Care Allowance, Rent Allowance, Childcare Allowance,
and Child Budget. Each entity represents a data object that is either shared across
multiple programs or specific to certain ones.
• Entities such as Applicant, Income, Transaction, and Bank Account are used in
multiple programs, emphasizing reusability and modularity.
• Some entities, like Insurance and Employer, are only relevant to specific
allowances (e.g., Health Care and Rent Allowance).
• The Childcare Allowance column (marked in red) indicates which entities are in
scope for that program, including Applicant, Income, Child, Childcare Provider,
Transaction, and Bank Account.

9
Framework Step3: Identify common process

3.1 Reuseable Processes for the entire program

Reusable processes can be structured as modular components to enhance efficiency.
These include the Information Request module, which allows government employees to
request additional information from citizens, and the Payout module, enabling them to
arrange payments for citizens. Additionally, the Archiving module ensures compliance by
handling legal requirement-related document storage, while External Integrations
provide seamless connectivity with other systems through integration components.

10
Framework Step4: Validate Modularity & Application design

4.1 Collaboration Between Pega BA, LSA, and SSAs in Validating

Modularity
To build a modular and scalable Pega application, teams must validate modularity through
Design Thinking Workshops, ensuring alignment with business needs and best practices.
These workshops provide a structured approach to engage stakeholders, gather feedback,
and iteratively refine the system’s design. Pega Business Analysts (BA), Lead System
Architects (LSA), and Senior System Architects (SSA) play crucial roles in this process.
• BA leads the workshops, translating business needs into functional specifications.
• LSA defines the architectural blueprint, ensuring scalability, reusability, and
adherence to best practices.
• SSA focuses on technical feasibility, optimizing rule reusability, and maintaining
compliance with Pega’s guardrails.
During these sessions, teams showcase modular designs by breaking down applications
into reusable components, microservices, and case hierarchies, demonstrating how each
module interacts within the system. Actively incorporating stakeholder feedback helps
refine the design, ensuring a balance between business objectives and technical feasibility.
By fostering collaboration and continuously validating modularity, teams enhance
reusability, improve maintainability, and optimize performance—delivering a robust,
efficient, and future-proof Pega solution.

4.2 Design project architecture

Childcare Childbudget Rent Allowance Healthcare Business

Allowance Allowance Management Allowance application
Management management Management

Information Archieve Staff Employer Insurance

Request

Modules
Applicant Income Child Transactio Account
n

House Hold App Payment

Enterprise Layer Enterprise

E
11
4.3 Establishing Governance access various Pega applications

Without proper governance, Pega applications become inconsistent, unscalable, and

difficult to maintain, leading to duplicate rules, poor reusability, and performance
bottlenecks. Security risks increase due to unauthorized changes and lack of
compliance.
To establish governance in Pega modules, organizations must enforce standardization,
compliance, and maintainability through a structured framework. This includes defining
ownership by assigning clear responsibilities to Pega BAs, LSAs, and SSAs, ensuring
accountability in design and implementation.

12
About Swiftrinity
Intellectual Property Notice
Swiftrinity is a leading provider of
This document, including all course
cutting-edge solutions in the Pega
materials related to the Pega Constellation
ecosystem, specializing in workflow
course and its modular architecture, is the
automation, low-code development, and
intellectual property of Swiftrinity. The
AI-driven business process management.
content within this document is exclusively
With a strong focus on innovation and
owned by Swiftrinity and is protected under
expertise, Swiftrinity delivers high-
applicable intellectual property laws. Any
quality training, consulting, and
unauthorized use, reproduction,
technology solutions that empower
distribution, or modification of this material,
businesses to streamline their
in whole or in part, without the prior written
operations efficiently. Our Pega
consent of Swiftrinity's management, is
Constellation training programs are
strictly prohibited. Unauthorized usage may
designed to equip professionals with the
lead to legal action or other consequences
knowledge and skills necessary to
as deemed necessary by Swiftrinity. All
leverage the full potential of the
rights are reserved.
platform.

13