[Paper Review] Meta-Data Objects as the Basis for System Evolution

Florida Estrella, Richard McClatchey+3 more|arXiv (Cornell University)|Jul 30, 2001

Business Process Modeling and Analysis4 references15 citations

TL;DR

This paper proposes a reflective software architecture using meta-data objects to enable system evolution in response to changing user requirements. By reifying implicit system aspects into explicit, versionable meta-data objects, the approach decouples system structure from behavior, enabling asynchronous, independent evolution of models and implementations—demonstrated through the CRISTAL project in high-energy physics.

ABSTRACT

One of the main factors driving object-oriented software development in the Web- age is the need for systems to evolve as user requirements change. A crucial factor in the creation of adaptable systems dealing with changing requirements is the suitability of the underlying technology in allowing the evolution of the system. A reflective system utilizes an open architecture where implicit system aspects are reified to become explicit first-class (meta-data) objects. These implicit system aspects are often fundamental structures which are inaccessible and immutable, and their reification as meta-data objects can serve as the basis for changes and extensions to the system, making it self- describing. To address the evolvability issue, this paper proposes a reflective architecture based on two orthogonal abstractions - model abstraction and information abstraction. In this architecture the modeling abstractions allow for the separation of the description meta-data from the system aspects they represent so that they can be managed and versioned independently, asynchronously and explicitly. A practical example of this philosophy, the CRISTAL project, is used to demonstrate the use of meta-data objects to handle system evolution.

Motivation & Objective

• Address the challenge of system evolvability in object-oriented software under changing user requirements.
• Overcome limitations of traditional systems where core structural aspects are implicit and immutable.
• Enable independent management and versioning of system models and their implementations.
• Provide a foundation for self-describing systems through explicit meta-data abstractions.
• Demonstrate the feasibility of the approach in a real-world scientific software context (CRISTAL project).

Proposed method

• Introduce a reflective architecture based on two orthogonal abstractions: model abstraction and information abstraction.
• Reify implicit system aspects (e.g., class structures, constraints) into first-class meta-data objects.
• Separate the description of system models from the runtime system aspects they represent.
• Enable independent, asynchronous, and explicit versioning of meta-data objects and system components.
• Use the CRISTAL project as a practical implementation case to validate the architecture.
• Leverage meta-data objects to support runtime introspection, modification, and evolution of system behavior.

Experimental results

Research questions

• RQ1 How can system evolution be decoupled from runtime behavior in object-oriented systems?
• RQ2 What architectural mechanisms allow implicit system structures to become explicitly manageable and versionable?
• RQ3 Can meta-data objects effectively support the independent evolution of system models and implementations?
• RQ4 How does the separation of model and information abstractions improve system adaptability?
• RQ5 To what extent can this approach be applied in real-world scientific software systems with evolving requirements?

Key findings

• The reflective architecture enables system evolution by making previously implicit structural aspects explicit through meta-data objects.
• Model and information abstractions allow for independent, asynchronous, and explicit versioning of system components.
• The CRISTAL project demonstrates that meta-data-driven evolution supports complex, evolving requirements in high-energy physics software.
• The approach enables self-describing systems where system structure and behavior can be introspected and modified at runtime.
• The separation of meta-data from implementation enhances maintainability and supports long-term system evolution.
• The architecture provides a scalable foundation for evolving systems in domains with dynamic and complex requirements.