Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
hekate:hekate [2007/11/22 13:55] wojnicki bibliography link added |
— (current) |
====== Hekate ====== | |
[[pl:hekate:hekate|Polska Wersja]], [[hekatedev:hekate_development|For Developers]] | |
| |
{{:hekate.png |Hekate Logo}} | |
| |
**HeKatE** is an acronym for (pick one): | |
| |
* **Hybrid Knowledge Engineering** (current winner), | |
| |
* **Hybrid Engineering of Knowledge-bAsed technologies and inTerfacEs**, | |
| |
* **Hybrid Engineering of Knowledge-bAsed TEchnologies**. | |
| |
The codename regards [[wp>Hekate]] somehow: childbirth, sorcery, witchcraft, ghosts, untamed areas and wilderness ... to name some ;-) -- to show new directions, helpout in our current, desperate IT condition. | |
The project was started by an informal group: the [[knowledge_engineering_group]]. | |
| |
Hekate Web Page: http://hekate.ia.agh.edu.pl | |
| |
===== Publications & Papers ===== | |
| |
Papers and publications regarding the Hekate project are at: [[.bib:Hekate Bibliography]] | |
| |
===== Motto? ===== | |
| |
If a machine is expected to be infallible, it cannot also be intelligent. | |
-- A.Turing | |
We won't make'em intelligent, we'll make them work! | |
| |
| |
Insufficient facts always invite danger | |
-- Spock, "Space Seed" | |
| |
===== Main Aspects ===== | |
| |
* Knowledge Representation -- allowing for forward and backward chaining (perhaps combined or trigerred or sth. else) | |
* Knowledge Design Methods -- visual design with verification ARD and XTT can be used to some extent, more ARD I guess | |
* Software Design Methods based on Knowledge Engineering | |
* Knowldge Runtime Environment -- running the stuff on General Purpose and Embedded Systems | |
* Integrated Knowledge Visualization based on the Model-View-Controler approach | |
* Interfacing with existing applications and paradigms (ie. files, directories, streams) | |
* Extending/replacing current software design approaches such as UML | |
| |
| |
===== Applications ===== | |
* Business Logic Applications (ie. [[hekatedev:business_rules]]) | |
* General purpose applications | |
* Expert Systems | |
* Databases | |
* Control systems -- [[:hexor]] robot control | |
| |
| |
===== Why? ===== | |
* There is a [[:semantic_gap]] in the contemporary Software Engineering which should be minimized | |
* Turing machines suck -- they get too complicated, in time, hard to maintain, alter etc.; bug squashing is a nightmare | |
* 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 -- __no bugs are possible by design!__ | |
* The Knowledge Base can be easily extended to meet new requirements, implement new functionality etc. | |
| |
| |
| |
===== Team Meetings ===== | |
| |
Public meetings: | |
* 2006/12/08 2:00pm | |
* 2006/07/05 9:00am: all systems are GO | |
| |
Development Team meetings are available at [[hekatedev:hekate_meetings]]. | |
| |
| |
===== News ===== | |
* 2007/09/06: Hekate is under heavy development right now, outcomes will be published here ASAP. | |
* 2007/03/29: We have a GO!!! The grant proposal has been accepted!!! | |
* 2006/11/20 00:01: a first article for [[http://www.flairs.com/|Flairs]] conference regarding the project is out | |
* 2006/07/21: The Grant Proposal has been sent -- we just need to sit back and relax waiting for the reply about funding. | |
| |
===== Logo ===== | |
| |
The logo depicts a few triplets: | |
| |
* three faces of Hekate, | |
* Model, View, Controller, | |
* Forward Chaining, Backward Chaining, Human-Computer Interfacing, | |
* Software Engineering, Knowledge Engineering, Interfacing, | |
* Art, Spirit, Science. | |