Inter-Organizational Workflow

1. Context	This is the 2021 summer project of Kevin starting from June 27, 2021 to August 14,2021. Personal Knowledge Container has the potential for data governance.
2. Goal	Develop distributed and centralized security system based on PKC. System integration of content management system and automation tools so that data copy, transfer, and testing could be automated and triggered in PKC. Utilize formal methods to prove the system's soundness Use PKC to manage the project itself so that all the work could be accounted. Theorize the system's structure based on Universal Abstraction.
3. Success Criteria	Important workflows of PKC are specified.
4. Boundary Conditions	6 weeks of project time.

TLA Sub-Model

Logic Model (TLA+) Template:LogicModel 08 23, 2021
Abstract Specification Context To analyze a system correctly before it is implemented, a language to model the system and automatic tools to prove the system is required. Mathematics is more expressive to model system and independent of the order of execution. Goal To efficiently state the system's preferred condition and determine them. Success Criteria The specified property are determined.
Concrete Implementation Given Inputs When Process is executed... Then, we get Outputs TLA+/Input TLA+/Process TLA+/Output
Boundary/Safety Conditions of TLA+ TLA+/Boundary

Jenkins Sub-Model

Logic Model (Jenkins) Template:LogicModel 08 23, 2021
Abstract Specification Context Jenkins/Context Goal Jenkins/Goal Success Criteria Jenkins/Criteria
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

Docker Workflow

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.

Ideation Sub-Model

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

1. Software Resource
2. Work Breakdown Structure
3. Meeting and Communication
4. Issue
5. Updates and reports
6. Documentation
7. Activities
8. PKC Workflow/Drafts
9. Namespace Management

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.