http://jtonedm.com/2008/06/30/first-look-corticon/ James Taylor on Everything Decision Management Sat, 20 Mar 2010 01:10:43 -0700 http://wordpress.org/?v=2.9.2 hourly 1 http://jtonedm.com/2008/06/30/first-look-corticon/comment-page-1/#comment-14461 Making complex policies visual for the web » JT on EDM Wed, 01 Jul 2009 21:51:40 +0000 http://jtonedm.com/?p=485#comment-14461 [...] kind of interactive/reflexive questioning that rules vendors are adding to their products (notably Corticon, Blaze Advisor and Idiom). In both cases it seems to me that an opportunity exists for more [...] [...] kind of interactive/reflexive questioning that rules vendors are adding to their products (notably Corticon, Blaze Advisor and Idiom). In both cases it seems to me that an opportunity exists for more [...]

]]> http://jtonedm.com/2008/06/30/first-look-corticon/comment-page-1/#comment-10708 First Look - IDS Scheer ARIS Business Rule Designer » Smart (Enough Systems, the blog) Fri, 08 Aug 2008 16:11:50 +0000 http://jtonedm.com/?p=485#comment-10708 [...] The product is designed to let you specify rules at a reasonably high level - against a business vocabulary rather than a detailed object model. The intent is to keep business designers at a conceptual level - once they have a good model of their process then they can model explicit decision making in a declarative way. The primary interface for this is decision tables, chosen both for being intuitive and for their easy support for branching and parameter-based logic (important in a process). The vocabulary against which the rules are written is modeled as a UML diagram or an Entity Relationship Diagram. A vocabulary model can then be automatically generated out of these data models. The interface used to model decision tables also allows capturing rules in natural language syntax. It is designed for supporting capturing business rules while they are still at an early stage of specification. The underlying components (rule engine) of the decision modeler are from Corticon’s product (as I discussed before). [...] [...] The product is designed to let you specify rules at a reasonably high level – against a business vocabulary rather than a detailed object model. The intent is to keep business designers at a conceptual level – once they have a good model of their process then they can model explicit decision making in a declarative way. The primary interface for this is decision tables, chosen both for being intuitive and for their easy support for branching and parameter-based logic (important in a process). The vocabulary against which the rules are written is modeled as a UML diagram or an Entity Relationship Diagram. A vocabulary model can then be automatically generated out of these data models. The interface used to model decision tables also allows capturing rules in natural language syntax. It is designed for supporting capturing business rules while they are still at an early stage of specification. The underlying components (rule engine) of the decision modeler are from Corticon’s product (as I discussed before). [...]

]]>