This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hekate:start [2009/12/02 19:05] gjn Links to hekate:umlrep:visual_rules_process_modeling changed to hekate:visual_rules_process_modeling |
hekate:start [2019/06/27 15:49] (current) |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| * 2009/01: Draft [[hekate:bib:hekate_bibliography#gjn2009flairs-oo|UML-based representation for XTT and ARD]] (see the [[Visual Rules Process Modeling]] presentation) | * 2009/01: Draft [[hekate:bib:hekate_bibliography#gjn2009flairs-oo|UML-based representation for XTT and ARD]] (see the [[Visual Rules Process Modeling]] presentation) | ||
| * 2008/12: Draft [[hekatedev:xtt2|XTT2 formulation]] published | * 2008/12: Draft [[hekatedev:xtt2|XTT2 formulation]] published | ||
| - | * 2008/11: The [[hekate:semweb:dl_intro|possible integration of ALSV(FD) with Description Logic]] considered | + | * 2008/11: The [[dl_intro|possible integration of ALSV(FD) with Description Logic]] considered |
| * 2008/10: Rule prototyping algorithm presented at [[http://www.imcsit.org/?cont=91&type=page&page=72|AAIA workshop]] | * 2008/10: Rule prototyping algorithm presented at [[http://www.imcsit.org/?cont=91&type=page&page=72|AAIA workshop]] | ||
| * 2008/09: The [[https://ai.ia.agh.edu.pl/wiki/kese:kese2008|KESE 2008 workshop]], UML based representation discussed | * 2008/09: The [[https://ai.ia.agh.edu.pl/wiki/kese:kese2008|KESE 2008 workshop]], UML based representation discussed | ||
| - | * 2008/09: [[plnxt:start|PlNXT prototype]] presented at [[http://ki2008.dfki.uni-kl.de/|KI 2008]] | + | * 2008/09: [[mindstorms:plnxt:start|PlNXT prototype]] presented at [[http://ki2008.dfki.uni-kl.de/|KI 2008]] |
| * 2008/07: Project results presented at the [[http://oxygen.informatik.tu-cottbus.de/RuleApp2008/|RuleApp 2008]] workshop at [[http://www.ece.upatras.gr/ecai2008|ECAI 2008]] | * 2008/07: Project results presented at the [[http://oxygen.informatik.tu-cottbus.de/RuleApp2008/|RuleApp 2008]] workshop at [[http://www.ece.upatras.gr/ecai2008|ECAI 2008]] | ||
| * 2008/06: Preliminary [[hekate:alsvfd|ALSV(FD)]] formulation | * 2008/06: Preliminary [[hekate:alsvfd|ALSV(FD)]] formulation | ||
| Line 61: | Line 61: | ||
| - | ===== Mottos ===== | + | ===== Team ===== |
| - | If a machine is expected to be infallible, it cannot also be intelligent. | + | Project Leader: [[http://home.agh.edu.pl/ligeza|Prof. Antoni Ligęza, PhD]] |
| - | -- A.Turing | + | |
| + | Project Coordinator: [[http://home.agh.edu.pl/gjn|Grzegorz J. Nalepa, PhD]] | ||
| - | Insufficient facts always invite danger | + | The Project involved number of important AGH UST staff members and students, see [[team]] information. |
| - | -- Spock, "Space Seed" | + | |
| ===== Insight ===== | ===== Insight ===== | ||
| - | See [[hekate:hekate concepts]] for more info about the ideas, [[hekate process|process]], architecture, applications etc. | + | See [[hekate:hekate concepts]] for more info about the ideas, |
| + | [[hekate process|process]], architecture, applications etc. | ||
| Line 89: | Line 88: | ||
| ===== Cases ===== | ===== Cases ===== | ||
| - | * [[hekate case thermostat|Thermostat]] | + | A number of [[https://ai.ia.agh.edu.pl/wiki/hekate:cases:start|rule systems cases]] has been modeled using the HeKatE approach. |
| ===== Motivation ===== | ===== Motivation ===== | ||
| * There is a [[misc:semantic_gap]] in the contemporary Software Engineering which should be minimized | * There is a [[misc:semantic_gap]] in the contemporary Software Engineering which should be minimized | ||
| * Designed Knowledge Base is a 'program' capable of running, assuming that a proper runtime environment is supplied | * Designed Knowledge Base is a 'program' capable of running, assuming that a proper runtime environment is supplied | ||
| - | * The Knowledge Base can be verified and its proper behavior can be assured -- minimize the number of bugs | + | * The Knowledge Base can be verified and its proper behavior can be assured. |
| * The Knowledge Base can be easily extended to meet new requirements, implement new functionality etc. | * The Knowledge Base can be easily extended to meet new requirements, implement new functionality etc. | ||
