Difference between revisions of "PKC Workflow/Presentation"

From PKC
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?  
* [out] Start from function (input-process-output)
** 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.
* [out] function lacks information indicating (purpose), so need other 4 args
 
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 and contributions ==  
== Work ==  
[work] : tla+  
* Specify and implement several software engineering workflows in the system using the logic model.
[work] : k8s+
** 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
Abstract Specification
Context
  1. This is the 2021 summer project of Tz-Chuang starting from June 27, 2021 to August 21,2021.
  2. Despite the various models for domain knowledge, there isn't a high-level model which is expressive, compact, practical, and independent of domains. This gives rise to Logic Model.
Goal
  1. Utilize formal methods to prove the system's soundness
  2. Use Logic Model to describe the project itself.
  3. Theorize Logic Model based on the implementation.
Success Criteria
  1. An example of how the formal method could integrate into Logic Model is demonstrated.
  2. The Logic Models of the project are defined correctly
  3. The core concepts which explain the Logic Model is defined.
Concrete Implementation
Given Inputs When Process is executed... Then, we get Outputs
System Verification
  1. Software/TLA+ Tools
  2. PKC System Specification
  3. Knowledge/TLA+ Tools

Jenkins Integration

  1. Jenkins setup
  2. A service namespace

Docker Registry

  1. Docker
  2. Docker registry tutorial
  3. Image Naming
  1. System Verification by TLA+
  2. Jenkins Integration
  3. Docker Registry
  4. Meeting and Communication
  5. Issues
  6. Updates
  7. All activities


  1. PKC Workflow/Knowledge
  2. PKC Workflow/Drafts
  3. PKC Workflow/Project Conclusion
  4. PKC Workflow/Presentation
Boundary/Safety Conditions of PKC Workflow
  1. 6 weeks of project time.



Note

Need to give clear examples to listeners.