Difference between revisions of "PKC Workflow/Presentation"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Introduction of Logic Model == | == Introduction of Logic Model == | ||
Navigate: [[Template:Logic Model]] | Navigate: [[Template:Logic Model]] | ||
* What is logic model? | * What is logic model? | ||
* | ** The syntax for filling up the Template is as two parts. The top part, surrounded by a blue dashline, is the abstract specification of a function. Describing what it is. The bottom part, surrounded by a red dashline, is the concrete implementation, revealing the resources and strategies to realize the cause-effect linkage between the abstraction specification with the concrete implementation and execution. The two parts, top and bottom of a Logic Model is shown below: (The blue part represents the abstraction specification, or the signature of a function. The red part represents the concrete implementation, which can be considered as the body of a function. Then, all techniques for functional composition can be applied to Logic Model, and henceforth, applied to anything that Logic Model represents. | ||
* | |||
Navigate: [[Logic Model/Example/Buying Coffee]] | ** | ||
* [out]: the coffee example | * Origin of LM: | ||
** It origins from Symmetry-breaking. | |||
* The relation with knowledge representation and programming language: | |||
* Logic model is a meta-language independent of domain | |||
** Benefit: test, goal model purpose, context locates the purpose, criteria? could test the goal | |||
Coffee example in a picture (Navigate): [[Logic Model/Example/Buying Coffee]] | |||
* [out]: the coffee example | |||
== Language == | |||
== TLA+ == | |||
Curry Howard correspondence : Logic language, and Functional Language . | |||
== Work | == Work == | ||
* Specify and implement several software engineering workflows in the system using the logic model. | |||
** It serves as a Workflow engine (due to the structure) | |||
tla+, docker registry , ..? | |||
== PKC == | == PKC == |
Latest revision as of 17:41, 29 August 2021
Introduction of Logic Model
Navigate: Template:Logic Model
- What is logic model?
- The syntax for filling up the Template is as two parts. The top part, surrounded by a blue dashline, is the abstract specification of a function. Describing what it is. The bottom part, surrounded by a red dashline, is the concrete implementation, revealing the resources and strategies to realize the cause-effect linkage between the abstraction specification with the concrete implementation and execution. The two parts, top and bottom of a Logic Model is shown below: (The blue part represents the abstraction specification, or the signature of a function. The red part represents the concrete implementation, which can be considered as the body of a function. Then, all techniques for functional composition can be applied to Logic Model, and henceforth, applied to anything that Logic Model represents.
- Origin of LM:
- It origins from Symmetry-breaking.
- The relation with knowledge representation and programming language:
- Logic model is a meta-language independent of domain
- Benefit: test, goal model purpose, context locates the purpose, criteria? could test the goal
Coffee example in a picture (Navigate): Logic Model/Example/Buying Coffee
- [out]: the coffee example
Language
TLA+
Curry Howard correspondence : Logic language, and Functional Language .
Work
- Specify and implement several software engineering workflows in the system using the logic model.
- It serves as a Workflow engine (due to the structure)
tla+, docker registry , ..?
PKC
(Basic intro)
Logic Model
- What is logic model
Logic Model of PKC Workflow
Logic Model (PKC Workflow) Template:LogicModel 08 29, 2021 | ||||||
---|---|---|---|---|---|---|
| ||||||
| ||||||
|
Note
Need to give clear examples to listeners.