Difference between revisions of "Data Architecture"

From PKC
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
In [[PKC]], data is consistently represented using one universal construct, [[directed relation]]. This also means that we can always use the same data type, [[directed relation]] to interpret and manipulate data.
In [[PKC]], data is consistently represented using one universal construct, [[directed relation]]. This also means that we can always use the same data type, [[directed relation]] to interpret and manipulate data.
=Architecture = Invariant Properties =
It is important to note that the word '''[[Architecture]]''' implies elements of a system that doesn't change. Therefore, this section will talk about the data elements of [[PKC]] that don't change over space and time.


{{LogicModel
{{LogicModel
|name=DataArchitecture
|name=Data Architecture
}}
}}
=References=
<references/>
=Related Pages=
[[Category:Information Architecture]]

Latest revision as of 16:33, 23 February 2022

In PKC, data is consistently represented using one universal construct, directed relation. This also means that we can always use the same data type, directed relation to interpret and manipulate data.

Architecture = Invariant Properties

It is important to note that the word Architecture implies elements of a system that doesn't change. Therefore, this section will talk about the data elements of PKC that don't change over space and time.


Logic Model (Data Architecture) Template:LogicModel 02 23, 2022
Abstract Specification
Context Data Architecture/Context
Goal Data Architecture/Goal
Success Criteria Data Architecture/Criteria
Concrete Implementation
Given Inputs When Process is executed... Then, we get Outputs
Data Architecture/Input Data Architecture/Process Data Architecture/Output
Boundary/Safety Conditions of Data Architecture
Data Architecture/Boundary

References

Related Pages