Derivation rules are used to create symbolic representations using other symbolic representations. As such they do not reflect business objects or activities, only their representations, and can therefore be managed at will.
Derivation mechanisms can be applied to any symbolic representation:
- Derived attributes, whose values are computed using native values.
- Derived connections, which are built as shortcuts of native ones.
- Derived objects, which are views defined on native objects.
- Derived activities, which analyze native representations.
- Derived states, which reflect native states.
- Derived events, aka cascade, which are instant replicas of actual ones.
Since their footprint is circumscribed to symbolic representations (i.e system objects), derivation rules have no direct impact on couplings between systems and contexts. As a consequence, their implementation can be singled out and dealt with independently of the architecture. That may be especially useful for business rules managed according business opportunities.