Concern Management (Re: Mountains or Molehills)
- From: topmind <topmind@xxxxxxxxxxxxxxxx>
- Date: Sat, 11 Aug 2007 13:50:52 -0700
www.gerardvignes.com wrote:
I believe that the next major innovation in software development will
have to address separation of concerns and it will contine to demand
more from pre-processors, compilers and runtime environments.
I believe that "separation of concerns" is an unrealistic goal. It is
the interweaving of concerns that creates the power and utility of
production software to begin with. They interweave in the real world
and thus they need to interweave somehow in software also. Bloated
interfaces to separate everything merely complicate the
interconnectivities with messy, labor-intenstive layers of bloat.
I suspect a more useful goal would be isolatABLE concerns rather than
isolated. Isolatable means that you can find what you want by asking
for it. The idea is influenced by relational queries that can see the
same data from different viewpoints: a RELATIVITY ENGINE, so to speak.
To be able to ask, "show me all code that alters screen X" would be
helpful, and more realistic than sticking all code that alters screen
X in one module. The latter is not realstic because such code probably
does other stuff also. Concerns are usually not mutually exclusive.
Altering screen X does not preclude it from also altering thing B.
(Like I said above, we can force full separation, but it gets very
messy.)
We need to learn to manage our view of concerns, not try to isolate
them.
Gerard Vignes
-T-
.
- References:
- Mountains or Molehills
- From: www.gerardvignes.com
- Mountains or Molehills
- Prev by Date: Re: Mountains or Molehills
- Next by Date: Re: De facto class diagram school example?
- Previous by thread: Re: Mountains or Molehills
- Next by thread: Maintaining Layer Separation with Push and Pull
- Index(es):
Relevant Pages
|
