A semantics of multiple inheritance
Information and Computation - Semantics of Data Types
A translation approach to portable ontology specifications
Knowledge Acquisition - Special issue: Current issues in knowledge modeling
A behavioral notion of subtyping
ACM Transactions on Programming Languages and Systems (TOPLAS)
Covariance and contravariance: conflict without a cause
ACM Transactions on Programming Languages and Systems (TOPLAS)
Toward principles for the design of ontologies used for knowledge sharing
International Journal of Human-Computer Studies - Special issue: the role of formal ontology in the information technology
Modeling collaborative behavior using cooperation contracts
Data & Knowledge Engineering
A flexible authorization mechanism for relational data management systems
ACM Transactions on Information Systems (TOIS)
Database abstractions: aggregation and generalization
ACM Transactions on Database Systems (TODS)
Behavior-consistent specialization of object life cycles
ACM Transactions on Software Engineering and Methodology (TOSEM)
Active data warehouses: complementing OLAP with analysis rules
Data & Knowledge Engineering - Data warehousing
Realizing active data warehouses with off-the-shelf database technology
Software—Practice & Experience
Trigger Inheritance and Overriding in an Active Object Database System
IEEE Transactions on Knowledge and Data Engineering
Modeling Business Rules with Situation/Activation Diagrams
ICDE '97 Proceedings of the Thirteenth International Conference on Data Engineering
Proceedings of the Seventh International Conference on Data Engineering
Should Superclasses be Abstract?
ECOOP '94 Proceedings of the 8th European Conference on Object-Oriented Programming
The specification of business rules: A comparison of selected methodologies
Proceedings of the IFIP WG8.1 Working Conference on Methods and Associated Tools for the Information Systems Life Cycle
Public Process Inheritance for Business-to-Business Integration
TES '02 Proceedings of the Third International Workshop on Technologies for E-Services
Modelling Object Behavior: To Use Methods or Rules or Both?
DEXA '96 Proceedings of the 7th International Conference on Database and Expert Systems Applications
"Real World" as an Argument for Covariant Specialization in Programming and Modeling
OOIS '02 Proceedings of the Workshops on Advances in Object-Oriented Information Systems
Simula Begin
Artifact-Centric Business Process Models: Brief Survey of Research Results and Challenges
OTM '08 Proceedings of the OTM 2008 Confederated International Conferences, CoopIS, DOA, GADA, IS, and ODBASE 2008. Part II on On the Move to Meaningful Internet Systems
Modeling Flexible Business Processes with Business Rule Patterns
EDOC '11 Proceedings of the 2011 IEEE 15th International Enterprise Distributed Object Computing Conference
ER'11 Proceedings of the 30th international conference on Advances in conceptual modeling: recent developments and new directions
Multi-dimensional navigation modeling using BI analysis graphs
ER'12 Proceedings of the 2012 international conference on Advances in Conceptual Modeling
Design for service compatibility
Software and Systems Modeling (SoSyM)
Hi-index | 0.00 |
It is common in organizational contexts and in law to apply a decision-scope approach to decision making. Higher organization levels set a decision scope within which lower organization levels may operate. In case of conflict the regulations and rules of a higher level (e.g. European Union) take precedence over those of a lower level (e.g. a member state). This approach can also be beneficially applied to the specialization of the most important kind of business rules in information systems, action rules. Such rules define under which conditions certain actions may, must not, or need to be taken. Applying the decision scope approach to business process modeling based on BPMN means that business rules should not be buried in decision tasks but be made explicit at the flow level. This requires a rethinking of the current BPMN modeling paradigm in that several aspects in conditional flow so far modeled jointly are separately captured: (a) potential ordering of tasks, (b) conditions under which a task may or may not be invoked, and (c) conditions under which a particular task needs to be invoked. Rather than re-defining BPMN as such, an appropriate extension may be provided on-top of BPMN and mapped to standard BPMN primitives. Applying the decision scope approach to active data warehousing, where analysis rules express actionable knowledge, requires to consider two alternative hierarchies: (1) hierarchies of sets of points at the same granularity and (2) the roll-up hierarchy of points in multi-dimensional space. This paper presents the decision scope approach, outlines how it complements inheritance and specialization approaches typically followed in object-oriented systems, and introduces consistency rules for business rule specialization as well as auto-correction rules, which rectify an inconsistent lower-level business rule such that it becomes consistent with higher-level business rules.