Difference between revisions of "Inter-Organizational Workflow"

Revision as of 14:58, 25 July 2021

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.

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

1. 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.
2. Goal	To efficiently state the system's preferred condition and determine them.
3. Success Criteria	The specified property are determined.
4. Outputs	5. Process	6. Inputs
The TLA tools are set up The PKC System Result are shown.	Task:TLA+ Installation Task:PKC System Specification	Formal Tools PKC System Specification
7. Boundary Conditions	Determine what the PKC system should achieve. 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 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.	REDIRECT Process/Docker Workflow	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.

@@ Line 120: / Line 120: @@
 == Notes ==
-When writing a logic model, one should be aware of the difference between concept and instance.
+* 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.
+* 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?
+* 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.
+* 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.
 ==Reference==