Transactions in ORM

Languages for specifying information systems should not only contain a data definition (sub)language (DDL), i.e., a part for specifying data structures. but also a data retrieval (sub)language (DRL), i.e., a part for specifying queries. and a data manipulation (sub)language (DML), i.e., a part for s...

Full description

Bibliographic Details
Main Author: de Brock, E. O.
Other Authors: Halpin, T, Krogstie, J, Nurcan, S, Proper, E, Schmidt, R, Soffer, P, Ukor, R
Format: Article in Journal/Newspaper
Language:English
Published: Springer 2009
Subjects:
ORM
DML
transaction
add
remove
change
syntax
verbalization
diagram
compound transaction
DYNAMIC RULES
Online Access:https://hdl.handle.net/11370/6dc52885-703c-4e4a-b9db-99d554cd764f
https://research.rug.nl/en/publications/6dc52885-703c-4e4a-b9db-99d554cd764f
Description
Summary:Languages for specifying information systems should not only contain a data definition (sub)language (DDL), i.e., a part for specifying data structures. but also a data retrieval (sub)language (DRL), i.e., a part for specifying queries. and a data manipulation (sub)language (DML), i.e., a part for specifying transactions. The language ORM contains a DDL and a DRL (ConQuer), but it does not contain a sufficient DML as yet. We therefore propose an extension of ORM with a DML, for specifying transactions to he easily validated by domain experts. We introduce the following set of standard classes of specifiable transactions: add an instance, add a query result, remove a subset, and change a subset. We also treat compound transactions in ORM. In ORM there are usually several ways to specify something. For all transactions we therefore propose syntaxes, verbalizations, and diagrams as well. They allow for type-checking and easy validation by domain experts.

Similar Items