This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hekate:hekate_concepts [2007/11/26 15:33] gjn alpha, needs figures |
hekate:hekate_concepts [2019/06/27 15:49] (current) |
||
|---|---|---|---|
| Line 69: | Line 69: | ||
| The HeKatE project should eventually provide a coherent runtime environment for running the combined Prolog and Java/C code. | The HeKatE project should eventually provide a coherent runtime environment for running the combined Prolog and Java/C code. | ||
| - | The HeKatE architecture is presented below. | + | {{ :hekate:hekate-design-big.png |Figure: The HeKatE architecture}} |
| - | FIXME | + | |
| From the implementation point of view HeKatE is based on the idea of multiparadigm programming. | From the implementation point of view HeKatE is based on the idea of multiparadigm programming. | ||
| Line 79: | Line 78: | ||
| The logical design which specifies the knowledge base becomes an application executable by a runtime environment, combining an inference engine and classic language runtime (e.g. a JVM). | The logical design which specifies the knowledge base becomes an application executable by a runtime environment, combining an inference engine and classic language runtime (e.g. a JVM). | ||
| - | A concept of the HeKatE application is presented below. | + | {{ :hekate:hekate-hybrid-big.png |Figure: The concept of the HeKatE application}} |
| - | FIXME | + | |
| ====== Methods ====== | ====== Methods ====== | ||
| Currently, the development is focused on the: | Currently, the development is focused on the: | ||
| - | * conceptual design method, codename //ARD+// see [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardformal-submitted]] | + | * conceptual design method, codename //ARD+// see [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardformal]] |
| - | * logical design, codename //XTT+//, also in an extended form as //GREP// see [[:hekate:bib:hekate_bibliography#]], and [[:hekate:bib:hekate_bibliography#ali2008flairs-submitted]] | + | * logical design, codename //XTT+//, also in an extended form as //GREP// see [[:hekate:bib:hekate_bibliography#]], and [[:hekate:bib:hekate_bibliography#ali2008flairs]] |
| * knowledge markup, early stage, see [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]], | * knowledge markup, early stage, see [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]], | ||
| * knowledge translation, early stage, see [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]]. | * knowledge translation, early stage, see [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]]. | ||
| + | |||
| + | |||
| + | |||
| ===== ARD+ ===== | ===== ARD+ ===== | ||
| For a more complete description of ARD+ see | For a more complete description of ARD+ see | ||
| - | [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardprolog-submitted]]. | + | * [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardformal|formal description]]. |
| + | * [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardprolog|Prolog tool]]. | ||
| + | * [[:hekate:bib:hekate_bibliography#gjn2008flairs-userv|UServ example]]. | ||
| The ARD (Attribute Relationships Diagrams) method aims at capturing relations between //attributes// in terms of //Attributive Logic//. | The ARD (Attribute Relationships Diagrams) method aims at capturing relations between //attributes// in terms of //Attributive Logic//. | ||
| Line 107: | Line 110: | ||
| A //physical attribute// is an attribute describing a well-defined, atomic aspect of the system. | A //physical attribute// is an attribute describing a well-defined, atomic aspect of the system. | ||
| Names of physical attributes are not capitalized, e.g. theWaterLevelInTank1. | Names of physical attributes are not capitalized, e.g. theWaterLevelInTank1. | ||
| - | Physical attributes cannot be finalized, they are present in the final rules capturing knowledge about the system. | + | Physical attributes cannot be finalized, they are present in the final rules capturing knowledge about the system.\\ |
| - | FIXME | + | {{:hekate:ard-finalization-ex1.png?500|Figure: General Finalization of an Attribute}} {{:hekate:ard-finalization-ex2.png?500|Figure: Simple Finalization of an Attribute}} |
| There are two transformations allowed during the ARD+ design. | There are two transformations allowed during the ARD+ design. | ||
| Line 117: | Line 120: | ||
| //Split// transforms a complex property into a number of properties and defines functional dependencies among them. | //Split// transforms a complex property into a number of properties and defines functional dependencies among them. | ||
| - | FIXME | + | {{:hekate:ard-split-dep1.png?500|Figure: Dependent Split}} {{:hekate:ard-split-indep1.png?500|Figure: Independent Split}} |
| During the design process, upon splitting and finalization, the ARD model grows. | During the design process, upon splitting and finalization, the ARD model grows. | ||
| Line 125: | Line 128: | ||
| The implementation of such hierarchical model is provided through storing the lowest available, most detailed diagram level at any time, and additional information needed to recreate all of the higher levels, the so-called //Transformation Process History// (TPH). | The implementation of such hierarchical model is provided through storing the lowest available, most detailed diagram level at any time, and additional information needed to recreate all of the higher levels, the so-called //Transformation Process History// (TPH). | ||
| It captures information about changes made to properties at consecutive diagram levels. | It captures information about changes made to properties at consecutive diagram levels. | ||
| + | |||
| + | An example of a complete ARD+ design (the lowest level) is shown below. | ||
| + | |||
| + | {{:hekate:ard-therm-01.png|Figure: ARD design example}} | ||
| + | |||
| + | Based on the ARD, rule prototypes, complying with XTT, can be automatically generated as it is showed below. | ||
| + | |||
| + | {{:hekate:thermostat-varda-xtt.png|:hekate:thermostat-varda-xtt.png}} | ||
| ===== XTT+ ===== | ===== XTT+ ===== | ||
| Line 134: | Line 145: | ||
| On the visual level the model is composed of extended decision tables. | On the visual level the model is composed of extended decision tables. | ||
| - | A single table is presented below. FIXME | + | A single table is presented below. |
| + | |||
| + | {{:hekate:xttp-table.png|Figure: Single XTT Table}} | ||
| The table represents a set of rules, having the same attributes. | The table represents a set of rules, having the same attributes. | ||
| Line 145: | Line 158: | ||
| A link is followed when rule (row) is fired. | A link is followed when rule (row) is fired. | ||
| - | FIXME | + | The structure below, corresponds to the ARD+ design presented above. |
| + | {{:hekate:xtt-structure-therm.png|Figure: An Example of an XTT structure}} | ||
| On the logical level a table corresponds to a number of rules, processed in a sequence. | On the logical level a table corresponds to a number of rules, processed in a sequence. | ||
| Line 158: | Line 172: | ||
| Currently the base XTT is being extended on the syntax level to provide a better expressiveness towards XTT+, or to be applied for more general cases into GREP, see [[:hekate:bib:hekate_bibliography#gjn2007inap]] | Currently the base XTT is being extended on the syntax level to provide a better expressiveness towards XTT+, or to be applied for more general cases into GREP, see [[:hekate:bib:hekate_bibliography#gjn2007inap]] | ||
| - | Another area of development includes formalism extensions, such as temporal and fuzzy, see [[:hekate:bib:hekate_bibliography#ali2008flairs-submitted]] | + | Another area of development includes formalism extensions, such as temporal and fuzzy, see [[:hekate:bib:hekate_bibliography#ali2008flairs]] |
| ===== Markup ===== | ===== Markup ===== | ||
| - | Markup languages currently considered: | + | [[Hekate Markup Language]] considers the following sublanguages: |
| * ATTML (Attribute ML), for attribute only markup | * ATTML (Attribute ML), for attribute only markup | ||
| * ARDML (ARD ML) for conceptual design markup | * ARDML (ARD ML) for conceptual design markup | ||
| Line 170: | Line 185: | ||
| * R2ML interoperability (at XTT level) | * R2ML interoperability (at XTT level) | ||
| - | See | + | See [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]] for some general ideas. |
| - | [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]]. | + | More details at: [[Hekate Markup Language]]. |
| - | for some general ideas. | + | |
| ===== Translation ===== | ===== Translation ===== | ||
| Line 183: | Line 198: | ||
| [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]]. | [[:hekate:bib:hekate_bibliography#gjn2007cms-knowtrans]]. | ||
| for some general ideas. | for some general ideas. | ||
| + | |||
| + | |||
| ====== Process ====== | ====== Process ====== | ||
| - | The HeKatE process is: | + | The [[HeKatE process]] is: |
| * hierarchical, | * hierarchical, | ||
| * integrated, | * integrated, | ||
| * multiaspect. | * multiaspect. | ||
| - | For some ideas see below. | + | For some ideas see below, more info available at [[HeKatE Process]]. |
| - | FIXME | + | |
| + | {{:hekate:new-proc.png|Figure: HeKatE methodology}} | ||
| + | |||
| + | {{:hekate:hlc-beta.png|Figure: HeKatE Process}} | ||
| ====== Applications ====== | ====== Applications ====== | ||
| Line 197: | Line 217: | ||
| * Business Logic Applications (ie. [[hekatedev:business_rules]]) | * Business Logic Applications (ie. [[hekatedev:business_rules]]) | ||
| * General purpose applications | * General purpose applications | ||
| - | * Control systems -- [[:mindstorms]] and [[:hexor]] robot control | + | * Control systems -- [[:mindstorms:start]] and [[misc:hexor]] robot control |
| * Expert Systems | * Expert Systems | ||
| * Databases | * Databases | ||
| Line 203: | Line 223: | ||
| ===== Cases ===== | ===== Cases ===== | ||
| There are several benchmark system design cases considered as the HeKatE testbed. | There are several benchmark system design cases considered as the HeKatE testbed. | ||
| + | |||
| ==== Thermostat ==== | ==== Thermostat ==== | ||
| A classic //control system// case form the AI book by M. Negnevitsky, called the //Thermostat// | A classic //control system// case form the AI book by M. Negnevitsky, called the //Thermostat// | ||
| - | is currently being modeled. | + | is currently being modeled, see [[Hekate Case Thermostat]] and [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardprolog]]. |
| - | See [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardprolog-submitted]]. | + | |
| ==== UServ ==== | ==== UServ ==== | ||
| Line 213: | Line 233: | ||
| (see [[http://www.businessrulesforum.com/2005_Product_Derby.pdf|The Product Derby PDF]]), | (see [[http://www.businessrulesforum.com/2005_Product_Derby.pdf|The Product Derby PDF]]), | ||
| called the //UServ// is currently being modeled. | called the //UServ// is currently being modeled. | ||
| - | See [[:hekate:bib:hekate_bibliography#gjn2008flairs-userv-submitted]] | + | See [[:hekate:bib:hekate_bibliography#gjn2008flairs-userv]] |
| ====== Tools ====== | ====== Tools ====== | ||
| Current development tools include: | Current development tools include: | ||
| - | * VARDA, an ARD+ design and visualization tool, see [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardprolog-submitted]] | + | * VARDA, an ARD+ design and visualization tool, see [[:hekate:bib:hekate_bibliography#gjn2008flairs-ardprolog]] |
| * HQed, an XTT+ editor, see [[:hekate:bib:hekate_bibliography#gjn2007cms-destls-accepted]] | * HQed, an XTT+ editor, see [[:hekate:bib:hekate_bibliography#gjn2007cms-destls-accepted]] | ||
