Software Development and Management

Pega's Dynamic Select feature enables cascading dropdowns where one field's choices depend on another field's value. When a Make is selected, the system dynamically filters and updates the available Model options based on that selection.

When rules in Pega are specifically designed to return boolean outcomes only - either true or false. Unlike decision trees, tables, and maps which can return various data types (strings, numbers, etc.), When rules are strictly boolean conditions used for conditional logic.

Declarative rules in Pega Process Commander (PRPC) automatically control when processing occurs based on conditions and changes. Examples include Declare-Expression, Declare-Constraint, and Declare-OnChange rules that trigger processing when specified conditions are met or when property values change. Decision tables and decision trees are rule types that execute logic but don't automate the timing of execution.

In Pega PRPC, harness rules are formally named Rule-HTML-Harness. Harnesses define the UI layout and structure for work object forms and other screens. The naming convention follows the pattern Rule-HTML-Harness where HTML indicates it's a markup-based rule and Harness specifies its purpose.

Decision shapes in flowcharts require a path for each logical branch, not for every possible return value. A decision typically has 2-3 paths (yes/no, or multiple mutually exclusive conditions) regardless of how many distinct values the processing might produce. For example, a decision checking 'is x > 0' has two paths (yes/no) even though x could have infinite possible values.

Meeting customer needs is the primary design consideration because applications exist to solve specific user problems. Without addressing actual user requirements, even highly scalable, maintainable, reliable, or performant applications fail to deliver value. While all the other factors (scalability, maintainability, reliability, performance, budget/timeline) are important considerations, they are secondary to ensuring the application fulfills its intended purpose for the customer.

The suggested architecture (3 web servers, application server, database server on separate machines) creates a three-tier model with thin clients (browser-based interface), good separation of business logic (application server layer isolates business rules), and good scalability (each tier can be scaled independently). This contrasts with fat clients where business logic resides on client machines, which would create poor separation and poor scalability.

Vertical scalability involves adding resources like CPU, memory, or storage to a single machine rather than adding more servers. It typically requires minimal architectural changes since you're upgrading existing capacity rather than redesigning for distributed processing. However, it has limits compared to horizontal scaling.

While 3-tier architecture improves separation of concerns and can enhance scalability, it also introduces complexity. More tiers mean more components to deploy, configure, monitor, and maintain, which can lead to poorer manageability compared to simpler 2-tier architectures.

N-tier applications can show better performance than 2-tier applications because their modular nature allows individual components and containers to be tuned and scaled independently. While performance depends on implementation, the architectural flexibility provides optimization opportunities that monolithic 2-tier systems lack.

Thick clients require software installation and updates on each user's machine. When UI changes are made, they must be packaged and redeployed to all clients - a complex, time-consuming process. In contrast, web-based applications update instantly on the server. Option D describes an advantage of web/thin clients, which by comparison is a disadvantage of thick clients.

Routers can be attached to Assignments in Pega. They determine which path a flow takes based on conditions. While some other shapes might have routing logic, routers specifically attach to assignment shapes.

Professional floor planning and space optimization enterprise applications utilize standardized, fixed user interface structures. While users can customize the floor plans, fixtures, and layout designs, they cannot modify or customize the software's built-in application screens or UI layout.

Events are not a core UML construct; they are state machine diagram elements, not general UML concepts. Actors (roles external to the system), Use Cases (system functionality), and Stakeholders (people with interests in the system) are all fundamental UML modeling elements.