Difference between revisions of "Inter-Organizational Workflow"

From PKC
Jump to navigation Jump to search
Line 16: Line 16:
}}
}}


<section begin=TLA Logic Model />
== TLA Sub-Model ==  
== TLA Sub-Model ==  
{{LogicModel
{{LogicModel
|name = TLA+  
|name = TLA+  
}}
}}
{{Logic Model 2
|name=TLA Workflow
|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.
|criteria=
# The [[PKC System Specification|specified property]] are determined.
|outputs=
# The TLA tools are set up
# The [[PKC System Result]] are shown.
|process=
# [[Job/TLA+ Installation]]
# [[Job/PKC System Specification]]


|inputs=  
== Jenkins Sub-Model ==  
# [[TLA+|Formal Tools]]
{{LogicModel
# [[PKC System Specification]]
|name = Jenkins
|boundaries=
# Determine what the PKC system should achieve.
# Finish within 1 week of time
}}
}}
<section end=TLA Logic Model />


== Jenkins Sub-Model ==
 
{{Logic Model  
{{Logic Model  
|context=  
|context=  
Line 126: Line 106:
* 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.
* 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.


==Reference==
==Reference==

Revision as of 03:51, 23 August 2021


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


TLA Sub-Model

Logic Model (TLA+) Template:LogicModel 08 23, 2021
Abstract Specification
Context
  1. To analyze a system correctly before it is implemented, a language to model the system and automatic tools to prove the system is required.
  2. Mathematics is more expressive to model system and independent of the order of execution.
Goal
  1. To efficiently state the system's preferred condition and determine them.
Success Criteria
  1. 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
  1. The Universal Data Abstraction includes data scheme of Page/File/Service.
  2. Jenkins is an automation server for users to interact with services.
2. Goal
  1. To integrate automation server with PKC to build a workflow engine
3. Success Criteria
  1. Users could manipulate programmable objects on other application in PKC page.
4. Outputs 5. Process 6. Inputs
  1. A complete service namespace.
  2. A module serving as interface for users to interact
  1. Specify a namespace to express the interaction with service.
  2. Activity:Learn Lua
  3. Create a Lua based module which takes parametrized inputs.
  1. Jenkins setup
  2. A service namespace
7. Boundary Conditions
  1. 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
  1. The Mediawiki container on thewiki.us contains software which are constantly changing.
2. Goal
  1. Specify and docker registry workflow of PKC and test.
3. Success Criteria
  1. The process are investigated and streamlined.
  2. Users follow and improve the workflow.
  3. The tags are named properly.
4. Outputs 5. Process 6. Inputs
  1. A workflow page.
  2. Pull and build a docker registry image from the official website. [1].
  3. For the target container to be versioned, commit the container.
  4. Push to the local registry and then test whether it succeeded.
  5. Install some extensions and make a software version from it.
  1. Knowledge from Docker.
  2. Docker registry tutorial
  3. Image Naming
7. Boundary Conditions
  1. 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
  1. To model and formalize the structure of Ideation.
  2. Leverage PKC as the foundation for Ideation.
3. Success Criteria
  1. Specify Ideation structure
  2. Specify how PKC could process these ideas.
4. Outputs 5. Process 6. Inputs
  1. Ideation structure specification
  2. PKC application on Ideation specification

Status:Uncertain

Status:Uncertain

7. Boundary Conditions
  1. 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.


Reference

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