For developers, maintaining a shallow object model with generic class templates has presented itself as critical. One primary goal of this project as it was developed was to eliminate "spaghetti code" at the form level, where
one control's event code changes data in another control, which changes another control, etc. Code like this is unmaintainable and easily broken. Generic, reusable class templates and a shallow object model has lent itself to avoiding this problem.
In the end, this same "chain reaction" of control updating can still be employed, but rather than having to follow a trail of event updates through a variety of subroutine calls, some of which may unintentionally trigger other events, one class encapsulating
the composite control interactions manages this, allowing the developer to determine the order in which control updates take place.