This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
hekate:start [2009/05/25 22:39] wojnicki |
hekate:start [2009/12/11 11:38] gjn |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| The main HeKatE Web Page: http://hekate.ia.agh.edu.pl | The main HeKatE Web Page: http://hekate.ia.agh.edu.pl | ||
| + | The project started in May 2007, and **has ended** in November 2009. | ||
| - | ===== News ===== | ||
| + | ===== News ===== | ||
| + | * 2009/11: //HeKatE has officially **ended**// (more cleanup follows) | ||
| + | * 2009/11: tools updates, [[HaDEs]] releases, important [[HeaRT]] and [[HQEd]] improvements, [[hekate:cases:]] modeling, meet us at [[http://www.cms.agh.edu.pl/|CMS2009]] | ||
| + | * 2009/10: tools updates, [[hekate:cases:]] modeling | ||
| + | * 2009/09: meet us on: [[https://ai.ia.agh.edu.pl/wiki/kese:kese2009|KESE2009]] at [[http://ki2009.uni-paderborn.de/|KI2009]], and [[http://hydrogen.informatik.tu-cottbus.de/wiki/index.php/RuleApps2009|RuleApps2009]] | ||
| + | * 2009/08: public releases of the most important [[HaDEs]] components; the project enters an //internal evaluation phase// | ||
| + | * 2009/07: [[HeaRT]] beta with integration libraries, new version of [[HQEd]]; [[hekate:bib:hekate_bibliography#section|final version]] of the [[http://www.amcs.uz.zgora.pl/|AMCS]] paper on HeKatE and [[XTT2]]. | ||
| + | * 2009/06: major tools improvement, internal releases; the Project has been presented on the [[http://www.iwse.pwr.wroc.pl/|IWSE 2009]] conference, see [[hekate:bib:hekate_bibliography#section|recent IWSE papers]] | ||
| * 2009/05: first major [[HaDEs]] toolset integration, release of: [[HMR]], newer version of [[hekate_markup_language|HML]], related research | * 2009/05: first major [[HaDEs]] toolset integration, release of: [[HMR]], newer version of [[hekate_markup_language|HML]], related research | ||
| * 2009/04: [[hekate:HJEd]] design tool released | * 2009/04: [[hekate:HJEd]] design tool released | ||
| * 2009/03: [[PlNXT:]] first official release | * 2009/03: [[PlNXT:]] first official release | ||
| * 2009/02: HJEd beta, HQEd M6 alpha versions | * 2009/02: HJEd beta, HQEd M6 alpha versions | ||
| - | * 2009/01: Draft [[hekate:bib:hekate_bibliography#gjn2009flairs-oo|UML-based representation for XTT and ARD]] (see the [[hekate:umlrep: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 | ||
| Line 36: | Line 44: | ||
| * 2008/04: [[HeKatE markup language]] proposed | * 2008/04: [[HeKatE markup language]] proposed | ||
| * 2008/03: HeKatE tools released, see [[hekate:varda]] and [[hekate:hqed]] | * 2008/03: HeKatE tools released, see [[hekate:varda]] and [[hekate:hqed]] | ||
| - | * 2008/02: VARDA and HQed go GPLv3! This day (29/02) is //special// :-) | + | * 2008/02: VARDA and HQed go GPLv3! This day (29/02) is special |
| * 2007/11: HeKatE papers on line, finally; see: [[hekate:bib:hekate_bibliography]] | * 2007/11: HeKatE papers on line, finally; see: [[hekate:bib:hekate_bibliography]] | ||
| * 2007/11: ARD+ prototype description | * 2007/11: ARD+ prototype description | ||
| Line 53: | 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 81: | 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. | ||
