物件導向軟體之架構(Object-Oriented Software Construction)探討

We propose a novel formalism, called Frame Logic (abbr., F-logic), that accounts in a clean and declarative fashion for most of the structural aspects of object-oriented and frame-based languages. These features include object identity, complex objects, inheritance, polymorphic types, query methods, encapsulation, and others. In a sense, F-logic stands in the same relationship to the object-oriented paradigm as classical predicate calculus stands to relational programming. F-logic has a model-theoretic semantics and a sound and complete resolution-based proof theory. A small number of fundamental concepts that come from object-oriented programming have direct representation in F-logic; other, secondary aspects of this paradigm are easily modeled as well. The paper also discusses semantic issues pertaining to programming with a deductive object-oriented language based on a subset of F-logic.

/pdf/logical-foundations-of-object-oriented-and-frame-based-2acr2uie5u.pdf

Logical foundations of object-oriented and frame-based languages

A large number of distributed applications requires continuous and timely processing of information as it flows from the periphery to the center of the system. Examples include intrusion detection systems which analyze network traffic in real-time to identify possible attacks; environmental monitoring applications which process raw data coming from sensor networks to identify critical situations; or applications performing online analysis of stock prices to identify trends and forecast future values.Traditional DBMSs, which need to store and index data before processing it, can hardly fulfill the requirements of timeliness coming from such domains. Accordingly, during the last decade, different research communities developed a number of tools, which we collectively call Information flow processing (IFP) systems, to support these scenarios. They differ in their system architecture, data model, rule model, and rule language. In this article, we survey these systems to help researchers, who often come from different backgrounds, in understanding how the various approaches they adopt may complement each other.In particular, we propose a general, unifying model to capture the different aspects of an IFP system and use it to provide a complete and precise classification of the systems and mechanisms proposed so far.

Processing flows of information: From data stream to complex event processing

In this paper, we present the design, implementation, and evaluation of a system that executes complex event queries over real-time streams of RFID readings encoded as events. These complex event queries filter and correlate events to match specific patterns, and transform the relevant events into new composite events for the use of external monitoring applications. Stream-based execution of these queries enables time-critical actions to be taken in environments such as supply chain management, surveillance and facility management, healthcare, etc. We first propose a complex event language that significantly extends existing event languages to meet the needs of a range of RFID-enabled monitoring applications. We then describe a query plan-based approach to efficiently implementing this language. Our approach uses native operators to efficiently handle query-defined sequences, which are a key component of complex event processing, and pipeline such sequences to subsequent operators that are built by leveraging relational techniques. We also develop a large suite of optimization techniques to address challenges such as large sliding windows and intermediate result sizes. We demonstrate the effectiveness of our approach through a detailed performance analysis of our prototype implementation under a range of data and query workloads as well as through a comparison to a state-of-the-art stream processor.

/pdf/high-performance-complex-event-processing-over-streams-24vc8wfi8x.pdf

High-performance complex event processing over streams

Role-based access control (RBAC) models are receiving increasing attention as a generalized approach to access control. Roles may be available to users at certain time periods, and unavailable at others. Moreover, there can be temporal dependencies among roles. To tackle such dynamic aspects, we introduce Temporal-RBAC (TRBAC), an extension of the RBAC model. TRBAC supports periodic role enabling and disabling---possibly with individual exceptions for particular users---and temporal dependencies among such actions, expressed by means of role triggers. Role trigger actions may be either immediately executed, or deferred by an explicitly specified amount of time. Enabling and disabling actions may be given a priority, which is used to solve conflicting actions. A formal semantics for the specification language is provided, and a polynomial safeness check is introduced to reject ambiguous or inconsistent specifications. Finally, a system implementing TRBAC on top of a conventional DBMS is presented.

/pdf/trbac-a-temporal-role-based-access-control-model-384hpgad24.pdf

TRBAC: A temporal role-based access control model

This paper attempts to define an object-oriented database system It describes the main features and characteristics that a system must have to qualify as an object-oriented database system

We have separated these characteristics into three groups: 
•	
Mandatory, the ones the system must satisfy in order to be termed an object-oriented database system These are complex objects, object identity, encapsulation, types or classes, inheritance, overriding combined with late binding, extensibility, computational completeness, persistence, secondary storage management, concurrency, recovery and an ad hoc query facility

•	
Optional, the ones that can be added to make the system better, but which are not mandatory These are multiple inheritance, type checking and inferencing, distribution, design transactions and versions

•	
Open, the points where the designer can make a number of choices These are the programming paradigm, the representation system, the type system, and uniformity




We have taken a position, not so much expecting it to be the final word as to erect a provisional landmark to orient further debate

The object-oriented database system manifesto

The Object-Oriented Database System Manifesto.

In this paper we investigate the definition, detection, and management of events in the active object-oriented database system SAMOS. First, we present various event specification facilities based on simple but nevertheless powerful constructs which support the modelling of time aspects as well. Second we show how events can be detected in an efficient way. Finally, we deal with the internal representation of events using the benefits of the underlying data model.

Events in an Active Object-Oriented Database System

Active database systems have been a hot research topic for quite some years now. However, while “active functionality” has been claimed for many systems, and notions such as “active objects” or “events” are used in many research areas (even beyond database technology), it is not yet clear which functionality a database management system must support in order to be legitimately considered as an active system. In this paper, we attempt to clarify the notion of “active database management system” as well as the functionality it has to support. We thereby distinguish mandatory features that are needed to qualify as an active database system, and desired features which are nice to have. Finally, we perform a classification of applications of active database systems and identify the requirements for an active database management system in order to be applicable in these application areas.

The Active Database Management System Manifesto: A Rulebase of ADBMS Features

Data integration is one of the older research fields in the database area and has merged shortly after database systems were first introduced into the business world. In this paper, we briefly introduce the problem of integration and, based on an architectural perspective, give an overview of approaches to address the integration issue. We discuss the evolution from structural to semantic integration and provide a short outlook on our own research in the SIRUP (Semantic Integration Reflecting User-specific semantic Perspectives) approach.

/pdf/three-decades-of-data-intecration-all-problems-solved-34yd4jmfjf.pdf

Klaus R. Dittrich

Papers

The object-oriented database system manifesto

The Object-Oriented Database System Manifesto.

Events in an Active Object-Oriented Database System

The Active Database Management System Manifesto: A Rulebase of ADBMS Features

Three Decades of Data Intecration — all Problems Solved?