Sentence examples for rules repository from inspiring English sources

The chapter explains the basic business rules repository (BRR) design for relationships, pathways, and subtypes.

The chapter provides the concept of enriching the business rules repository (BRR) with metadata relevant to the business.

The first step is to design the main entity to hold column information in the business rules repository (BRR).

Although the referential integrity rules can be derived from the metadata in the business rules repository (BRR), the design presented opens them up to users for viewing and updating.

The chapter also adds to the richness of metadata in the business rules repository, which positions engineers to do additional administrative functions, such as determining what version of a rule is in force when a particular piece of data is populated.

Optimization Rule Repository stores optimization rules which detail relevant parameters for each optimization type.

Figure 1 describes the architecture of OCSO including its five components, namely Optimization Gateway, Optimization Facilitator, Optimization Executor, Optimization Rule Repository, Logging and Notification Controller, as well as their data and process dependencies.

These objectives are achieved through the enhancement of the rule repository schema with information on the logistics of the collection process and references to underlying enterprise informational and behavioural knowledge models.

Reports for medication rules are generated separately using another user interface connected to the rule repository.

It focuses on the critical case of anti-fraud rule repositories for the inspection of Card Not Present (CNP) transactions in e-commerce environments.

While physical sharing of the separate rule repositories could theoretically be implemented in their current format, this could quickly become a complex task due to the diversity of representation models and terminologies.