Re: Separation of concerns

On Mar 28, 8:01 am, "Thomas Kowalski" <t...@xxxxxx> wrote:
Hi everyone,
I am currently quite confused about the separation of concerns things
and search here for enlightenment.
I have some classes. lets say A and B that shall implement a certain
interface (e.g. Drawable).
Now it would not be very nice if A and B would implement then directly
or?
Should I subclass like A_Draw and B_Draw or what is the current
pattern to solve this?

Thanks a lot in advance,
Thomas Kowalski

"Separation of concerns" is a buzz-word that so far has very little
consistency and rigor. Plus, in reality it is hard to separate
everything because real-world apps have to model real-world
relationships, which are often intertangled by their nature. Often
there is a tradeoff between separating one factor at the expense of
another. It is rarely a free lunch.

Further, sometimes heavy separation creates beurocratic software. You
have to weigh tradeoffs using experience. It is relatively easy to get
software to work without experience, but experience is necessary to
future-proof software (or at least make it reasonably maintainable).

My advice is to keep an eye on potential future change, but keep it
simple. If you don't keep it simple and a future change comes along
that you failed to anticipate (you guessed the wrong kinds of
changes), then software is often harder to change than if you didn't
do any future-proofing but kept it simple. Thus, it is ofter more
benefitial to ponder how to obtain simplicity than to ponder what to
isolate for estimated future changes. Isolation is like a rifle, where
simplicity is like a shot-gun: you don't have to aim at the future as
accurately to get benefits from simplicity.

-T-

.

Relevant Pages

  • Re: Separation of concerns
    ... I am currently quite confused about the separation of concerns things ... If you don't keep it simple and a future change comes along ... isolate for estimated future changes. ... simplicity is like a shot-gun: you don't have to aim at the future as ...
    (comp.object)
  • Re: Separation of concerns
    ... I am currently quite confused about the separation of concerns things ... If you don't keep it simple and a future change comes along ... isolate for estimated future changes. ... simplicity is like a shot-gun: you don't have to aim at the future as ...
    (comp.object)
  • Concern Management (Re: Mountains or Molehills)
    ... I believe that "separation of concerns" is an unrealistic goal. ... and thus they need to interweave somehow in software also. ... The idea is influenced by relational queries that can see the ... We need to learn to manage our view of concerns, not try to isolate ...
    (comp.object)
  • Re: Very frustrated with MS Server 2003 SBS
    ... you having these two domains on the same wire, that's why I was hoping you could make some separation to isolate the issue. ... Re-installing the workstation OS might work for this WS, but if the root cause is elsewhere, then it's not a good solution. ... And, yes, I'd start with a fresh workstation account, created on the SBS using the Add Computer Wizard. ...
    (microsoft.public.windows.server.sbs)