PKC Workflow/Process

From PKC
Revision as of 05:55, 23 August 2021 by KevinTung (talk | contribs)
Jump to navigation Jump to search
  1. Meeting and Communication
  2. Issue
  3. Updates and reports
  4. All activities


Note

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.

Inputs - [Process] -> Outputs

Where the input/output is defined according to the function's specification. 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.


Recurring

Non-recurring (normal)