Logic Model
A Logic Model is the model of logic, where logic simply means a piece of data that presents a causal relation, or a symmetry breaking information piece. On a higher level, it can be written as a one page diagram that summarizes the Context, Goal, Desirable Effects, Input/Output, and specifications of Boundary Conditions of a given project or task.
It is also a kind of structural description of the nature of data, functions, or logic in a fundamental form. All data, logic, functions, should be describable in a Logic Model, so that when some data item, even as simple as a number, say 42, had been captured in the form of Logic Model, the past experience can be reused for future references.
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.
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
And it should be rendered in a page as what follows:
TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel
| 1. Context |
A statement describing the spatial and temporal context of the event or project at hand. | ||
| 2. Goal |
An imperative statement that describes what is to be accomplished. | ||
| 3. Success Criteria |
A conditional statement that can be judged based on the outputs of the expected execution process. | ||
| 4. Outputs | 5. Process | 6. Inputs | |
|
A list of items that were to be created through the process. |
An organized set of actions or sub-processes that takes inputs and transforms them into outputs. |
A set of resources that were to be employed in the above mentioned process. | |
| 7. Boundary Conditions |
A set of situations which could affect the validity of the overall project, or event. | ||