pub:projects:samurai
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
pub:projects:samurai [2013/01/02 10:58] – kkr | pub:projects:samurai [2013/01/10 12:57] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOTOC~~ | ||
====== SaMURaI ====== | ====== SaMURaI ====== | ||
// | // | ||
+ | |||
<WRAP center round info 60%> | <WRAP center round info 60%> | ||
{{ : | {{ : | ||
* Preludium 2 NCN Grant no. UMO-2011/ | * Preludium 2 NCN Grant no. UMO-2011/ | ||
- | * **Project | + | * **Project |
- | * **Scientific Supervisor: | + | * **Scientific Supervisor: |
* **Start time:** 05.09.2012 | * **Start time:** 05.09.2012 | ||
* **Duration: | * **Duration: | ||
- | * **Budget:** 67 600 PLN | ||
</ | </ | ||
- | + | ===== Motivation ===== | |
- | The main objective of this project is to propose a new knowledge interoperability formalism for rules. | + | The main objective of this project is to propose a new knowledge interoperability formalism for business |
- | Existing | + | The motivation for this project involves the fact that existing technologies and languages for rule interchange (e.g. RIF, RuleML, R2ML, KIF) suffer from their general nature and complexity. |
+ | Hence, their practical support is very difficult. | ||
+ | What is more, existing | ||
Even though the syntax of these languages is precisely defined, they rarely provide any underlying logical interpretation. | 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. | + | This research aims at developing a unified business rule representation model which will play a key role in formulation |
- | ===== 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, | + | |
- | + | ||
- | ==== 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 | + | |
- | + | ||
- | Our solution proposes the consistent methodology which will be effectively using the BPMN notation | + | |
- | + | ||
- | ==== Intended results ==== | + | |
- | * **Conceptual: | + | ===== Intended results ===== |
- | * **Practical**: | + | The most important |
- | * **Evaluative**: | + | In this project the following rule languages are considered: CLIPS, Jess, Drools, OpenRules. |
+ | Nevertheless, | ||
+ | From the practical point of view, the project outcome will constitute a semantically coherent knowledge interoperability | ||
+ | - Unified logical interpretation | ||
+ | - Unequivocal knowledge exchange between rule language formats. | ||
+ | - Improved rule base maintenance methods. | ||
- | {{tag> | + | {{tag> |
Go back to -> [[start|projects]] | Go back to -> [[start|projects]] |