Schema evolution in the star framework

The STAR data model supports the definition of object schemata, according either to some design methodology or to the designer's decision. Object schemata allow a flexible management of the various representations that are created during the design of a particular object. Object schemata can evolve or even be dynamically defined, departing from an existing object schema and making changes to it. Schema evolution facilities are a valuable support for both the definition of new design objects and design methodology management. Schema evolution is maintained through versions, so that version management is applied not only to design objects themselves, but also to object schemata. Consistency is guaranteed for schema operations, based on a set of invariant rules

Data model evolution as a basis of business process management

In this article we propose an approach to business process management which meets the demands of business process evolution. This approach allows for on-the-fy modifications of business processes. In contrast to many other approaches, we do not only concentrate onactivities to be carried out in business processes, but also on the datacreated and manipulated by these activities We propose to apply datamodel analysis and improvement strategies well-known from the information system field in the context of business process management

Utilisation de l'analyse formelle de concepts pour extraire le plus grand modèle commun

International audienceThe development of information systems follows a long and complex process in which various actors are involved. We report an experiment in which we observe the evolution of the analysis model of an information system through 15 successive versions. We use indicators on the underlying concept lattices built by applying Relational Concept Analysis (RCA) to each version. RCA is an extension of FCA which groups entities based on characteristics they share, including links to other entities. It here helps in analyzing their evolution. From this experience, we establish recommendations to monitor and verify the proper evolution of the analysis process

A database model for object dynamics.

Object-oriented database systems, Dynamic object re-classification, Object role model, Dynamic class hierarchy, Object migration

Partially shared views : a scheme for communicating among groups that use different type hierarchies

"March 1988."Includes bibliographical references (p. [27]).Research supported in part by Wang Laboratories, Inc., Xerox Corporation, General Motors, and Bankers Trust Company.Jintae Lee, Thomas W. Malone

Partially shared views : a scheme for communicating among groups that use different type hierarchies

Includes bibliographical references (p. 34-36).Supported by Digital Equipment Corp., the National Science Foundation, Wang Laboratories, Inc., Xerox Corporation, General Motors and Bankers Trust Company.Jintae Lee, Thomas W. Malone

How can groups communicate when they use different languages? : translating between partially shared type heirarchies

Includes bibliographical references (p. 1-3, second group).Supported in part by DARPA, the National Science Foundation, Wang Laboratories, Inc., Xerox Corporation, General Motors, and Bankers Trust Company.Jintae Lee, Thomas W. Malone

A Programming Environment Evaluation Methodology for Object-Oriented Systems

The object-oriented design strategy as both a problem decomposition and system development paradigm has made impressive inroads into the various areas of the computing sciences. Substantial development productivity improvements have been demonstrated in areas ranging from artificial intelligence to user interface design. However, there has been very little progress in the formal characterization of these productivity improvements and in the identification of the underlying cognitive mechanisms. The development and validation of models and metrics of this sort require large amounts of systematically-gathered structural and productivity data. There has, however, been a notable lack of systematically-gathered information on these development environments. A large part of this problem is attributable to the lack of a systematic programming environment evaluation methodology that is appropriate to the evaluation of object-oriented systems