Using Separation of Concerns to Simplify Software Product Family Engineering

Published proposals and solutions for building software product families rely on some of the most complex, resource intensive, capital intensive, and intellectually demanding software engineering practices developed to date[1,2,6]. For most software engineering organizations, the complexity, cost, and perceived risk are a prohibitive barrier for implementing formal software product family practices.