PKC Workflow/Process

1. PKC Workflow/Work Breakdown Structure
2. PKC Workflow/System Verification
3. PKC Workflow/Jenkins Integration
4. PKC Workflow/Task/Docker Installation
5. PKC Workflow/Meeting and Communication
6. PKC Workflow/Issues
7. PKC Workflow/Updates
8. All activities

When describing a process, it could be confusing as a process relates some inputs to outputs. The information entity such as Issue could mean either a process of issuing or the issue result presenting as a page.

When describing a process in the macroscope, it is always a verb. The input/output is defined according to the function's specification.

Inputs - [Process] -> Outputs

<graphviz> digraph G {

   rankdir=LR
   input [URL="PKC Workflow/Input"];
   process [URL="PKC Workflow/Process"];
   output [URL="PKC Workflow/Output"];
   input->process;
   process->output;

} </graphviz>

There are 2 possible reasons why the input/output might be incomplete:

1. Stateful functions which cause side effects or dependence on global variables: It is the trade-off when using functional representation. To stick to the functional representation style, we should think about how to reorganize the function so that it is closer to stateless.
2. Not capturing the input/output that a function cares about: Ideally, every input/output should be captured at least in low precision (type system). But since there are complexity and obscurity when describing real-world knowledge, it is possible that the input/output is incomplete.

When describing the inner structure of a process, there are more kinds of modeling methods (we can see this in the complexity of programming). It is feasible to add more structure (corresponding to different semantics) but note that a compact structure (desired traits of knowledge representation) is preferable.

Loop

In the simplest form, the process is the mapping of input to output. To describe the recurring event in the project, we add a Loop structure on top of it. See the LoopingConstructs Primitive in Mathematica The diagram representing the function with loop will be:

• (Need to specify the LISP processing language, which is its origin)
• Everything is a list

Inputs -> Process -> Outputs
Process -> Process

<graphviz> digraph G {

   rankdir=LR
   input [URL="PKC Workflow/Input"];
   process [URL="PKC Workflow/Process"];
   output [URL="PKC Workflow/Output"];
   input->process;
   process->process [label="recursive"];
   process->output;

} </graphviz>

States and Local Variables

In a process, there are data generated alongside but isn't intended to serve as the output or expose outside the process. In programming, it corresponds to Module and Localization. In PKC Workflow, the following pages

serve as this kind of localized resource.

1. Meeting and Communication
2. Issue
3. Activities
4. Updates and reports

Subprocess

Modular programming is a software design technique that emphasizes separating the functionality of a program into independent, interchangeable modules, such that each contains everything necessary to execute only one aspect of the desired functionality. A Process in Logic Model could be divided into SubModels. How Logic model relates with SubModels All the submodels in PKC Workflow:

Logic Model (TLA Workflow) Template:LogicModel 08 28, 2021
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 (PKC Workflow/Jenkins Integration) Template:LogicModel 08 28, 2021
Abstract Specification Context The Universal Data Abstraction includes data scheme of Page/File/Service. Jenkins is an automation server for users to interact with services. Goal To integrate automation server with PKC to build a workflow engine Success Criteria Users could manipulate programmable objects on other application in PKC page.
Concrete Implementation Given Inputs When Process is executed... Then, we get Outputs Jenkins setup A service namespace Specify a namespace to express the interaction with service. Activity:Learn Lua Create a Lua based module which takes parametrized inputs. A complete service namespace. A module serving as interface for users to interact
Boundary/Safety Conditions of PKC Workflow/Jenkins Integration Finish within 1 week of time

Logic Model (PKC Workflow/Task/Docker Installation) Template:LogicModel 08 28, 2021
Abstract Specification Context The Mediawiki container on thewiki.us contains software which are constantly changing. Goal Specify and docker registry workflow of PKC and test. Success Criteria The process are investigated and streamlined. Users follow and improve the workflow. The tags are named properly.
Concrete Implementation Given Inputs When Process is executed... Then, we get Outputs Docker Docker registry tutorial Image Naming 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. All Images
Boundary/Safety Conditions of PKC Workflow/Task/Docker Installation By now we only test the workflow on thewiki.us server. More servers should be tested in the future.

Branch primitive

FlowControl primitives of Mathematica