[jboss-svn-commits] JBL Code SVN: r13260 - labs/jbossrules/trunk/documentation/manual/en/Chapter-BRMS.

[jboss-svn-commits at lists.jboss.org]

Author: michael.neale at jboss.com
Date: 2007-07-09 03:34:41 -0400 (Mon, 09 Jul 2007)
New Revision: 13260

Modified:
   labs/jbossrules/trunk/documentation/manual/en/Chapter-BRMS/Section-UserGuide.xml
Log:
JBRULES-688 user guide update

Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-BRMS/Section-UserGuide.xml
===================================================================
--- labs/jbossrules/trunk/documentation/manual/en/Chapter-BRMS/Section-UserGuide.xml	2007-07-09 07:20:20 UTC (rev 13259)
+++ labs/jbossrules/trunk/documentation/manual/en/Chapter-BRMS/Section-UserGuide.xml	2007-07-09 07:34:41 UTC (rev 13260)
@@ -323,7 +323,7 @@
             <para>A</para>
 
             <para>This is where the "editor widget" lives - exactly what form
-            the editor takes depends on the asset or rule type. </para>
+            the editor takes depends on the asset or rule type.</para>
           </listitem>
 
           <listitem>
@@ -378,7 +378,7 @@
             <para>F</para>
 
             <para>This shows what package the asset belong to (you can also
-            change it from here). </para>
+            change it from here).</para>
           </listitem>
 
           <listitem>
@@ -524,6 +524,30 @@
 
   <section>
     <title>The business user perspective</title>
+
+    <para>You can see from this manual, that some expertise and practice is
+    required to use the BRMS. In fact any software system in some sense
+    requires that people be "technical" even if it has a nice looking GUI.
+    Having said that, in the right hands the BRMS can be setup to provide a
+    sutiable environment for non technical users.</para>
+
+    <para>The most appropriate rule formats for this use are using the Guided
+    editor, Decision tables and DSL rules. You can use some DSL expressions
+    also in the guided editor (so it provides "forms" for people to enter
+    values).</para>
+
+    <para>You can use categories to isolate rules and assets from non
+    technical users. Only assets which have a category assigned will appear in
+    the "rules" feature.</para>
+
+    <para>The initial setup of the BRMS will need to be done by a
+    developer/technical person who will set the foundations for all the rules.
+    They may also create "templates" which are rules which may be copied (they
+    would typically live in a "dummy" package, and have a category of
+    "template" - this can also help ease the way). </para>
+
+    <para>Deployment should also not be done by non technical users (as
+    mentioned previously this happens from the "Package" feature).</para>
   </section>
 
   <section>