Guidelines have been updated 12/18/2017 based on a lot of feedback.

 

All the disclaimers still apply.  These are sample guidelines used by a real organization.  In most instances, these are meant to be served as template to be modified.  See the attached document.

 

Appendix F: Checklist for Compliance

The following checklist is use for compliance to this guideline.  The only requirement for compliance is that all the mandatory requirements be met.  Scoring is utilized as a quality assessment to measure maturity of an OPA implementation.

Scoring is as follow:

0 = Not in use

1 = Partially available and/or partially used by the project

2 = Available and in-use by the project

Quality Check

Analysis

OPA is being used for rule lifecycle management

T / F

Overarching policy outcomes are defined in OPA

T / F

Substantive OPA Policy Rules are reviewed by a lawyer and/or agency policy analyst

T / F

OPA is being used to assist in mining rules from source policy and/or legislation

T / F

The OPA project has separate roles for lawyer / policy analyst, OPA policy modeler, OPA interview designer, and OPA technical integrator / developer

0 / 1 / 2

OPA is being used for rule discovery and rule verification via analysis of existing data

0 / 1 / 2

OPA is being used to discover attributes needed by an application in determining outcomes

0 / 1 / 2

OPA is being used for impact analysis of rules

0 / 1 / 2

OPA substantive rules are primarily used to determine outcomes defined by Agency policy and/or legislation

T / F

OPA substantive rules need visibility by the business

T / F

OPA provides decision reports

T / F

OPA rules provide "temporal reasoning"

0 / 1 / 2

Substantive, procedural, and visibility rules are not combined

T / F

Traceability is provided from all substantive rules to source material

T / F

Substantive rules are in Natural Language

T / F

Rules are written to be read by non-OPA analysts

0 / 1 / 2

Production rules documents only contain operational rules

T / F

All OPA rulesets have a design document

T / F

OPA rules within a document are "on topic"

0 / 1 / 2

OPA only receives data originating from the rule consumer

0 / 1 / 2

OPA should determine outcomes for "I don't know" inferences

0 / 1 / 2

All Microsoft Word rule documents must have a TOC (Table of Contents)

T / F

Booleans attributes are never conclusions in word tables

T / F

Rules should not go deeper than level 3

0 / 1 / 2

Excel is used when source material is in a table, to implement rate tables, or there are multiple conclusions from the same conditions

0 / 1 / 2

All attributes must be properly parsable and parsed by OPA

T / F

Production projects can be debugged via the OPA debugger

T / F

Projects redefine "the current date"

T / F

All substantive policy conclusions have unit test cases

T / F

Projects have regression test suites

T / F

Projects plan OPA upgrades once per quarter

T / F

List Items are turned into boolean attributes before using them as conditions

0 / 1 / 2

An ability to regression test with production data has been implemented

0 / 1 / 2

An OPA quality checklist is utilized

T / F

Public names are created for integration / mapping with other applications

0 / 1 / 2

Public names follow a naming guideline

T / F

Entity's identifying attributes are provided

T / F

Entities and relationships are only created when the rules require them

0 / 1 / 2

Rule text should follow Oracle guidelines for entities, relationships, and attributes

0 / 1 / 2

Design and rule documents should contain description of relevant entities and relationships

0 / 1 / 2

Data saved from OPA can be re-loaded into OPA

0 / 1 / 2

Only the initial rules to determine an outcome should avoid effective dates via temporal logic

0 / 1 / 2

Rate tables should be temporal in Excel

0 / 1 / 2

Rules should not be deleted after they are used in production

0 / 1 / 2

Interviews are created with Accessibility warning level of WCAG 2.0 AA or better

T / F

Interviews have goals that support relevance of collected attributes

T / F

All policy determinations are available as web services

T / F

OPA "Relevancy" is used for all screens and attribute collection

0 / 1 / 2

Policy determination rules are developed prior to developing interview screens

0 / 1 / 2

All entities, personal attributes, headings, and labels have names substitution

0 / 1 / 2

Attribute text should not be changed on screens

0 / 1 / 2