Difference between revisions of "Inter-Organizational Workflow"

From PKC
Jump to navigation Jump to search
Line 2: Line 2:




== TLA Workflow ==
{{LogicModel
|name = TLA Workflow
}}
== Jenkins Sub-Model ==
{{LogicModel
|name = Jenkins
}}
{{Logic Model
|context=
# The [[Universal Data Abstraction]] includes data scheme of [[Page/File/Service]]. 
# Jenkins is an automation server for users to interact with services.
|goal=
# To integrate automation server with PKC to build a workflow engine
|criteria=
# Users could manipulate programmable objects on other application in PKC page.
|outputs=
# A complete service namespace. 
# A module serving as interface for users to interact
|process=
# Specify a namespace to express the interaction with service. 
# [[Activity:Learn Lua]]
# Create a Lua based module which takes parametrized inputs. 
|inputs=
# Jenkins setup
# A service namespace
|boundaries=
# Finish within 1 week of time
}}
== [[Docker Workflow]]==
{{Logic Model
|context=
# The Mediawiki container on thewiki.us contains software which are constantly changing.
|goal=
# Specify and docker registry workflow of PKC and test. 
|criteria=
# The process are investigated and streamlined.
# Users follow and improve the workflow.
# The tags are named properly. 
|outputs=
# A workflow page.
|process=
# {{:Process/Docker Workflow}}
|inputs=
# Knowledge from [[Docker]].
# [https://docs.docker.com/registry/ Docker registry tutorial]
# [https://docs.docker.com/registry/introduction/#understanding-image-naming Image Naming]
|boundaries=
# By now we only test the workflow on thewiki.us server.  More servers should be tested in the future.
}}
== Ideation Sub-Model ==
{{Logic Model
|context= [[Ideation Project]]
|goal=
# To model and formalize the structure of Ideation.
# Leverage PKC as the foundation for Ideation. 
|criteria=
# Specify Ideation structure
# Specify how PKC could process these ideas.   
|outputs=
# Ideation structure specification
# PKC application on Ideation specification
|process=
[[Status:Uncertain]]
|inputs=
[[Status:Uncertain]]
|boundaries=
# Finish within 1 week of time
}}


== Notes ==  
== Notes ==  

Revision as of 08:10, 23 August 2021

Logic Model (PKC Workflow) Template:LogicModel 08 23, 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.


Notes

  • When writing a logic model, one should be aware of the difference between concept and instance.
  • A logic model is composed of lots of submodels. When not intending to specify the abstract part of them, one could only use Function Model.
  • What is the relationship between the model submodules, and the relationships among all the subfunctions?
  • Note: Sometimes, the input and process are ambiguous. For example, the Service namespace is required to achieve the goal. It might be an input or the product along the process. In general, both the input and process contain uncertainty and need a decision.
  • The parameter of Logic Model is minimized to its name, which is the most important part of it. The name should be summarized from its value.
  • Note that, when naming as Jenkins, it means the resource itself, but when naming as Jenkin Implementation On PKC, it consists of more context information therefore is more suitable.

Reference

Retrieved from "https://pkc.pub/index.php?title=Inter-Organizational_Workflow&oldid=10002"