Maximizing reuse of existing software assets is a common goal for companies as they move to new projects and products. Typically, reuse is complicated by changes to the context in which the software executes; the software architecture. As in all development areas, software architects are seeking continuous improvement to their designs either through internal innovation or established external standards. However, changes to the software architecture (e.g. interfaces, services, scheduling etc.) can prove to be a driver of fundamental, large-scale change to software if reuse strategies are not planned into the product line. This paper describes a reuse strategy that maximizes the preservation of existing assets while focusing effort on the development of transformation rules that generate software targeting a new architectural context.