A critical design decision in the object-oriented world is whether to choose cohesion or coupling.  These two approaches are not mutually exclusive.  However, it is rare to see a mix of the two.  Therefore, this decision in the architecture will profoundly impact the rest of the project. Big or Small, Cohesion or Coupling It helps to set the stage for this discussion.  The decision comes down to either building your system with small components or large (more full-featured) ones.  The result can range from microservices up to a monolithic class that stands alone.  A single object option is a cohesive approach, while coupling uses smaller classes that work together. Pros and Cons Each of these approaches has pros and cons. ... Read more

Object names and namespaces are just the beginning of creating a class architecture.  We need to consider globally available values, data hiding, abstraction, and how to group features.  The old “is-a” and “has-a” questions are essential cogs in building out this piece.  You will be looking for common pieces of data, methods, and how they should relate. A Goldie Locks Class Architecture It is incredibly easy to make your architecture too complex.  There is a broad range of “best practices” that try to provide the best general solution.  However, you are architecting a specific solution.  Thus, keep that in mind as you create the object architecture.  You should make every decision with supporting reasons for the related decisions.  The last... Read more