Inter-Organizational Workflow

Abstract Specification
Context	This is the 2021 summer project of Tz-Chuang starting from June 27, 2021 to August 21,2021. 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	Utilize formal methods to prove the system's soundness Use Logic Model to describe the project itself. Theorize Logic Model based on the implementation.
Success Criteria	An example of how the formal method could integrate into Logic Model is demonstrated. The Logic Models of the project are defined correctly The core concepts which explain the Logic Model is defined.

Concrete Implementation
Given Inputs	When Process is executed...	Then, we get Outputs
System Verification Software/TLA+ Tools PKC System Specification Knowledge/TLA+ Tools Jenkins Integration Jenkins setup A service namespace Docker Registry Docker Docker registry tutorial Image Naming	System Verification by TLA+ Jenkins Integration Docker Registry Meeting and Communication Issues Updates All activities	PKC Workflow/Knowledge PKC Workflow/Drafts PKC Workflow/Project Conclusion PKC Workflow/Presentation

Boundary/Safety Conditions of PKC Workflow
6 weeks of project time.

TLA Workflow

Abstract Specification
Context	REDIRECT PKC Workflow/System Verification by TLA+/Context
Goal	REDIRECT PKC Workflow/System Verification by TLA+/Goal
Success Criteria	REDIRECT PKC Workflow/System Verification by TLA+/Criteria

Concrete Implementation
Given Inputs	When Process is executed...	Then, we get Outputs
REDIRECT PKC Workflow/System Verification by TLA+/Input	REDIRECT PKC Workflow/System Verification by TLA+/Process	REDIRECT PKC Workflow/System Verification by TLA+/Output

Boundary/Safety Conditions of TLA Workflow
REDIRECT PKC Workflow/System Verification by TLA+/Boundary

Logic Model (Jenkins) Template:LogicModel 08 23, 2021

Concrete Implementation
Given Inputs	When Process is executed...	Then, we get Outputs
Jenkins/Input	Jenkins/Process	Jenkins/Output

Boundary/Safety Conditions of Jenkins
Jenkins/Boundary

TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel

1. Context	The Universal Data Abstraction includes data scheme of Page/File/Service. Jenkins is an automation server for users to interact with services.
2. Goal	To integrate automation server with PKC to build a workflow engine
3. Success Criteria	Users could manipulate programmable objects on other application in PKC page.
4. Outputs	5. Process	6. Inputs
A complete service namespace. A module serving as interface for users to interact	Specify a namespace to express the interaction with service. Activity:Learn Lua Create a Lua based module which takes parametrized inputs.	Jenkins setup A service namespace
7. Boundary Conditions	Finish within 1 week of time

TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel

1. Context	The Mediawiki container on thewiki.us contains software which are constantly changing.
2. Goal	Specify and docker registry workflow of PKC and test.
3. Success Criteria	The process are investigated and streamlined. Users follow and improve the workflow. The tags are named properly.
4. Outputs	5. Process	6. Inputs
A workflow page.	Pull and build a docker registry image from the official website. [1]. For the target container to be versioned, commit the container. Push to the local registry and then test whether it succeeded. Install some extensions and make a software version from it.	Knowledge from Docker. Docker registry tutorial Image Naming
7. Boundary Conditions	By now we only test the workflow on thewiki.us server. More servers should be tested in the future.

TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel

1. Context	Ideation Project
2. Goal	To model and formalize the structure of Ideation. Leverage PKC as the foundation for Ideation.
3. Success Criteria	Specify Ideation structure Specify how PKC could process these ideas.
4. Outputs	5. Process	6. Inputs
Ideation structure specification PKC application on Ideation specification	Status:Uncertain	Status:Uncertain
7. Boundary Conditions	Finish within 1 week of time

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.