Difference between revisions of "Logic Model"
| Line 1: | Line 1: | ||
=Context= | |||
A Logic Model is capturing the '''[[logic]]''' or [[causal relation]]s in a project of interest. All projects in [[PKC]] will be modeled using [[Logic model]], and will be universally managed in a consistent [[namespace]] with a [[common global clock]] in the form of [[entropy pool]]. On the highest level, a [[Logic model]] has seven top level keys, they are [[Context]], [[Goal]], [[Success criteria]], [[Input]], [[Process]], [[Output]], and a set of [[Boundary conditions]]. | A Logic Model is capturing the '''[[logic]]''' or [[causal relation]]s in a project of interest. All projects in [[PKC]] will be modeled using [[Logic model]], and will be universally managed in a consistent [[namespace]] with a [[common global clock]] in the form of [[entropy pool]]. On the highest level, a [[Logic model]] has seven top level keys, they are [[Context]], [[Goal]], [[Success criteria]], [[Input]], [[Process]], [[Output]], and a set of [[Boundary conditions]]. | ||
=Goal= | |||
The goal of using a logic model to represent projects is to offer a [[universal construct|unifying construct]]<ref>{{:Thesis/All Concepts are Kan extensions}}</ref> that captures the common properties in project management. This will help reuse and apply experience and insights into project management across the widest range of applications possible. | The goal of using a logic model to represent projects is to offer a [[universal construct|unifying construct]]<ref>{{:Thesis/All Concepts are Kan extensions}}</ref> that captures the common properties in project management. This will help reuse and apply experience and insights into project management across the widest range of applications possible. | ||
=Success criteria= | |||
A good [[Logic model]] has a common set of [[success criteria]]. The three common properties in projects are: | A good [[Logic model]] has a common set of [[success criteria]]. The three common properties in projects are: | ||
# [[Soundness]]: A sound project should be able to demonstrate/prove its internal logical consistency. | # [[Soundness]]: A sound project should be able to demonstrate/prove its internal logical consistency. | ||
| Line 8: | Line 11: | ||
# [[Terminability|Terminable]]: A project should be able to reach a concluding state. | # [[Terminability|Terminable]]: A project should be able to reach a concluding state. | ||
=Outputs= | |||
This is an instrument for one to quickly organize thoughts and create a Design Contract with the rest of the world. It can be considered as being the [[Monad]] of functional programming and in mathematical logic/[[Category Theory]]. [[Logic Model]] can be thought of a data structure that captures the different facets of a [[morphism]], which is a kind of [[universal component]] in [[algebra]], [[functional programming]], and in [[topology]]. A [[Logic Model]] is the [[Monad|Monadic]] design pattern for all of the above applications. It provides the idealized data structure to approximate and standardize all the abstract structures mentioned before. | This is an instrument for one to quickly organize thoughts and create a Design Contract with the rest of the world. It can be considered as being the [[Monad]] of functional programming and in mathematical logic/[[Category Theory]]. [[Logic Model]] can be thought of a data structure that captures the different facets of a [[morphism]], which is a kind of [[universal component]] in [[algebra]], [[functional programming]], and in [[topology]]. A [[Logic Model]] is the [[Monad|Monadic]] design pattern for all of the above applications. It provides the idealized data structure to approximate and standardize all the abstract structures mentioned before. | ||
=Inputs= | |||
The syntax for filling up the Template is as two parts. The top part, surrounded by a blue dashline, is the abstract specification of a function. Describing what it is. The bottom part, surrounded by a red dashline, is the concrete implementation, revealing the resources and strategies to realize the cause-effect linkage between the '''abstraction specification''' with the '''concrete implementation''' and execution. The two parts, top and bottom of a Logic Model is shown below: (The blue part represents the abstraction specification, or the signature of a function. The red part represents the concrete implementation, which can be considered as the body of a function. Then, all techniques for [[functional composition]] can be applied to [[Logic Model]], and henceforth, applied to anything that [[Logic Model]] represents. | The syntax for filling up the Template is as two parts. The top part, surrounded by a blue dashline, is the abstract specification of a function. Describing what it is. The bottom part, surrounded by a red dashline, is the concrete implementation, revealing the resources and strategies to realize the cause-effect linkage between the '''abstraction specification''' with the '''concrete implementation''' and execution. The two parts, top and bottom of a Logic Model is shown below: (The blue part represents the abstraction specification, or the signature of a function. The red part represents the concrete implementation, which can be considered as the body of a function. Then, all techniques for [[functional composition]] can be applied to [[Logic Model]], and henceforth, applied to anything that [[Logic Model]] represents. | ||
Revision as of 05:42, 4 September 2021
Context
A Logic Model is capturing the logic or causal relations in a project of interest. All projects in PKC will be modeled using Logic model, and will be universally managed in a consistent namespace with a common global clock in the form of entropy pool. On the highest level, a Logic model has seven top level keys, they are Context, Goal, Success criteria, Input, Process, Output, and a set of Boundary conditions.
Goal
The goal of using a logic model to represent projects is to offer a unifying construct[1] that captures the common properties in project management. This will help reuse and apply experience and insights into project management across the widest range of applications possible.
Success criteria
A good Logic model has a common set of success criteria. The three common properties in projects are:
- Soundness: A sound project should be able to demonstrate/prove its internal logical consistency.
- Precision: All activities and resources in a project are accounted for in precise measures.
- Terminable: A project should be able to reach a concluding state.
Outputs
This is an instrument for one to quickly organize thoughts and create a Design Contract with the rest of the world. It can be considered as being the Monad of functional programming and in mathematical logic/Category Theory. Logic Model can be thought of a data structure that captures the different facets of a morphism, which is a kind of universal component in algebra, functional programming, and in topology. A Logic Model is the Monadic design pattern for all of the above applications. It provides the idealized data structure to approximate and standardize all the abstract structures mentioned before.
Inputs
The syntax for filling up the Template is as two parts. The top part, surrounded by a blue dashline, is the abstract specification of a function. Describing what it is. The bottom part, surrounded by a red dashline, is the concrete implementation, revealing the resources and strategies to realize the cause-effect linkage between the abstraction specification with the concrete implementation and execution. The two parts, top and bottom of a Logic Model is shown below: (The blue part represents the abstraction specification, or the signature of a function. The red part represents the concrete implementation, which can be considered as the body of a function. Then, all techniques for functional composition can be applied to Logic Model, and henceforth, applied to anything that Logic Model represents.
{{
Logic Model
|context=A statement describing the spatial and temporal context of the event or project at hand. (The namespace)
|goal= An imperative statement that describes what is to be accomplished. (The symmetry-breaking statement to give orientation in the namespace defined above.)
|criteria= A conditional statement that can be judged based on the outputs of the expected execution process. (A set of logical connectives to qualify outputs shown below to the namespace shown above)
|outputs= A list of items that were to be created through the process.
|process= An organized set of actions or sub-processes that takes inputs and transforms them into outputs.
|inputs= A set of resources that were to be employed in the above mentioned process.
|boundaries=A set of situations which could affect the validity of the overall project, or event.
}}
A Rendered Logic Model in a PKC page
| Logic Model (Meta Logic Model) Template:LogicModel 09 4, 2021 | ||||||
|---|---|---|---|---|---|---|
| ||||||
| ||||||
|
References
- ↑ Lehner, Marina (2014). "All Concepts are Kan Extensions":Kan Extensions as the Most Universal of the Universal Constructions (PDF) (Bachelor). local page: Harvard College. Retrieved June 28, 2021.