Pipeline of Activities
In this chapter, the set of activities that must be performed to move a business process from one state to another is defined as a pipeline.
Pipeline of Activities
Let's look again at the example from the previous chapter, “Business Process Activities”:
As we have learned, several different types of logic interact with each other in a specific sequence to support a “Verify health card validity” transition that begins with the “Initial” state of the “Person Identification” use case. A particular type of logic may or may not be present in a particular sequence that supports a particular transition. For example, in the above diagram, no activity is required at the Data Processing Logic because all it does is simply pass a request to the next logic and return a response from it to the previous logic. Even though in this case there is no need for Data Processing Logic, the request must somehow be transferred from Business Logic to Data Access Logic. And this is the responsibility of the pipeline.
A pipeline is a sequential collection of placeholders, in which each placeholder is dedicated to a specific type of logic, which may or may not be represented, and in which activities specific to the presented logic occur :
State Logic is a required component of the pipeline because this is where any transition begins. The remaining components are optional and can be presented in any combination.
The following diagram shows the pipeline for the “Verify health card validity” transition example above, where Data Processing Logic is not present. In this case, the pipeline passes the request from the Business Logic directly to the Data Access Logic and passes the response from the Data Access Logic back to the Business Logic:
