Language Support for Evolvable Software: An Initial Assessment of Aspect-Oriented

Separation of concerns [1] is key to manage the complexity of understanding and evolving software. Software engineers have learned how to decompose a complex system into simpler sub-systems, with the goal of making the complexity of sub-problems tractable. Sub-problems are addressed relatively independently and the complete solution is built by gluing together the sub-solutions. The parts that compose the whole system are often modular units of functionality and this partitioning is well supported by existing programming languages, thanks to object orientation, functional decomposition, etc. Indeed, object-oriented programming languages, and the adoption of suitable programming techniques, are important steps in the direction of making software evolution easier. There are two major object-oriented concepts that affect evolution: encapsulation and inheritance. Encapsulation limits the effects of change to localized portion of code. Inheritance allows one to incrementally evolve a component by adding new features or redefining existing features. Both encapsulation and inheritance are instances of the more general concept of separation of concerns. However, sometimes a concern is not easily encapsulated in a functional unit, because it crosscuts the entire system, or parts of it. Synchronization, memory management, network distribution, load balancing, error checking, profiling, security are all aspects of computer problems that are unlikely to be separated in functional units.