Software evolution is a costly yet unavoidable consequence of a successful application. To accommodate the requirements of today's fast changing business world, it is required to adapt the new business rules without disturbing the existing working system. For the business rules evolutions where old and new business rules and business data entities have to exist concurrently in the system, we proposed the Framework, CFFES (Control Flow Framework for Evolving Systems) which focuses on smooth and seamless evolution. CFFES also validates the different business rules as well as business data entities according to their temporal specifications. The Framework capabilities are to be compared with the existing methodologies which are aimed at prioritizing the quality factor - evolvability of a system. The principle of encapsulation in Object Oriented (OO) design overcame the flaws present in structured methodology due to separate data and process components and their interdependencies. However OO design has been proved inadequate in addressing design issues due to crosscutting concerns which are across the objects or components or packages. These crosscutting concerns are main obstacles in the evolution of OO systems. Aspect Oriented software development was proposed as a solution to this problem. In this paper we discuss the impact of evolution on the architectural design of a system designed using Aspect Oriented Design Methodology and a system designed using the Framework (CFFES) proposed by us.