The software operator is a design pattern. A design pattern describes the approach to cover the operational tasks of an application’s implementation. The first post in this series introduced the concept of a design pattern in general. The second post covers the software operator design pattern in particular.
In the second part, we also explained that a design pattern usually covers a discussion about consequences, advantages or disadvantages. After all, a “pattern” refers to an approach that has been applied multiple times. As a consequence, this experience should be written down to help software developers make informed decisions about which design to apply.
Design forces impact the eventual solution design and may be lead to an evaluation of multiple paths until the final solution is reached (photo credit: Marko Blažević)
This third installment in our series will discuss the “so called” design forces which motivate the pattern. A discussion of design forces…
