<div dir="ltr">Hi Mark<br><br> I went through the RuleAnalytics Module document. It looks like there is a good compatibility between your visions of Rule Analysis and our rule dependency generation work. I'll be excited to further develop and integrate my work with drools-verifier module code. <br>
<br>Just a short summary of how I had approached the problem:<br><br>We have long ruleflow which consists of other ruleflows, ruleflow groups, split conditions. Using drools API I was<br>able to traverse through the main ruleflow including (recursively) constituent nodes. So at any node I knew which rules<br>
are relevant. Now, to find out dependency between rules I required very intricate information about any given rule. I could not <br>find sufficient drools APIs to get this information. There are methods to get LHS and RHS of a rule but they do not give information about individual attributes. For RHS its more worse. No textual information was availabe about it. (I am using 4.0.7 and I had even posted my questions on Drools user mailing list)<br>
<br> As a result, I wrote my own .drl file parser using javacc (which was very interesting to do) and got whatever information I required.<br>Now I knew which rule modifies which attribute (and of which class) and which rule uses what atrributes in its conditional part. Its much easier to get dependecy sequence now. I know a few cases where this approach might produce a false dependency sequence but using other rule-flow(salience, agenda) information can help us avoid that.<br>
<br>Now, how shall we go about it? I have installed irc on my system and I think I require some url to be able to connect to you guys.<br><br>Siddharth<br><br><div class="gmail_quote">On Sun, Oct 5, 2008 at 7:40 PM, Mark Proctor <span dir="ltr"><<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Drools 5.0 has the drools-verifier. This does a variety of verifications and analysis, like where class fields are used, gap analysis etc. The Guvnor BRMS can produce HTML reports for this information. Subsumption isn't done yet, we needed to analys the consequences for update/modify to try and detect potential impacted rules - this is also needed to detect which rules depend on other rules.<br>
<a href="http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-verifier/" target="_blank">http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-verifier/</a><br>
<a href="http://wiki.jboss.org/wiki/RuleAnalyticsModule" target="_blank">http://wiki.jboss.org/wiki/RuleAnalyticsModule</a><br>
<br>
So we would love to have your work as additions to this, but it will need to be integrated with the existing drools-verifier module code and the HTML reporting - can you make that happen? It would be ideal, as it then means your code is part of the main project and will be maintained and improved by the community.<br>
<br>
Maybe you could pop onto irc, and chat to us about it more?<br>
<a href="http://www.jboss.org/drools/irc.html" target="_blank">http://www.jboss.org/drools/irc.html</a><br>
<br>
Do you have any visualisation plans? If on the web GWT-Diagram is turning out to be a great tool<br>
<a href="http://code.google.com/p/gwt-diagrams/" target="_blank">http://code.google.com/p/gwt-diagrams/</a><br><font color="#888888">
<br>
Mark</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
Sangrish wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi<br>
<br>
I have been using Drools Rules Engine in our application for past<br>
couple of weeks.<br>
One of the requirements in our project was to let a user (anyone who is<br>
writing/analysing the rules) find out<br>
what other rules a given rule depends upon. There were a few kinds of<br>
dependencies:<br>
1) Object Attribute dependency: The attributes of an object being used in<br>
the conditional part of a rule<br>
might be getting modified in the consequence part of another rule. We<br>
wanted all such rules with each rule having its own dependency list.<br>
2) Rule Salience based dependency. A rule having lower salience should be<br>
executed only after a higher (if any) salience rule has already been<br>
executed.<br>
3) Dependency caused by a specific Rule flow. Rules in a ruleflow group<br>
should be executed only if (if any) Split condition gets satisfied.<br>
4) Agenda flow dependency (i.e., one agenda following another) <br>
We could not find much support for this in the Drools API. Hence we<br>
decided to write our own dependency generator. The tool we are writing<br>
caters to first 3 dependencies. We might even handle the 4th one. Since Drools is open source, we thought of contributing our bit towards<br>
its development. If the drools team wants I can happily work with them on<br>
getting this functionality plugged in the Drools system.<br>
<br>
<br>
Thanks<br>
Siddharth<br>
<br>
</blockquote>
<br></div></div><div><div></div><div class="Wj3C7c">
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</div></div></blockquote></div><br></div>