Issue 15140: ComputerExecutableRuleset should have Reference and Modifies associations with Class
Issue 15141: RuleCondition RuleAction and RuleVariable should have Reference and Modifies associations with Class
Issue 15142: PRR Relationship with RIF, typo and compliance
Issue 15260: Example from Annex F in SBVR Structured English
Issue 15140: ComputerExecutableRuleset should have Reference and Modifies associations with Class (prr-rtf)
Click here for this issue's archive.
Source: TIBCO (Mr. Paul Vincent, pvincent(at)tibco.com)
Nature: Clarification
Severity: Significant
Summary:
In implementations of PRR in a UML tool, it has been found that rulesets (as well as rules) should be able to reference and modify a Class. This should be at the ComputerExecutableRuleset level per Figure 7.1. This should not impact any current implementations by adding this.
The modelling of PRR would be enhanced by being able to report or visualise Classes that are impacted by rules in models by associating RuleCondition (reference), RuleAction (reference, modify), and RuleVariable (reference) to Class.
1. pg iii has a capitalisation in the index which is a typo (RElationship instead of Relationship) 2. Annex D covers the relationship between PRR, and OMG standard, and W3C RIF. This should be updated with the latest information on RIF PRD and PRR-RIFPRD compliance.
As a demonstration on an SBVR project, I wrote a version in SBVR Structured English of the example in PRR Annex E, pages 58 - 65. It was suggsted at a PRR meeting that it could be useful as an alternative view of the example, and might be included as an additional annex (or perhaps included in Annex E). It is contained in a separate document.