Object Oriented Software Engineering View all facts Glossary Help |
| subject > pattern > architectural pattern > pipe and filter |
| pipe and filter (transformational architectural pattern, transformational architecture) | ||||
| subject | fact | |||
| pipe and filter | has definition An architectural pattern in which data in a standard format is passed through a series of processes (filters) that transform it in some way | ![]() |
| facilitates designing for testability because it is normally easy to test the individual processes | ![]() | |
| has advantage the system can be modified easily by adding or changing the transformational processes | ![]() | |
| increases cohesion because the processes have functional cohesion | ![]() | |
| increases flexibility | ![]() | |
| increases reusability because the processes can often be used in many different contexts | ![]() | |
| increases reuse because it is often possible to find reusable components to insert into a pipeline | ![]() | |
| is a subtopic of 9.5 - Architectural Patterns | ![]() | |
| is a kind of architectural pattern | ![]() | |
| reduces coupling because the processes have only one input and one output, normally using a standard format | ![]() | |
| uses a pipeline | ![]() | |
| is a synonym of transformational architectural pattern | ![]() | |
| is a synonym of transformational architecture | ![]() | |
| architectural pattern | allows you to design flexible systems using components that are as independent of each other as possible | ![]() |
| pattern | should be as general as possible | ![]() |
| should be described in an easy-to-understand form so that people can determine when and how to use it | ![]() | |
| should contain a solution that has been proven to effectively solve the problem in the indicated context | ![]() |
Next architectural pattern: transaction-processing Up: architectural pattern Previous architectural pattern: multi-layer