Difference between revisions of "Process"
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
An organized set of actions or sub-processes that takes inputs and transforms them into outputs. | An organized set of actions or sub-processes that takes [[inputs]] and transforms them into [[outputs]]. | ||
<noinclude> | <noinclude> | ||
In [[Logic Model]], a [[Process]] is a function that maps [[Inputs]] to [[Outputs]]. Technically speaking, a Process is inseparable from [[Inputs]] and [[Outputs]], therefore, a Process can be considered as a system of [[Resource]]s. From an operational viewpoint, every Process should be associated with a [[timeline]], which specifies the starting and ending points of process execution in real-world time. | In [[Logic Model]], a [[Process]] is a function that maps [[Inputs]] to [[Outputs]]. Technically speaking, a Process is inseparable from [[Inputs]] and [[Outputs]], therefore, a Process can be considered as a system of [[Resource]]s. From an operational viewpoint, every Process should be associated with a [[timeline]], which specifies the starting and ending points of process execution in real-world time. | ||
| Line 5: | Line 5: | ||
=Process in the era of Big Data= | =Process in the era of Big Data= | ||
To help explain the nature of a process, [[Ansible]] as a tool came out particularly relevant. It provides a process abstraction model that unified a number of essential ideas that [[PKC]] promotes as architectural elements: | To help explain the nature of a process, [[Ansible]] as a tool came out particularly relevant. It provides a process abstraction model that unified a number of essential ideas that [[PKC]] promotes as architectural elements: | ||
# The [[yaml]] format data representation for its programming language, which subscribes to the notion of [[key value]] representation of data. | # The [[yaml]] format data representation for its programming language, which subscribes to the notion of [[key-value pair]] representation of data. | ||
# Multi-layered annotation of a task/process, which is similar to [[Logic model]]. | # Multi-layered annotation of a task/process, which is similar to [[Logic model]]. | ||
# Directly programmable to perform [[sequential]] and [[parallel]] tasks on networked computing resources. | # Directly programmable to perform [[sequential]] and [[parallel]] tasks on networked computing resources. | ||
# Provides both [[declarative]] and [[imperative]] programming models. | # Provides both [[declarative]] and [[imperative]] programming models. | ||
=Processes should be modeled as Dynamical Systems= | |||
All processes by definition must deal with ordered events. To represent dynamical systems using simple primitives, [[Category Theory]] offers a highly condensed notation to describe dynamical systems. [[Richard Southwell]] has a video tutorial on dynamical systems<ref>{{:Video/Category Theory For Beginners: Graphs And Dynamical Systems}}</ref>. | |||
<noinclude> | <noinclude> | ||
=References= | =References= | ||
<references/> | <references/> | ||
Latest revision as of 02:00, 29 March 2023
An organized set of actions or sub-processes that takes inputs and transforms them into outputs.
In Logic Model, a Process is a function that maps Inputs to Outputs. Technically speaking, a Process is inseparable from Inputs and Outputs, therefore, a Process can be considered as a system of Resources. From an operational viewpoint, every Process should be associated with a timeline, which specifies the starting and ending points of process execution in real-world time.
Process in the era of Big Data
To help explain the nature of a process, Ansible as a tool came out particularly relevant. It provides a process abstraction model that unified a number of essential ideas that PKC promotes as architectural elements:
- The yaml format data representation for its programming language, which subscribes to the notion of key-value pair representation of data.
- Multi-layered annotation of a task/process, which is similar to Logic model.
- Directly programmable to perform sequential and parallel tasks on networked computing resources.
- Provides both declarative and imperative programming models.
Processes should be modeled as Dynamical Systems
All processes by definition must deal with ordered events. To represent dynamical systems using simple primitives, Category Theory offers a highly condensed notation to describe dynamical systems. Richard Southwell has a video tutorial on dynamical systems[1].
References
- ↑ Southwell, Richard (Sep 11, 2019). Category Theory For Beginners: Graphs And Dynamical Systems. local page: Richard Southwell.