Różnice między wybraną wersją a wersją aktualną.
| Nowa wersja | Poprzednia wersja | ||
|
pl:miw:2009:piw09_hades_1:hekate_case_hello [2009/06/09 21:39] piw09 utworzono |
pl:miw:2009:piw09_hades_1:hekate_case_hello [2019/06/27 15:50] (aktualna) |
||
|---|---|---|---|
| Linia 1: | Linia 1: | ||
| ====== The HeKatE Case HELLO ====== | ====== The HeKatE Case HELLO ====== | ||
| - | Eliasz Kańtoch | + | Eliasz Kańtoch, |
| Tomasz Michalski | Tomasz Michalski | ||
| Linia 10: | Linia 10: | ||
| ====== Stages ====== | ====== Stages ====== | ||
| - | |||
| - | The process is involves the following the stages described below. | ||
| ===== Description ===== | ===== Description ===== | ||
| Linia 18: | Linia 16: | ||
| ===== Conceptualization ===== | ===== Conceptualization ===== | ||
| - | In this stage some primary concepts are identified. | ||
| - | These can be //attributes//, //properties//, //objects// (in the general sense), or //rules//. | ||
| - | The output of this stage is a preliminary list of possible //attributes//, //properties//. | ||
| - | The list //may be// somehow structured, or formalized. | ||
| - | Though, it is not mandatory. | ||
| ==== Vocabulary ==== | ==== Vocabulary ==== | ||
| - | *Greeting is a text that consists of salutation and title of the person. | + | * Greeting is a text that consists of salutation and title of the person. |
| - | *Salutation is one of the following: Good Morning, Good Afternoon, Good Evening, Good Night. | + | * Salutation is one of the following: Good Morning, Good Afternoon, Good Evening, Good Night. |
| - | *Title of person is based on status of the person. | + | * Title of person is based on status of the person. |
| - | *Status are age,martial status and gender. | + | * Status are age,martial status and gender. |
| - | *Gender – male albo female | + | * Gender – male or female |
| - | *Martial status – married i single | + | * Martial status – married and single |
| + | |||
| ==== Original Rules ==== | ==== Original Rules ==== | ||
| - | In a case where an already designed system is being modeled, some ready rules can be provided. | + | |
| - | In the H approach these rules should be considered a mean of conceptualization only. | + | |
| - | These rules are often informal, or semi-formal. | + | |
| - | In the [[business rules]] approach number of rule types are identified, that do not map in a straightforward way to the H logical design. | + | |
| <code> | <code> | ||
| Rule: 1 | Rule: 1 | ||
| - | if the Hour is 'between 0 and 11' | + | if the hour is 'between 0 and 11' |
| - | then Greeting is 'Good morning' | + | then greeting is 'Good morning' |
| Rule: 2 | Rule: 2 | ||
| - | if the Hour is 'between 12 and 17' | + | if the hour is 'between 12 and 17' |
| - | then Greeting is 'Good afternoon' | + | then greeting is 'Good afternoon' |
| Rule: 3 | Rule: 3 | ||
| - | if the Hour is 'between 18 and 22' | + | if the hour is 'between 18 and 22' |
| - | then Greeting is 'Good evening' | + | then greeting is 'Good evening' |
| Rule: 4 | Rule: 4 | ||
| - | if the Hour is 'between 23 and 24' | + | if the hour is 'between 23 and 24' |
| - | then Greeting is 'Good night' | + | then greeting is 'Good night' |
| + | Rule: 5 | ||
| + | if the gender is female | ||
| + | and marital status is married | ||
| + | then title is 'Mrs' | ||
| - | </code> | + | Rule: 6 |
| + | if the gender is female | ||
| + | and marital status is single | ||
| + | then title is 'Ms' | ||
| + | Rule: 7 | ||
| + | if the gender is male | ||
| + | then title is 'Mr' | ||
| + | Rule: 9 | ||
| + | if the gender is female | ||
| + | and marital status is single | ||
| + | and age < 10 | ||
| + | then title is 'Little' | ||
| - | ===== Conceptual design ===== | ||
| - | The conceptual design stage is the beginning of the formalized hierarchical process. | + | </code> |
| - | Based on the concepts, or vocabulary, the ARD properties and attributes are being identified, as well as functional dependencies between them stated. | + | |
| - | See the [[ARDplus]] design for the detailed specification. | + | ===== Analysis ===== |
| - | The output of this stage is the low-level [[ARDplus]] diagram with //physical attributes//, plus attribute domains, and types description. | ||
| - | This output as a whole is [[:hekate:hekate_process#encoding|encoded]] with use of the [[HeKatE Markup Language]]. | + | Input danta: hour, gender, martial_status and age. |
| + | Output data: combination salutation with title. | ||
| - | ==== General Conceptual Design ==== | + | Buiding ARD model starts from level 0 and attribute HelloSystem. Attribute is finalized into two attributes Greeting and Salutation and one physical attribute invitation. Next step is to show relation between attributes that were created. Attribute invitation is the input to the system it depends on two attributes. On the level 4 there is finalization Salutation into four phisical attributes gender, martial_status, salutation_text and age. On the next level Greeting is finalized to hour and greeting_text. Level six is the last level, where there are all dependences. |
| - | In a general case, the ARD diagram is built using the vocabulary previously identified. | + | |
| - | ==== Directed Conceptual Design ==== | ||
| - | In a case where the [[hekate_process:original rules]] were provided, the physical attributes identified during the design should match the original rules. | ||
| - | The lowest ARD level should match the structure of the original rule-base. | ||
| - | ==== Refined Conceptual Design ==== | + | ===== Conceptual design ===== |
| - | This is also a case where the [[hekate_process:original rules]] were provided. | + | |
| - | However, the design is not aimed at matching the original rule-base. | + | |
| - | The goal is to improve the original design with the HeKatE approach. | + | |
| - | ===== Physical Attribute Specification ===== | + | ==== General Conceptual Design ==== |
| - | This is actually the partial output of the [[:hekate:hekate_process#conceptual design]] | + | |
| - | in a //standalone// form, that is only the appropriate [[:hekate:hekate_process#ATTML]] encoding. | + | |
| - | It is a natural input for the next stage. | + | |
| - | It is also a point, where the formalized [[attribute specification]] can be shared with other systems, tools and approaches. | + | |
| - | TBC: | ||
| - | at this stage it should be possible to import attributes from other formalized sources, e.g. RIF-based systems. | ||
| - | TBC: | + | ==== Directed Conceptual Design ==== |
| - | this should be compatible with the attributive logic concepts and definitions. | + | |
| - | ===== Structuralization ===== | ||
| - | Using a partial output of the [[:hekate:hekate_process#conceptual design]] | + | === Full Optimized Design === |
| - | that is only the apropriate [[hekate markup language|ARDML]] dependencies. | + | |
| - | In this stage a fully or semi automated generation of the XTT table schemas (rule prototypes) is performed. | ||
| - | Using the lowest ARD level XTT schemes are generated. | ||
| - | The inference structure (table-to-table links) is also built which serve as a guideline for future XTT processing order. | ||
| - | The algorithm is given in the //ECAI submission// FIXME. | + | === Full ARD Model === |
| - | The //output// of this stages is the XTT schemes structure [[:hekate:hekate_process#encoding|encoded]] with the use of the [[XTTML]]. | ||
| - | ===== Logical design ===== | ||
| - | In this stage the actual design of the [[XTT]] tables is put forward. | ||
| - | Tables are filled with rules, and extra, fine-grained links can be added (row-to-row) links. | ||
| - | See the [[XTT]] design for the detailed specification. | + | Diagram genereted with HQEd M6_6: \\ |
| - | WIP: | ||
| - | The application of the XTT+ a.k.a. GREP extensions should be considered here, with: | ||
| - | * grouped attributes | ||
| - | * scope operators | ||
| - | Things that seem to be needed, in the final verision, but too complex now: | ||
| - | * hybrid operators (HOP) | ||
| - | Things considered to complex for the first implementation are: FIXME | ||
| - | * labeled links | ||
| - | * other GREP? | ||
| + | The full hierarchical diagram is presented below:\\ | ||
| + | {{:pl:miw:2009:piw09_hades_1:hello_levels.png?500|}} | ||
| - | The //output// of this stages is the full XTT structure [[:hekate:hekate_process#encoding|encoded]] with the use of the [[XTTML]]. | ||
| - | ===== On-Line Analysis ===== | + | Diagrams design in VARADA M_3 : {{:pl:miw:2009:piw09_hades_1:hello-model.pl|}} |
| - | In this stage the logical description of the XTT is used to conduct a formal analysis of selected formal properties such as: | + | |
| - | * completeness | + | |
| - | * redundancy -> knowledge optimization | + | |
| - | * determinism | + | |
| - | * inference -> inference optimization | + | |
| - | * other? | + | |
| - | WIP | ||
| - | currently only some old experiences form the original XTT are available. | ||
| - | TBC | + | ARD model was designed using Varda M_3: \\ |
| - | Several aspects, cases, classes, levels should be considered, e.g.: | + | {{:pl:miw:2009:piw09_hades_1:hello-model.dot.png?350|}} |
| - | * local (table) vs. global (diagram) | + | \\ dot file: {{:pl:miw:2009:piw09_hades_1:hello-model.dot|}} |
| - | * relation to scope operators | + | |
| - | * relation to grouped attributes | + | |
| + | The TPH for this model is: \\ | ||
| + | {{:pl:miw:2009:piw09_hades_1:hello-model_tph.dot.png?350|}} | ||
| + | \\ dot file: {{:pl:miw:2009:piw09_hades_1:hello-model_tph.dot|}} | ||
| - | ===== Physical Design ===== | + | TPH and ARD combined: \\ |
| - | The executable design generation. | + | {{:pl:miw:2009:piw09_hades_1:hello-model-tphard.dot.png?400|}} |
| - | ==== Prolog Implementation ==== | ||
| - | The XTT representation has a clear, well-defined Prolog representation. | ||
| - | This representation is fully automatically generated from the XTT design. | ||
| - | WIP | ||
| - | currently only some old experiences form the original XTT are available. | ||
| - | TBC | ||
| - | Integration of BLOBS, data structures, lists, etc, has to be considered. | ||
| - | So is the use and integration of the HOP. | ||
| - | ==== UML Serialization ==== | + | ARD model desiged with HJEd : \\ |
| - | WIP | + | {{:pl:miw:2009:piw09_hades_1:hello_model_ard.png?400|}} |
| - | An object-oriented serialization of the XTT is to be provided. | + | |
| - | It should match UML on the diagram level, and Java on the code level. | + | |
| - | WIP | + | The TPH for this model is: \\ |
| - | Current naive idea is to map | + | {{:pl:miw:2009:piw09_hades_1:hello_model_tph.png?450|}} |
| - | * tables -> objects | + | |
| - | * attributes -> attributes | + | |
| - | * rules -> methods | + | |
| - | ==== Rule Engine Implementation ==== | ||
| - | WIP | ||
| - | Generate rules for some well-established rule engines, such as Drools. | ||
| - | ====== Integration ====== | + | ==== Refined Conceptual Design ==== |
| - | The stages are integrated with: | + | |
| - | * knowledge encodings | + | |
| - | * transformations | + | |
| - | * other? | + | |
| - | FIXME | + | ===== Physical Attribute Specification ===== |
| - | This needs filling! | + | |
| - | ===== Encoding ===== | + | ===== Structuralization ===== |
| - | Currently XML encodings to be used: | + | |
| - | * ATTML | + | |
| - | * ARDML | + | |
| - | * XTTML | + | |
| - | The are now integrated into //HML// the [[Hekate Markup Language]]. | + | |
| - | ===== Knowledge Markups ===== | + | XTT prototype generated by [[VARDA]]: \\ |
| - | Aspects: | + | |
| - | * the stack: XML -> RDF -> RIF -> R2ML | + | |
| - | * ATTML <-> RDF | + | |
| - | * RIF <-> ARD | + | |
| - | * RIF <-> XTT | + | |
| - | * R2ML <-> XTT | + | |
| - | * ontologies <-> ATTML | + | |
| - | * ontologies <-> ARDML | + | |
| - | ===== Transformations ===== | + | {{:pl:miw:2009:piw09_hades_1:hello-model_xtt.dot.png?500|}} |
| - | FIXME | + | |
| - | ====== Tools ====== | + | ===== Logical design ===== |
| - | Current tools: | + | |
| - | * VARDA | + | |
| - | * HQed | + | |
| + | Design made by HQed M6_6 | ||
| - | ====== Case Template ====== | ||
| - | |||
| - | <code> | ||
| - | ====== Introduction ====== | ||
| - | |||
| - | ===== Description ===== | ||
| - | |||
| - | ===== Conceptualization ===== | ||
| - | |||
| - | ==== Vocabulary ==== | ||
| - | |||
| - | ==== Original Rules ==== | ||
| - | |||
| - | ===== Analysis ===== | ||
| - | |||
| - | ===== Conceptual design ===== | ||
| - | |||
| - | ==== General Conceptual Design ==== | ||
| - | |||
| - | ==== Directed Conceptual Design ==== | ||
| - | |||
| - | === Full ARD Model === | ||
| - | |||
| - | ==== Refined Conceptual Design ==== | ||
| - | |||
| - | ===== Physical Attribute Specification ===== | ||
| - | |||
| - | ===== Structuralization ===== | ||
| - | |||
| - | ===== Logical design ===== | ||
| - | |||
| - | </code> | ||
| + | {{:pl:miw:2009:piw09_hades_1:hello_model2.png?600|}} | ||
