Designing your decision management architecture (7.3)

Target users: Business analyst and business rules developer (citizen dev and java dev). See [https://drive.google.com/drive/u/1/folders/0B6cY6hNQRMMTSzJsVENXR0N4TFU|persona profiles] for details.

This document needs to walk the customer through this standard approach to conceptual architecture.

Tentative TOC: Online draft

Squad:

• Alex P. (eng)
• Mario, Matteo, Edson (eng)
• Tibor (QE)
• Marian (QE)

Links:

• Standard approach to conceptual architecture
• Pros-cons list of design considerations
• Drools community doc
• The 7 "Designing a decision service ..." docs in Customer Portal

Customer questions:

• Should I deploy my assets to KIE Server or to my own app server?
• Should I use remote execution on KIE Server or embedded execution of my assets on my own app server?
• Should I use Business Central or my own IDE?
• Which decision-authoring asset should I use?

-------

DEPRECATED:

1. Rule-authoring assets in DM/PAM
1.1. Guided rules
1.2. Guided rule templates
1.3. Guided decision tables
1.4. Uploaded decision tables
1.5. DRL rules
1.6. DMN models and support
1.7. PMML models and support
[Maybe the above?]
2. Considerations for decision service setup/design
2.1. Relationships (New)
2.2. Stateless vs Stateful KIE Sessions (Stateless KIE session, Stateful KIE session)
2.3 Inference
2.4. Methods versus Rules
2.5. Languages and Markup (drools, xml) (New)
2.6. Limitations
2.6.1. Limitations of FEEL
3. Decision asset examples for a project (New)

Links:

• Standard approach to conceptual architecture
• Pros-cons list of design considerations
• Drools community doc
  • Drools basics/user guide - Stateful/stateless, methods vs rules, etc.
  • DMN
  • PMML
  • Rule-authoring assets/concepts
• The 7 "Designing a decision service ..." docs in Customer Portal