Designing cases using aggregates [editor]

As show above, a case is a concept that combines many other concepts. A case always has a goal (most likely a single goal). in order to reach that goal, decisions are made, in one or more processes. A case goes through phases, where a phase changes done formally by means of a milestone. A case can have different states, even more at once. Information is persisted within a case or outside of a case, because of a case. Within cases, some tasks are not really part of the main or other processes, but can always be executed. Such generic tasks are part of the case as well. Notes and appointments are similar to generic tasks, they are part of the case an are probably available throughout the life cycle of a case. Triggers can lead to actions that need to be performed in a case. Case will most likely contain uploaded documents and will generate documents themselves as well. Cases are about collaboration; people can be involved and team, organizations and roles can be defined.

All afore mentioned concepts contribute to a case, but that does not mean that each case has to consist of all these concepts necessarily. However, most (or even all?) cases contain decisions, will have at least one process and will most likely store some data and/or produce a document.

Blueriq concept of a case

With Blueriq's proposition of Dynamic Case Management, many DCM concepts are available. However, not all concepts can be found in the software platform as a Blueriq-concept. Shown below is the same image containing a case and all its related concepts. The concepts in blue deviate; this means that the DCM concept itself is not available within the platform as such, but one or more Blueriq concepts are used to model the DCM-concept effectively.

In the diagram above, all pink concepts are DCM concepts that are part of Blueriq by default. The concept of decisions is probably the most dominant one, but also processes, persistency and documents are used in many - if not all -  Blueriq applications. Teams and roles may not be as common as decisions, but are used frequently.

The blue concepts in the diagram above indicate DCM concepts that are not available within the platform as a module element, but can be modeled using out-of-the-box Blueriq functionality. For instance the goal of a case and milestones and states; they can all be modeled using decisions, most likely decision tables or business rules. Notes and incoming documents can be modeled using specific containers. For triggers incoming message events can be used. Appointments, involvements and organizations can be modeled by attributes.

The most protruding blue icons are that of the case and related cases; aggregates are used to model cases. This means that not only standard persistency by means of registers is done using aggregates, but also the case itself is an aggregate! Not all aggregates are cases, but all cases are aggregates.

Comparison

The table below compares all DCM concepts with Blueriq concepts and briefly explains how standard Blueriq concepts can be used to model the DCM concept, if applicable.

Concept DCM		Concept Blueriq		Remarks
	Case		Aggregate
	Goal		Decision
	Decision		Decision
	Process		Process
	Milestone		Decision
	Phase		Process
	State		Decision
	Persistency		Aggregate
	Generic task		Process
	Related case		Aggregate
	Note		Comment container
	Appointment		Attribute(s)
	Trigger		Incoming message event
	Document input		File upload container
	Document output		Document
	Involvement		Attribute(s)
	Team		Team
	Organization		Attribute(s)
	Role		Role

See also

More information on how to design dynamic processes in Blueriq can be found here: Designing dynamic processes.
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.
Specifically for dynamic case management and persistency management, see