What term describes the classes that make up an application in Pega?

The term that describes the classes that make up an application in Pega is class hierarchy. In Pega, a class hierarchy is essential for organizing the various classes that represent different elements of the application's domain. The class hierarchy establishes an inheritance framework, where subclasses can inherit properties and behaviors from parent classes, promoting reuse and reducing redundancy.

Understanding class hierarchy is crucial in Pega development, as it allows developers to define and manage complex business processes efficiently. When designing an application, developers create a structure of classes that can encapsulate specific functionalities, making it easier to maintain and evolve the application over time.

The other concepts, while related to application architecture in Pega, do not specifically refer to the organization of classes. For instance, class structure would typically refer to the specifics of how individual classes are defined and organized, but it does not encompass the overall hierarchical relationships. An application framework might describe a broader set of components and guidelines for building applications but lacks the specific focus on the class relationships. The service layer relates to the aspects of backend processes that enable communication and integration with external systems, not the internal class organization within the application.