In practice various frequent decoupling scenarios exist. These scenarios can be categorized as follows:

  1. Calling/exposing domain functions to application
  2. Persistence of data
  3. Calling/exposing a webservice
  4. Showing data to customer facing applications
  5. Calling/exposing application functions

For every category examples exist of various complexity. We intend to cover examples of various complexity.

Each elaborated example is strongly supported by these theoretical principles and constraints:


In the practical examples are the theoretical principles applied, and these ultimately lead to modelling patterns withing Blueriq. This is shown schematically below.

 

 

 

Examples

In the table below an overview of the available examples is shown.

 

Decoupling category

Simple example

(S)

Complex example

(L)

Calling/exposing domain functions to application (1)

Calculation

Housing policy

Persistence of data (2)Persistence data (read/write)

Municipality Value List

Showing data to customer facing applications (4)

Input validation

Intelligent dialog for problem diagnosis
Calling/exposing application functions (5) Changing Personal Information

The following examples concern knowledge automation and decision management:

Cross-Cutting Concern Example

Some concerns are called cross cutting as it plays a role in any layer of the architecture. Well-known examples include security and performance. As these concerns play the same rule in Blueriq, an examples has been prepared concerning security.

User permission

 

  • No labels