The execute around functional design pattern is used when processes have pre- and post- processing that always occur. This allows us to focus on the core function and not on the processing that comes before or after. The pre- and post-processing code can exist once, instead of being part of each core process. This can result in a big win.
Consider a system with hundreds of individual classes that are run on an ad hoc nature based on business logic. Instead of each of those hundreds of processes including the pre- and post-processing code, that code can be located in one class.
The pre- and post-processing actions are paired and included in the object that requires those actions. This is done instead of including those actions in a class that uses the object. So, we are including the actions in the object itself, not in a class that...
