Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there a word for the problem of a framework becoming married to the software modules it supports, for example adding methods to a base class that may apply only to certain subclasses or use cases? It's a particular kind of violation of separation of concerns.

The words that come to mind are "upward devolution" or "feature capture," but these seem to belong to politics, not engineering. Wikipedia has an article on "subsidiarity" which mentions politics and object-oriented programming in the same sentence, but I'm still not sure.

share|improve this question
How about a "blurring/merging of concerns", or maybe "recoupling"? – FrustratedWithFormsDesigner Jan 18 '13 at 14:37

What you describe sounds like an increase in coupling, so the framework and associated modules are becoming more tightly coupled to each other.

"Tight coupling" adequately captures all of the challenges / issues you're mentioning.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.