Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

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
add comment

1 Answer 1

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
add comment

Your Answer

 
discard

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.