-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,23 @@ | ||
# Pipeline | ||
|
||
```mermaid | ||
classDiagram | ||
class AbstractPipeline | ||
class Pipeline | ||
class PipelineStep | ||
Pipeline--> "*" AbstractPipeline | ||
Pipeline..|>AbstractPipeline | ||
PipelineStep..|>AbstractPipeline | ||
``` | ||
|
||
For the pipeline definition, we use a composite to allow us to have a multi-level pipeline. | ||
As such, a pipeline consists of an arbitrary number of either *PipelineStep*s or further *Pipeline*s. | ||
|
||
In our approach, we use three levels for our pipeline: | ||
On the first level, the overall pipeline defines multiple *stages*, e.g., text preprocessing or element connection. | ||
Each stage is another pipeline that then defines *agents* that have the purpose of initiating the processing and of collecting the information of the various heuristics. | ||
Agents then use *Informants* as concrete PipelineSteps to execute the processing and heuristics. | ||
|
||
A pipeline step (i.e., an Informant) stores results within a repository that can be universally accessed by all pipeline steps, similarly to a blackboard in the blackboard pattern. | ||
This way, each pipeline step and, thus, each heuristic can access the results of previous steps and provide its results for others. |