• Corpus ID: 9365234

A General Theory for the Evolution of Application Models - Full version

@article{Proper2021AGT,
  title={A General Theory for the Evolution of Application Models - Full version},
  author={Henderik Alex Proper and Theo P. van der Weide},
  journal={ArXiv},
  year={2021},
  volume={abs/2105.11308}
}
In this article we focus on evolving information systems. First a delimitation of the concept of evolution is provided, resulting in a first attempt to a general theory for such evolutions. The theory makes a distinction between the underlying information structure at the conceptual level, its evolution on the one hand, and the description and semantics of operations on the information structure and its population on the other hand. Main issues within this theory are object typing, type… 

Data Schema Design as a Schema Evolution Process

  • H. Proper
  • Computer Science
    Data Knowl. Eng.
  • 1997

Conceptual Schema Optimisation - Database Optimisation before sliding down the Waterfall

An approach to database optimisation in which a conceptual schema is optimised by applying a sequence of transformations by separating between two classes of equivalence, one based on the mathematical semantics of the conceptual schemas and one on conceptual preference by humans.

Conceptual database security access permissions

The "mini world" of the database via Database Management System (DBMS) in an independent form will be mapped by the use of a mapping method to reach a DBMS specific model.

Workflow Automation and Management Services in Web 2.0: An Object-Based Approach to Distributed Workflow Enactment

The paper very briefly reviews the research work in the development, and outlines an object-oriented approach to workflow automation, and describes the architectural design built on the central idea of the workflow object which encapsulates relevant information items along with business protocol definition in one unit.

Component Based Solutions Under Architecture

Many of today’ s applications have an, almost tangible, monolithic nature, purporting to be self contained, offering little or nothing in the way of integration with other applications.

An Alignment Perspective on Architecture-driven Information Systems Engineering : White Paper

This article provides a discussion on architecture-driven information systems engineering from a BusinessIT alignment perspective by viewing Business-IT alignment as the alignment between two co-evolving systems.

FORMAL DEFINITION OF A CONCEPTUAL LANGUAGE FOR THE DESCRIPTION AND MANIPULATION OF INFORMATION MODELS

A language for conceptual data modelling techniques, which is a generalisation of object-role models (such as ER or NIAM), is defined, in which not only constraints, but also queries and updates can be expressed on a conceptual level.

Information System Evolution as Language Evolution

The evolution of information systems from the perspective of the evolution of domain languages is looked at, and an overview of the research efforts concerning the tackling of the matters discussed is presented.

References

SHOWING 1-10 OF 65 REFERENCES

FORMAL DEFINITION OF A CONCEPTUAL LANGUAGE FOR THE DESCRIPTION AND MANIPULATION OF INFORMATION MODELS

A language for conceptual data modelling techniques, which is a generalisation of object-role models (such as ER or NIAM), is defined, in which not only constraints, but also queries and updates can be expressed on a conceptual level.

Meta Object Management and its Application to Database Evolution

It is shown, how each schema update of a given taxonomy is realized by direct updating of schema objects, and how this approach can be used to build a complete tool for database evolution.

Understanding object-oriented: a unifying paradigm

The object- oriented design paradigm is the next logical step in a progression that has led from a purely procedural approach to an object-based approach and now to the object-oriented approach.

Toward a unified framework for version modeling in engineering databases

This work provides a common terminology and collection of mechanisms that underlie any approach for representing engineering design information in a database, and proposes a single framework, based on these mechanisms, which can be tailored for the needs of a given version environment.

A temporally oriented data model

The temporally oriented data model (TODM) presented in this paper is a result of a different approach, namely, it directly operationalizes the pervasive three-dimensional metaphor for time, and develops the notion of the data cube.
...