S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, 1997.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....aware that an explicit manipulation of business rules was required in order to support the entire business rule life cycle. As a result, numerous research projects have been carried out in support of business rule discovery, analyses, classification, articulation, formalization and documentation [6, 15, 12, 30, 7, 9, 16]. Today, one of the most promising areas of business rule research is integration of organization s business environment and its supporting IS [27, 28] While it is clear that an IS can act as a competitive asset to the organization, it must first conform to its real business needs. However, ....

S. Ceri, P. Fraternale, "Designing Database Applications with Objects and Rules: The IDEA Methodology", Addison-Wesley, 1997.

....step. The possibility of nontermination of the rule processing algorithm due to rules that trigger each other, is a well known feature of active databases [156] Nontermination resembles divergence 9. 7 Transactional workflows 151 in statecharts (see page 50) Furthermore, Ceri and Fraternali [33] combine the syntax of statecharts with active rules: they use statecharts as a graphical front end for an active rule language, Chimera. Unfortunately, they do not relate the active rule language to the statechart semantics. We do not know of any work comparing active rules to statechart ....

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, 1997.

....a language in which ECA rules on XML can be defined. ECA rules have been used in many settings, including active databases [26, 29] workflow management, network management, personalisation and publish subscribe technology [3, 13, 14, 17, 27] and specifying and implementing business processes [2, 16, 22]. However, one of the key recurring themes regarding the successful deployment of ECA rules is the need for techniques and tools for analysing their behaviour [15, 23] When multiple ECA rules are defined within a system, their interactions can be 1 difficult to analyse, since the execution of ....

....of rule execution is a possibility and thus rule analysis techniques are important for developing sets of wellbehaved rules. 3 Analysing ECA Rule Behaviour Analysis of ECA rules in active databases is a well studied topic and a number of analysis techniques have been proposed, e.g. [4, 5, 6, 8, 9, 10, 11, 16], mostly in the context of relational databases. Analysis is important, since within a set of ECA rules, unpredictable and unstructured behaviour may occur. Rules may mutually trigger one another, leading to unexpected (and possibly infinite) sequences of rule executions. Two important analysis ....

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, 1997.

.... data consistency [39] Boolean expression, A boolean expression over a global database schema [36] Integrity constraints are well typed boolean expressions built using the names and classes of the schema and general operators [6] Rule, which guarantees the integrity of a database [4] 9][12] [80] When integrity constraint is represented in a data model, it is called as integrity model. Integrity models are interrelated with data models and transaction models, by offering concepts for representing constraints to mini world states and constraints to mini world processes [68] A ....

S. Ceri and P. Fraterbali, Designing Database Application with Objects and Rules: The IDEA Methodology, Addison Wesley Longman, 1997.

....however, that the Chimera action language is powerful enough, in that it provides all data manipulation statements supported by commercial database management systems. Moreover, its declarative style can be useful at least at the specification level to formulate triggers and to reason about them [8]. Notice, moreover, that the issues addressed in this paper also apply to object relational databases with reactive capabilities, and in particular to the SQL 3 standard proposal [9] We discuss in detail the application of our results to object relational database systems at the end of the ....

....be performed. In Chimera triggers, instead, these two tasks are decoupled in the action and condition components. We remark that, however, this is a syntactic difference, since we can easily establish a correspondence between each SQL DML statement and a (set of) Chimera condition action pair(s) [8]. Example 11: The following SQL 3 trigger reacts to insertions of new employees, whose rank is manager. It sets the salary of all employees in the inserted manager department whose salary excedes the salary of the newly inserted manager, to the salary of that manager. CREATE TRIGGER updsal ....

S. Ceri and P. Fraternali, Designing Database Applications with Objects and Rules - The IDEA Methodology, Addison-Wesley, 1997.

....sense, several approaches have been published (cf. 3, 7, 8] dealing with issues such as use case granularity, the level of detail in which use cases should be described, and the suitability of creating a use case hierarchy. Based on the OOram three model architecture [13] and the IDEA method [2], we are working on the definition of a UML based process model for application in the information systems domain. This process includes a business modeling phase, aimed 1 Partially supported by the CICYT (Science and Technology Joint Committee) Spanish Ministry of Education and Ministry of ....

Ceri, S., Fraternalli, P.: Designing Database Applications With Objects and Rules. The IDEA Methodology. Addison-Wesley (1997)

.... Event condition action rules are used to provide reactive functionality in many settings, including active databases [34, 30] workflow management, network management, personalisation and publish subscribe technology [31, 18, 15, 16, 4, 28] and specifying and implementing business processes [19, 2, 25]. In this paper we propose a simple ECA rule language for providing reactive functionality over corpora of XML documents. The motivation for this work is the increasing use of XML as a mechanism for data warehousing see for example recent extensions of commercial database systems to support ....

....ECA rules can be used as an integrating technology for providing this kind of reactive functionality on corpora of XML documents. One of the key recurring themes regarding the successful deployment of ECA rules is the need for techniques and tools for analysing and optimising their behaviour [19, 26, 17]. Thus, the second part of this paper explores techniques for analysing and optimising our proposed ECA rule language for XML. The closest previous work to ours is [25, 15, 16] 25] describes a language for interacting with XML sources on the web which incorporates ECA rules. However, details of ....

[Article contains additional citation context not shown here]

S. Ceri and P. Fraternalli. Designing Database Applications with Objects and Rules:The IDEA Methodology. Addison-Wesley, 1997.

....in order to support the analysis of natural language informal specifications [29,1,11,47] The resulting conceptual model can be represented as a computer processable ontology and from there mapped to concrete target platforms. These aspects have been extensively studied in the ESPRIT IDEA project [14], especially for what concerns the mapping of the knowledge specification (the ontology) to schemes for many different types of databases (relational, object oriented, deductive, active) Another example of use of ontologies at development time is information integration: a common conceptual ....

Ceri, S. and Fraternali, P. 1997. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison Wesley.

.... of as declarative constraints about database states and defined which database states were valid and which were not, with the presence of cascade operations in the SQL3 constraints and the use of after triggers to maintain the integrity of the data, there is currently little tradition (except in [CF97] and few other cases) of using or following standard software engineering practices of separating specification from implementation when designing and developing active databases. This means that 1 often active database developers do not even specify what the purpose of the active features of ....

S. Ceri and P. Fraternali. Designing database applications with objects and rules -- the IDEA methodology. Addison-Wesley, 1997.

....of a user interface. 2) The user interface explains rule behaviour by means of a graphical presentation. This presentation can be customized using a sophisticated lter mechanism. In the recent literature, other approaches to active database design have been presented (e.g. the IDEA Methodology [1]) However, the emphasize is di erent in our design environment. We concentrate on the following issues: Declarative event language: Similarly as QBE and SQL are better accepted by end users than Relational Algebra, end users are assumed to prefer a declarative event language over an ....

S. Ceri and P. Fraternali, \Designing Database Applications with Objects and Rules: the IDEA Methodology," AddisonWesley, 1997.

....server being used to provide centralized administration of a soft switch in a communication network and show how it can be augmented to handle conflict resolution. 1 Introduction The simple event condition action rule paradigm has proved very useful in many AI and database applications [23, 4], from constraint maintenance to the general encoding of expert rules. However, the applicabil Work done while visiting Bell Labs. ity of the event condition action rule paradigm goes beyond data management or expert systems. Such rules can be used in network management and monitoring [11] ....

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, 1997.

....tools (CPT, PROP and SEA) using a common graphical approach to schema visualisation and manipulation and is available in source form via WWW. PRDT has been developed within a master thesis project at Bonn [Asc97] According to the application development process outlined in the IDEA Methodology [CF96], deductive concepts are identified and the resulting rules formulated during the design phase of the methodology. Syntactic properties of deductive rules (such as typecorrectness, range restiction and safety) have to be checked already during rule design, whereas the verification of semantic ....

....operand of the not operator. Thus, these dependencies can already be found in the textual representation of a Chimera schema, although it might be a non trivial task to find them. A more detailed discussion of these stratifiability problems and related examples can be found in the IDEA methodology [CF96]. 2.3.2 Using Self and Class So far, all dependencies have been explicitly introduced by the rule designer who refers to a concept within the body of a deductive rule. However, such dependencies can also be created implicitly by establishing relationships among concepts as they are typical for ....

Stefano Ceri and Piero Fraternali, editors. Designing Database Applications with Objects and Rules --- The IDEA Methodology. Addison-Wesley, 1996. to appear.

.... triggers and constraints into object oriented DBMS (OODBMS) 16, 17] or to enhance SQL with object oriented capabilities [14] A system, whose goal is specifically the integration of object oriented, deductive and active capabilities has been developed as part of the ESPRIT Project Idea [6, 7]. In this work we shall describe the data model of Idea, called Chimera [9, 19, 8] and we shall give a semantics for it. We have chosen Chimera because it is a meaningful example of the integration of different paradigms, and, though not a commercial system, it is actually implemented. It seems ....

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: the IDEA Methodology. Addison Wesley, 1997.

....interesting example of integration among different programming paradigms. This is an interesting example to verify the power and the flexibility of the considered framework. In the next sections we shall describe the data model of Chimera [10, 9, 23] developed as part of the ESPRIT Project Idea [8], and we shall give a logical semantics to it by defining an encoding in E hhf . Chimera has been chosen as a representative of modern database management systems (DBMS) These incorporate, for instance, objects modeling capabilities into deductive databases [5] triggers and constraints into ....

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: the IDEA Methodology. Addison Wesley, 1997.

....behaviour. Large scale applications making intensive use of active rules are very few because the use of rules is still problematic. First there is, for the time being, a crucial lack of design and conception methods dedicated to the use of active rules albeit some works are now emerging ( FRG96, CF97] Second, use of active rules represent a new programming style very distinct from procedural, functional or logical programming. The third and main reason is that it is very difficult for programmers to understand the overall behaviour of the rule system, i.e. when and how a set of ....

S. Ceri and P. Fraternali, Designing Database Applications with Objects and Rules - The IDEA Methodology, Addison-Wesley, ISBN 0-201-403692-1, 1997.

....object oriented model provides a way to reason and to build views of the database by using logical inferences. Finally, active rules add reactive capabilities to the system, providing for instance mechanisms for database integrity constraints and security. The Chimera data model and query language [9, 10, 23] is one of the most interesting proposals in this sense. In fact, it combines aspects of all the other proposals in the field, e.g. object modeling capabilities into deductive databases [5] triggers and constraints into object oriented DBMS (OODBMS) 20, 21] and query languages with ....

....This section also introduces a way of reading proofs and connectives which simplifies the reading of the linear logic specification of Chimera introduced in Section 5. We conclude the paper with some final remarks and comparisons with other works. 2 An Overview of Chimera The data model of Idea[9], called Chimera [10, 23] is an object oriented, deductive, active data model in that: it provides all concepts commonly ascribed to object oriented data models (such as object identity, complex objects and user defined operations, classes, inheritance) it provides capabilities for defining ....

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: the IDEA Methodology. Addison Wesley, 1997.

.... that the Chimera action language is powerful enough, providing all data manipulation statement supported by commercial database management systems, and that its declarative style in formulating triggers can be useful at least at a specification level to formulate triggers and to reason about them [13]. The contributions of the paper can then be summarized as follows: i) definition of a semantics for active object oriented rule languages, modeling trigger inheritance and overriding; ii) investigation of issues concerning rule inheritance, namely method selection in subclasses; iii) ....

S. Ceri and P. Fraternali. Designing Databases Applications with Objects and Rules: the IDEA Metodology. Addison-Wesley. To Appear.

....(Chen 1976; Teorey 1994; Elmasri and Navathe 1994) The recent trend in object orientation has led to the development of Object Definition Language (ODL) Cattel and Barry 1997) which models the real world in object oriented terms independent of specific implementation programming languages. Ceri and Fraternali (1997) cover various topics in the conceptual design phase with the object oriented or semantic database models and mapping abstract schemas to those in implementation models. FDL (Poulovassilis and Kind 1990) and its successor PFL (Small and Poulovassilis 1991; Small 1993) directly support the ....

Ceri, S. and P. Fraternali (1997). Designing Database Applications with Objects and Rules: the IDEA Methodology.

..... 96 References 97 1 Introduction This document provides the technical documentation for the Chimera Prototyping Tool (CPT) an experimental implementation of the Chimera data model and language introduced by members of the IDEA 1 consortium in 1993 [CM93, CM94, CF96]. The tool has been designed and implemented by the IDEA team at the University of Bonn. This report serves the purpose of describing the way CPT implements the object oriented Chimera data model and language on top of the active, deductive, and relational database system Phoenix [Gri95] Although ....

Stefano Ceri and Piero Fraternali, editors. Designing Database Applications with Objects and Rules --- The IDEA Methodology. AddisonWesley, 1996. to appear.

....by the various systems developed by the individual partners. The main results of the project are a comprehensive methodology, two sets of tools supporting the various phases of this methodology, and a collection of case studies performed by the industrial partners. The IDEA Methodology [3] provides a framework for analyzing, designing, and prototyping database applications with objects and rules. The tool environments have been developed by teams at the Politecnico di Milano and at the University of Bonn, respectively. Whereas the POLI team has been concentrating on aspects of ....

....naturally a couple shortcomings of the original design have been identified over time. Apart from the document defining the language in the form originally designed by the IDEA consortium [5] a comprehensive introduction into Chimera can be found in the book presenting the IDEA methodology [3]. Chimera consists of a conceptual model (called Chimera Model, short: CM) providing object oriented modeling facilities, and of a conceptual language (called Chimera Language, short: CL) providing data definition commands, declarative queries, procedural primitives for database manipulation, as ....

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, to appear 1997.

....be considered quite advanced. Hence, the system in its present status already provides a rather nice and comfortable environment for getting acquainted with application development in an intelligent style as offered by an advanced language like Chimera. In the terminology of the IDEA Methodology [CF96], the CPT supports the prototyping phase of the development process. Finally, we would like to point out that the subsequent manual pages are not intended to serve as a tutorial in schema design. The manual is rather aimed at providing brief and focussed detailed information about the various ....

Stefano Ceri and Piero Fraternali, editors. Designing Database Applications with Objects and Rules --- The IDEA Methodology. Addison-Wesley, 1996. to appear.

No context found.

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, 1997.

No context found.

S. Ceri and P.Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, 1997.

No context found.

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules:The IDEA Methodology. Addison-Wesley, 1997.

No context found.

S. Ceri and P. Fraternali. Designing Database Applications with Objects and Rules: The IDEA Methodology. Addison-Wesley, 1997.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC