Reusable

A software component is described as reusable if it supports a general-purpose function or process. The business benefit is a greater return on the initial investment of creating, testing, and documenting the component.

PRPC offers multiple facilities to promote reusability, such as

• Class inheritance — Rules that apply to more general (higher) classes are also available for lower (derived) classes. This is a major benefit of object-orientation.
• A library of standard rules — Thousands of standard rules, including flows, flow actions, properties, HTML rules, and others are available for your use.
• Subprocesses — Because one flow can start another, you can create common flows once and call or branch to them (with the Subprocess shape or ) from multiple other places.
• Organizational hierarchy — Access groups are associated with both organizations (Data-Admin-Organization class) and divisions (Data-Admin-OrgDivision class).

A RuleSet is termed "application reusable" if two unrelated businesses with similar operations can use the capabilities it provides. For example, an interest-rate calculation for mortgages is the same for all mortgage issuers.

A RuleSet is considered "organizationally reusable" if two divisions or other elements of a single organization can use the capabilities it provides. For example, a binary file image containing the company logo is valid for all the divisions of one business, but not valid in other organizations.

inheritance, standard rule, subprocess

Definitions — R