Application development best practices

In the following example, UplusBankDev version 08.02 represents the development Application Layer that developers use to improve the application. The UplusBankTests version 08.01 is the test layer that contains the test automation assets required to run Automated tests. The UplusBankTests application is locked to prevent any unintended changes. In turn, the UplusBank version 08.01 is the production application.

The following figure shows a recommended application structure that includes different layers:

• Development layer: The development layer is where the development team uses development applications to manage features that are in progress.
• Test layer: Applications such as UplusBankTests version 08.01 contain automated test assets for unit and scenario testing. These applications are locked to prevent unintended changes.
• Production (target): The primary application deployed to production. Keep this application locked to prevent unintended changes.
• PegaDevOpsFoundation: The PegaDevOpsFoundation application is a component of the Deployment Manager service that enables integration between Deployment Manager and the route to live (RTL) environments.

In the following image, click the + icons to learn more about the development and test layers:

The Branch quality tab in Dev Studio helps you track the quality metrics of your branch.

Monitor the status of your Branch to detect and address potential problems early and support a smooth merge process. The data refreshes each time you open or refresh the dashboard.

For more information, see Branch quality monitoring.

In the following image, click the + icons to learn more about the different branch quality metrics that you can use to analyze the quality of your branch:

The Application Quality dashboard in the Pega Platform helps you track the health of your application throughout development. The dashboard highlights areas in the application that need improvement. The Application Quality dashboard provides a clear and efficient way to validate your application and identify potential issues early.

The dashboard displays metrics commonly used during application development, including numbers, percentages, scores, and severity indicators. Use the dashboard to investigate violations, resolve issues, and improve application quality.

In the following image, click the + icons to learn more about the metrics on the Application Quality dashboard:

During parallel application development, developers frequently integrate their changes with updates from other team members. To ensure successful merges, each change must:

• Meet application quality standards.
• Be compatible with existing functionality.
• Avoid conflicts with other developers' changes.

To meet these criteria, developers work in Branches and merge their changes to the base application. For more information, see Best practices for branch-based development.