Hello all,
Are there any problems/points that should be considered when a class
is being used from too many places in project?
Is there any complexity measure associated with class overuse ?
Regards
Arjang Assadi
Depends. Is it doing the same job, or many jobs?
On 21 April 2010 13:27, Arjang Assadi arjang.ass...@gmail.com wrote:
Hello all,
Are there any problems/points that should be considered when a class
is being used from too many places in project?
Is there any complexity measure associated with
Here's a few issues you might want to consider:
* Application brittleness: Changes to that one class can affect large
portions of the applications.
* God object: If this class is available from everywhere then it's tempting
to dump methods/properties in there that don't relate to it's core
Thank you Preet and Micheal,
Assuming it is not a god class and has a very specific responsibility and
furthermore it is been used throughout the project very often.
Is there such a thing as over dependency/over use?Are there any
problems with when too many classes depend/rely on few
Can you be a little more specific about what this class does? Are you
actively concerned about something in particular or just generally concerned
that so many area rely on it? Is it core logic or is it a utility bag of
some kind?
If its role is very well defined and its implementation must
] On Behalf Of Arjang Assadi
Sent: Wednesday, 21 April 2010 10:11 AM
To: ozDotNet
Subject: Re: Persils of overusing a class?
Thank you Preet and Micheal,
Assuming it is not a god class and has a very specific responsibility
and
furthermore it is been used throughout the project very often
