| Pattern Name | Pattern Intent |
|---|
| Connection |
Decouple data-processing application components from the source from which they take their inputs and from the destination to which they write their outputs.
|
| Control Block |
Decouple the implementation of data-processing algorithms from their management. |
| Event |
Allow application components to create and share reports describing synchronous or asynchronous occurrences
together with any data associated to them.
|
| Finite State Machine |
Decouple the implementation of the state-dependent behaviour in a FSM from the management of the states and the state transitions and decouple the clients responsible for triggering state transitions from the FSM implementation.
|
|
Manager
|
Provide a solution to the problem of managing
a functionality that requires the same actions to be
repeatedly performed on a class of components providing different
implementations of the functionality itself.
|
| Manoeuvre Management |
Decouple the management of manoeuvres from their implementation.
|
|
Mode Management
|
This design pattern addresses the problem of endowing components with mode-dependent behaviour. It separates the implementation of the mode-dependent behaviour from the implementation of the logic required to decide mode switches.
|
| Operating System Interface |
Decouple the OBS application from the operating system upon which it is running.
|
|
Parameter Database
|
Decouple the use of database parameters from the physical representation of the on-board database and allow access to the database parameters using symbolic identifiers.
|
|
Punctual Action
|
Offer a solution to the problem of encapsulating, performing, and managing generic
punctual actions.
|
| Recovery Action |
Decouple the management of individual failure recovery actions from their implementation by allowing recovery actions to be manipulated as abstract entities independent of the specific recovery actions they implement.
|
|
Reconfiguration Management
|
Decouple the use of a redundant functionality from the management and implementation
of the redundancy switching logic.
|
| Shared Data |
Decouple the production of data from their consumption.
|
|
Telecommand Management
|
Decouple the management of telecommands from their implementation and from the data source from which they are loaded.
|
| Telemeterable |
Decouple the collection of the telemetry data to be provided by an object from their content and format.
|
|
Telemetry Management
|
Decouple the management of telemetry from the format and layout of the telemetry data and allow the development of an application-independent telemetry manager.
|
| Telemetry Stream |
Decouple the process of forwarding telemetry data to the ground from the characteristics of the physical channel over which the data are sent.
|
| Telemetry Item |
Decouple the collection of a set of Telemetry Items from the content of these Telemetry Items.
|
| Trace |
Decouple the signaling of trace events from the implementation of the interface to the trace test set.
|
| Variable Monitoring |
Decouple the monitoring of the value of a variable from the time profile against which the monitoring is performed.
|