Full Description
Recently, a set of new software development techniques - termed Aspect-Oriented Software Development (AOSD) - has become available that aims to support modularisation of systemic properties (also referred to as crosscutting-concerns) and their subsequent composition with other parts of the system. Rashid focuses on the use of Aspect-Oriented Programming (AOP) techniques to modularise otherwise broadly scoped features in database systems like the transaction or the versioning model to improve their customisability, extensibility, and maintainability. His aim is to show how the use of AOP can transform the way we develop, use and maintain database systems. He also discusses how database systems can support AOP by providing means for storage and retrieval of aspects.Aspect-Oriented Databases Systems shows the possible synergy between AOSD and database systems and is of particular interest for researchers, graduate students and software developers in database systems and applications.
Table of Contents
Preface xi
P.1 Outline of the Book xii
P.2 Who should Read this Book? xiii
P.3 Relevant Resources xiv
P.4 Acknowledgements xiv
1. Introduction 1 (20)
1.1 Database Systems 2 (11)
1.1.1 Schema Evolution in Object-Oriented 3 (7)
Databases
1.1.1.1 Class Hierarchy Modification 3 (2)
1.1.1.2 Class Structure Modification 5 (1)
1.1.1.3 Backward and Forward Compatibility 6 (4)
1.1.1.4 Need for Dynamic Changes 10 (1)
1.1.2 Versioning and Workgroup Support 10 (2)
1.1.3 Transaction Processing 12 (1)
1.2 Aspect-Oriented Database Systems 13 (6)
1.2.1 Crosscutting Concerns in Database 13 (1)
Systems
1.2.2 Fundamentals of Aspect-Oriented 14 (3)
Database Systems
1.2.3 Existing Aspect-Oriented Database 17 (6)
Systems
1.2.3.1 AODBs using AOP in their 17 (1)
Implementation and Operation
1.2.3.2 AODBs Supporting Aspect 18 (1)
Persistence
1.2.3.3 AODBs or Frameworks Supporting 18 (1)
Separation of Persistence Code from
Application Logic
1.2.3.4 Facets of the Database-AOP 19 (1)
Relationship Addressed by Current AODBs
1.3 Conclusion 19 (2)
2. Aspect-Oriented Programming (AOP) 21 (18)
2.1 Separation of Concerns 21 (2)
2.2 Addressing Crosscutting Concerns with AOP 23 (13)
2.2.1 Aspect Languages 26 (3)
2.2.2 Composition Filters 29 (2)
2.2.3 Adaptive Programming 31 (2)
2.2.4 Hyperspaces 33 (1)
2.2.5 Reflective Approaches 34 (1)
2.2.6 Hybrid Approach 35 (1)
2.3 Aspect-Oriented Software Development 36 (1)
2.4 Conclusion 37 (2)
3. Crosscutting Concerns in Database Systems 39 (14)
3.1 Crosscutting Concerns at DBMS Level 40 (6)
3.1.1 Instance Adaptation Approach 42 (1)
3.1.2 Schema Evolution Model 43 (2)
3.1.3 Transaction Model 45 (1)
3.1.4 Other Crosscutting Concerns at DBMS 46 (1)
Level
3.2 Crosscutting Concerns at Database Level 46 (5)
3.2.1 Links Among Persistent Entities 47 (1)
3.2.2 Versioning Information 48 (1)
3.2.3 Instance Adaptation Routines 49 (2)
3.2.4 Other Crosscutting Concerns at 51 (1)
Database Level
3.3 Conclusion 51 (2)
4. Applying AOP in Database Systems 53 (38)
4.1 A Model for AOP in Database Systems 53 (3)
4.2 AOP at DBMS Level 56 (11)
4.2.1 Instance Adaptation Approach 56 (7)
4.2.1.1 Customisable Instance Adaptation 56 (4)
in SADES
4.2.1.2 Customisable Instance Adaptation 60 (3)
in AspOEv
4.2.2 Schema Evolution Model 63 (1)
4.2.3 Transaction Model 64 (3)
4.3 AOP at Database Level 67 (20)
4.3.1 Links among Persistent Entities 67 (11)
4.3.1.1 Overview of SADES Architecture 67 (3)
4.3.1.2 Separation of Links using 70 (6)
Composition Filters
4.3.1.3 Change Propagation and 76 (2)
Referential Integrity
4.3.2 Versioning 78 (3)
4.3.3 Instance Adaptation Routines 81 (12)
4.3.3.1 Instance Adaptation Routines in 81 (5)
SADES
4.3.3.2 Instance Adaptation Routines in 86 (1)
AspOEv
4.4 Change Propagation: DBMS Level to 87 (1)
Database Level
4.5 Cost-effectiveness 88 (1)
4.6 Conclusion 88 (3)
5. Persistent Aspects 91 (28)
5.1 Need for Aspect Persistence 91 (2)
5.2 Persistent Aspect Stores 93 (18)
5.2.1 An Aspect Store Based on an 94 (5)
Object-Oriented Database
5.2.1.1 PersAJ: An Aspect Store Based on 97 (2)
AspectJ and Jasmine
5.2.2 An Aspect Store Based on a Relational 99 (12)
Database
5.2.2.2 An Aspect Store for AspectJ using 100 (11)
SQL-92 Databases
5.3 Aspect Composition in a Persistent 111 (6)
Environment
5.3.1 Exploiting Composition Mechanisms of 111 (1)
Existing AOP Techniques
5.3.2 Building Composition Mechanisms into 112 (9)
the DBMS
5.3.2.1 Persistent Aspect Structures 113 (1)
5.3.2.2 Weave-on-demand and Weave 114 (2)
Histories
5.3.2.3 Weaver for the SADES Object 116 (1)
Database Evolution System
5.4 Applications of Aspect Persistence 117 (1)
5.5 Conclusion 117 (2)
6. Persistence as an Aspect 119 (26)
6.1 A Bibliography Application 120 (1)
6.2 Aspectising Persistence 121 (16)
6.2.1 Database Access 122 (10)
6.2.1.1 Connection 124 (2)
6.2.1.2 Storage and Update 126 (1)
6.2.1.3 Retrieval 127 (2)
6.2.1.4 Deletion 129 (1)
6.2.1.5 Transactions 130 (2)
6.2.1.6 Meta-data Access 132 (1)
6.2.2 SQL Translation 132 (4)
6.2.3 The Emerging Persistence Framework 136 (1)
6.3 Analysis of the Persistence Aspectisation 137 (3)
6.3.1 Using Other Persistence Mechanisms 137 (1)
6.3.2 Reflection and Other AOP Techniques 137 (2)
6.3.3 Aspect Interaction 139 (1)
6.4 Other Approaches Aspectising Persistence 140 (2)
and Related Concerns
6.5 Conclusion 142 (3)
7. Conclusion and Outlook 145 (2)
Abbreviations 147 (2)
References 149 (24)
Index 173
