Page History
Target operating model
Within the design phase, one of the most important artifacts is the target operating model (in Dutch: bedrijfsfunctiemodel). Shown below is an abstract version of such a target operating model.
A target operating model is a model that describes the situation that is intended to achieve by means of the application(s) that are part of the entire solution. Some might use the term SOLL for this, with its counterpart IST for the current situation. The target operating model allows to scope, since it is not necessary to only describe elements of the solution that is desired now, but also include elements that are wanted or desired, but are left out of scope for the next release of the solution. Scoping is done using different colors, elements in pink are in scope of the intended solution, elements in grey are not.
The target operating model contains 7 groups:
- Roles
- Channels
- Control
- Primary functions
- Knowledge functions
- Secondary functions
- Information
Cases and registers
Bla bla
See also
More information on how to design dynamic processes in Blueriq can be found here: Designing dynamic processes.
How aggregates are used to model cases can be found here: Designing cases using aggregates.
Everything about persistency management and aggregates can be found here: Persistency Management guide.
A visualization of most concepts discussed in this article can be found here: Blueriq visuals.