An orthogonally persistent Java
ACM SIGMOD Record
Proceedings of the 2nd international conference on Aspect-oriented software development
GCSE '00 Proceedings of the Second International Symposium on Generative and Component-Based Software Engineering-Revised Papers
AOP: Does It Make Sense? The Case of Concurrency and Failures
ECOOP '02 Proceedings of the 16th European Conference on Object-Oriented Programming
Managing schema evolution in a container-based persistent system
Software—Practice & Experience
Self-Aware software – will it become a reality?
Self-star Properties in Complex Information Systems
A performance cost evaluation of aspect weaving
ACSC '13 Proceedings of the Thirty-Sixth Australasian Computer Science Conference - Volume 135
| Hi-index | 0.00 |
The separation-of-concerns principle aims to separately modularize the different parts of software that are relevant to a particular concept, goal, task, or purpose. Appropriate separation of application concerns reduces software complexity, improves comprehensibility, and facilitates concerns reuse. Considering persistence as a common application concern, its separation from a program's main code implies it is possible to develop applications without considering persistence requirements. Programmers can then plug in persistence aspects at a later stage. This separation gives the developer a way to handle persistence software attributes regardless of the application functionality. There are various approaches for separating persistent features. However, computational reflection can better manage persistence concerns with complete transparency, offering exceptional adaptability. The authors have developed a reflective system called nitrO, and a prototype persistence system based on this reflective system. This research-oriented prototype illustrates how to use computational reflection in future persistence systems to completely separate and adapt application persistence attributes at runtime.