Object-oriented design

About: Object-oriented design is a research topic. Over the lifetime, 5136 publications have been published within this topic receiving 144108 citations.

A new perspective on rule support for object-oriented databases

Abstract: This paper proposes a new approach for supporting reactive capability in an object-oriented database. We introduce an event interface, which extends the conventional object semantics to include the role of an event generator. This interface provides a basis for the specification of events spanning sets of objects, possibly from different classes, and detection of primitive and complex events. This approach clearly separated event detection from rules. New rules can be added and use existing objects, enabling objects to react to their own changes as well as to the changes of other objects.We use a runtime subscription mechanism, between rules and objects to selectively monitor particular objects dynamically. This elegantly supports class level as well as instance level rules. Both events and rules are treated as first class objects.

Method for customizing software applications

Abstract: Techniques for overlaying objects of a software application with other objects allow modification and customization of the application by one or more users in different ways, without storing multiple modified copies of the application. The technique allows configuring the software application to execute using overlaid objects instead of the base objects contained in the software application. In some embodiments, the base objects for the software application and the overlaid objects are stored in a datastore, and a runtime embodiment causes execution of the overlaid objects instead of the base objects.

Automated support for modeling OO software

Abstract: We explore how automated tools might support the dynamic modeling phase of object oriented software development. We use the Object Modeling Technique as a guideline and notational basis, but in principle our approach is not tied to any particular OO methodology. We assume, however, that dynamic modeling exploits scenarios (as in OMT) describing examples of using the system being developed. Our techniques can easily be adopted for various scenario representations, such as sequence diagrams or collaboration diagrams in UML.

The Offline Software Framework of the Pierre Auger Observatory

Abstract: The Pierre Auger Observatory is designed to unveil the nature and origin of the highest energy cosmic rays through the analysis of extensive air showers. The large and geographically dispersed collaboration of physicists and the wide-ranging collection of simulation and reconstruction tasks pose some special challenges for the offline analysis software. They have designed and implemented a general purpose framework which allows Auger collaborators to contribute algorithms and configuration instructions to build up the variety of applications they require. The framework includes machinery to manage these user codes, to organize the abundance of user-contributed configuration files, to facilitate multi-format file handling, and to provide access to event and time-dependent detector information residing in many data sources. A number of utilities are also provided, including a novel geometry package allowing manipulation of abstract geometrical objects independent of coordinate system choice. The framework is implemented in C++ and takes advantage of object oriented design and common open source tools, while keeping the user-side simple enough for C++ novices to learn in a reasonable time. The distribution system incorporates unit and acceptance testing in order to support rapid development of both the core framework and the contributed user codes.

Deterministic, probabilistic and subjective modeling system

Abstract: A modeling system that arranges the model in a hierarchical structure of communicating and independently executing object modules controlled by an overall supervisor. Each object represents a component or a system and includes an object controller which communicates with other object modules, an object error checker and an object model. The objects communicate through a database accessible by all objects. The structure of the object module and the hierarchical structure itself are standardized allowing new components or systems to be added by adding a standard object module which includes an object model that is unique to the object being modeled. The controller for an object causes subobjects upon which the object model depends for data to be executed prior to execution of the object model. Such bottom up model traversal insures that models do not execute until all needed data is available. The error check module checks the controller and model modules to make sure they are executing properly. The object model includes a deterministic equation based component aging model, a statistical based component aging model and expert rules that combine the deterministic and statistical model with the knowledge of experts to determine the current state of the object and make recommendations concerning future actions concerning the object. A maintenance module is also included along side the supervisor that allows maintenance actions for the objects to be taken into consideration.