Difference between revisions of "Inter-Organizational Workflow"

From PKC
Jump to navigation Jump to search
Line 15: Line 15:
# 6 weeks of project time.
# 6 weeks of project time.
}}
}}
notes:
output: concept-instance difference.
inputs: system spec:
intended to use Function Model, but turn to Logic model to specify intention.
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 question is: What is the relationship between the model submodules, and the relationships among all the subfunctions?


<section begin=TLA Logic Model />
<section begin=TLA Logic Model />
Line 48: Line 40:
# Finish within 1 week of time
# Finish within 1 week of time
}}
}}
# Modeling system in the code-level depends on the order of execution while modeling with logical conditions doesn't. 
<section end=TLA Logic Model />
todo : meta data of "the op data?" of writing a logic model


<section end=TLA Logic Model />


== Jenkins Sub-Model ==  
== Jenkins Sub-Model ==  
Line 75: Line 65:
# Finish within 1 week of time  
# Finish within 1 week of time  
}}
}}
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.


== [[Docker Workflow]]==  
== [[Docker Workflow]]==  
Line 130: Line 118:
# [[All activities|Activities]]
# [[All activities|Activities]]
# [[PKC Workflow/Drafts]]
# [[PKC Workflow/Drafts]]
== 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.
==Reference==
==Reference==

Revision as of 14:57, 25 July 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

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

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


Jenkins 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
  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. REDIRECT Process/Docker Workflow
  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

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.

Reference

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