Re: Separation of concerns


Daniel T. wrote:
"Thomas Kowalski" <th-ko@xxxxxx> wrote:

It means to keep variables, functions, objects, abstractions as
focused as possible.

And how do you trade off with cohesion?

There is no trade off. Separating concerns means that an abstraction
should do no more than one thing, cohesion means that an abstraction
should do no less than one thing.

That is a precedural-oriented definition because objects are not
necessarily about tasks and task divisions.

-T-

.

Relevant Pages

  • Re: Separation of concerns
    ... And how do you trade off with cohesion? ... There is no trade off. ... Separating concerns means that an abstraction ...
    (comp.object)
  • Re: Separation of concerns
    ... should do no more than one thing, cohesion means that an abstraction ... That is a precedural-oriented definition because objects are not ... necessarily about tasks and task divisions. ...
    (comp.object)
  • Re: Deinition of OOP needed for programming language documentation
    ... often devolves into a heap address without problem space semantics. ... > anyone doing programming irregardless of their knowledge of design. ... that is bleeding cohesion all over the map. ... >> was confused about the level of abstraction of your documentation ...
    (comp.object)
  • Re: Separation of concerns
    ... Separating concerns means that an abstraction ... Cohesion and separation of concerns are also not incompatible, ... to have a clear set of criteria for designing highly cohesive classes. ...
    (comp.object)