pub:projects:samurai
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pub:projects:samurai [2013/01/02 10:58] – kkr | pub:projects:samurai [2013/01/10 19:19] (current) – removed kkr | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== SaMURaI ====== | ||
- | // | ||
- | |||
- | <WRAP center round info 60%> | ||
- | {{ : | ||
- | * Preludium 2 NCN Grant no. UMO-2011/ | ||
- | * **Project Manager:** [[pub: | ||
- | * **Scientific Supervisor: | ||
- | * **Start time:** 05.09.2012 | ||
- | * **Duration: | ||
- | * **Budget:** 67 600 PLN | ||
- | </ | ||
- | |||
- | The main objective of this project is to propose a new knowledge interoperability formalism for rules. | ||
- | Existing Rule-Based System shells (e.g. CLIPS , Jess , Drools , OpenRules) provide different rule languages, which are merely a programming solution. | ||
- | Even though the syntax of these languages is precisely defined, they rarely provide any underlying logical interpretation. | ||
- | The proposed solution would allow for formalization of the knowledge interchange for common rule languages (CLIPS, Jess, Drools, OpenRules) thanks to unified logical interpretation. | ||
- | ===== Description ===== | ||
- | |||
- | ==== Motivation ==== | ||
- | |||
- | Apparently there are two main persistent problems with the existing approaches to integration of Business Processes (BP) with Business Rules (BR): | ||
- | - Semantic mismatch problem -- a semantic mismatch between a general workflow (defined by Business Process) and a specific task logic (defined using Business Rules). | ||
- | - Structure hierarchization problem -- lack of a hierarchical, | ||
- | |||
- | The aim of the project is to address these problems by providing an efficient integration method and developing a hierarchical methodology for design and integration of these technologies. Such a design methodology fits into the MDE (Model-Driven Engineering) paradigm, which focuses on creating and exploiting domain models and simplifies the design process. | ||
- | |||
- | ==== Expected benefits ==== | ||
- | |||
- | Although Business Process and Business Rules technologies are an active field of research and development in the world, there is a lack of a coherent and standardized solution in the field of their integration. | ||
- | |||
- | Our solution proposes the consistent methodology which will be effectively using the BPMN notation for modeling Business Processes with logic tasks defined using Business Rules based on SKE. | ||
- | |||
- | ==== Intended results ==== | ||
- | |||
- | * **Conceptual: | ||
- | * **Practical**: | ||
- | * **Evaluative**: | ||
- | |||
- | |||
- | {{tag> | ||
- | |||
- | Go back to -> [[start|projects]] |