Some components and connector types

Indicate how the system combines components and connecting parts

Each processing step is a separate program

Each step must start after the previous step is finished

The data must be complete and delivered as a whole

Basic components

Connectors

Suitable for scenarios where large amounts of data need to be processed and periodic and low real-time requirements are not high

The system divides several sequential processing steps to process the data generated continuously.

The steps are connected through a data stream, and the output of one step is the input of another step

Data transmission is completed by pipelines, and processing steps are implemented by filters

Basic components

Connectors

Data flow scenario

Generally, single-thread control is used to divide the problem into several processing steps

member

Connectors

Data representation method and corresponding operations are encapsulated in an abstract data type or object

member

Each layer provides services to the upper layer and serves as a customer at the lower layer.

The layer interface is only visible to the adjacent layer

Based on resource ambiguousness, it is proposed to realize sharing

Two-layer C/S architecture—"fat client, thin server"

Three-layer C/S architecture—"thin client"

The various components of the system interact through a central data (i.e., warehouse).

member

Connectors

A problem-solving model

Conceptual framework for domain knowledge organizing inference steps, controlling state data and problem solving

blackboard

Source of knowledge

Control module

Solve the unstructured problem of responsibility

Explanation Engine

Storage area

Data structure

Often used to build a virtual machine to bridge the difference between program semantics and hardware semantics

Deduce conclusions or perform actions through a set of rules

Rule Set

Rule Interpreter

Rules/Data Selector

Working memory

member

Connectors

The component does not directly call a process, but triggers or broadcasts one or more events.

Procedures in other components, registered in one or more events

When an event is triggered, the system automatically calls all procedures registered in the event