When designing an application, does any such issue occur where you have too many objects? How do you determine that when you cross the granularity line in your object model?
I think you type and not objects (I know this is called an object model But it is actually a model of the types involved).
However, if you subscribe to single liability theory, it has been said that each type should handle only one responsibility, as the application progresses, the number of types will increase.
However, due to its limited size, it should be quite easy to understand and assuming that you have some type of structure, you rarely (if ever) all kinds of methods One should look at the time.
Everything about managing large software projects is about sharing things in manageable pieces and labeling in a sensible way. If you do this, the number of types becomes less important in my experience.
Comments
Post a Comment