Selected writings on computing: a personal perspective
Selected writings on computing: a personal perspective
Annotation refactoring: inferring upgrade transformations for legacy applications
Proceedings of the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
The anti-goldilocks debugger: helping the average bear debug transparently transformed programs
Proceedings of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applications
Enhancing source-level programming tools with an awareness of transparent program transformations
Proceedings of the 24th ACM SIGPLAN conference on Object oriented programming systems languages and applications
Reusable enterprise metadata with pattern-based structural expressions
Proceedings of the 9th International Conference on Aspect-Oriented Software Development
Separation of concerns in service-oriented applications based on pervasive design patterns
Proceedings of the 2010 ACM Symposium on Applied Computing
Environmental modeling framework invasiveness: Analysis and implications
Environmental Modelling & Software
A programming model for the semantic web
ADNTIIC'11 Proceedings of the Second international conference on Advances in New Technologies, Interactive Interfaces and Communicability
| Hi-index | 0.00 |
Separation of concerns is one of the oldest concepts in computer science. The term was coined by Dijkstra in 1974.1 It is important because it simplifies software, making it easier to develop and maintain. Separation of concerns is commonly achieved by decomposing an application into components. There are, however, crosscutting concerns, which span (or cut across) multiple components. These kinds of concerns cannot be handled by traditional forms of modularization and can make the application more complex and difficult to maintain.