RTSORAC: A real-time object-oriented database model

Prichard, Janet J.; DiPippo, Lisa Cingiser; Peckham, Joan; Wolfe, Victor Fay

doi:10.1007/3-540-58435-8_226

Cited by 28 publications

(13 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We also plan to investigate tools for maintaining and browsing through the update rules, so that the database semantics are accessible once the database has been built. In addition, we are also investigating the role of relationships and enforcement rules in real time database applications (Prichard, 1994) and in forming complex views in design domains.…”

Section: Resultsmentioning

confidence: 99%

“…A schema checker that uses semantic information from the ASDIs to interact with the designer to assure correct and consistent schema has been developed (Peckham 1994;Qian, 1994). A graph theoretic representation of the objects, relationships, and enforcement rules is used with properties such as the transitivity of update actions to discover awkward, incorrect, and/or incomplete schema structures such as cycles and conflicting updates.…”

Section: Overview Of Sorac Systemmentioning

confidence: 99%

“…By defining monitors as properties of relationship objects, the SORAC data model combines the benefits of relationships as modeling constructs with the encapsulation of the propagator. The enforcement rules which define the operation of a monitor are taken from Peckham (1994), where they are defined for the analysis of schema correctness. Since the behavior defined by a monitor's enforcement rules is directly mapped to the behavior of a relationship object, any correctness guarantees made through analysis of the enforcement rules can be assumed for the resulting database.…”

Section: Oil Interfacementioning

confidence: 99%

See 2 more Smart Citations

Data model for extensible support of explicit relationships in design databases

1995

Self Cite

View full text Add to dashboard Cite

Abstract.We describe the conceptual model of SORAC, a data modeling system developed at the University of Rhode Island. SORAC supports both semantic objects and relationships, and provides a tool for modeling databases needed for complex design domains. SORAC's set of built-in semantic relationships permits the schema designer to specify enforcement rules that maintain constraints on the object and relationship types. SORAC then automatically generates C+ + code to maintain the specified enforcement rules, producing a schema that is compatible with Ontos. This facilitates the task of the schema designer, who no longer has to ensure that all methods on object classes correctly maintain necessary constraints. In addition, explicit specification of enforcement rules permits automated analysis of enforcement propagations. We compare the interpretations of relationships within the semantic and object-oriented models as an introduction to the mixed model that SORAC supports. Next, the set of built-in SORAC relationship types is presented in terms of the enforcement rules permitted on each relationship type. We then use the modeling requirements of an architectural design support system, called ArchObjects, to demonstrate the capabilities of SORAC. The implementation of the current SORAC prototype is also briefly discussed.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Overview Of Sorac Systemmentioning

confidence: 99%

Section: Oil Interfacementioning

confidence: 99%

See 1 more Smart Citation

Data model for extensible support of explicit relationships in design databases

1995

Self Cite

View full text Add to dashboard Cite

show abstract

“…Although some of the terms defined in [PCPW94] differ from our requirements, the same functionality can be found from their model and from our analysis.…”

Section: Rule Aspectsmentioning

confidence: 57%

“…A relationship constraint defines a constraint rule that can affect the relationship object and any of the participating objects. [PCPW94]. RTSORAC supports full transaction temporal consistency and semantic-based object-level transactions.…”

Section: Distribution Aspectsmentioning

confidence: 99%

Requirements for real-time object-oriented database models-how much is too much?

Taina

Son²

Proceedings Ninth Euromicro Workshop on Real Time Systems

View full text Add to dashboard Cite

In this paper we present an analysis of requirements for real-time object-oriented database models. The analysis is based on the assumption that in the future, real-time databases will need real-time, objectoriented, distributed, and active database features.W e consider the problem of real-time objectoriented database model requirements in three steps. First, we list the aspects that we jind important on real-time, object-orientation, distribution, and rule handling. Second, we give a set of features of all of the aspects that should constitute the very core of a realtime object-oriented database model. And third, we give an extended set of features that represents useful extra functionality to the models.

show abstract

Optimizing Performance-Polymorphic Declarative Database Queries

Padron-McCarthy

Risch

1997

Real-Time Database and Information Systems: Research Advances

View full text Add to dashboard Cite

RTSORAC: A real-time object-oriented database model

Cited by 28 publications

References 7 publications

Data model for extensible support of explicit relationships in design databases

Data model for extensible support of explicit relationships in design databases

Requirements for real-time object-oriented database models-how much is too much?

Optimizing Performance-Polymorphic Declarative Database Queries

Contact Info

Product

Resources

About