Zachman Ontology: Difference between revisions
| (19 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=What is an Ontology= | |||
Study of existence of things, and how we categorize them. | |||
From [[John Zachman]] - "an ontology – a theory of the existence of a structured set of essential components of an object for which explicit expressions is necessary and perhaps even mandatory for creating, operating, and changing the object (the object being an Enterprise, a department, a value chain, a "sliver," a solution, a project, an airplane, a building, a product, a profession of whatever)" | |||
==More== | |||
*Epistemology - Study of knowledge. How do we know? | |||
*Ontology - Who are we? (for example: Is it The Man, or Do we have agency?) | |||
*Axiology - What is good? (values) (for example: Do we study things just to understand them, or to change the world for the better?) | |||
https://www.youtube.com/watch?v=AhdZOsBps5o | |||
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/AhdZOsBps5o" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html> | |||
=Source= | =Source= | ||
https://zachman.com/resources/zblog/item/enterprise-architecture-defined-architecture-abstractions | *{{check}}Good presentation: [http://knut.hinkelmann.ch/lectures/ABIT2017-18/ABIT%2005-2%20Zachman%20Framework.pdf] | ||
*https://zachman.com/resources/zblog/item/enterprise-architecture-defined-architecture-abstractions | |||
*Historical Evolution: https://www.zachman.com/ea-articles-reference/54-the-zachman-framework-evolution | |||
*Zachman Foundation: https://www.zachman.org | |||
=Critique and Solution= | |||
*Critique - [https://en.wikipedia.org/wiki/Zachman_Framework#Criticism] | |||
*Critique that too much unnecessary information is captured. This represents OSE's case, where [[Development Spreadsheet]]s are in practice almost never completed - or are completed only by declaring that certain items do not need to be filled. | |||
*Solution - Just Enough Enterprise Architecture - [https://erwin.com/blog/5-best-practices-to-achieve-peak-enterprise-architecture-agility/] | |||
=More= | =More= | ||
| Line 20: | Line 38: | ||
https://www.researchgate.net/figure/The-Zachman-Framework-for-Enterprise-Architecture_fig1_221508381 | https://www.researchgate.net/figure/The-Zachman-Framework-for-Enterprise-Architecture_fig1_221508381 | ||
[[File:zachman.jpg]] | [[File:zachman.jpg|800px]] | ||
[[File:zachman.png]] | [[File:zachman.png]] | ||
=Working Doc= | |||
<html><iframe src="https://docs.google.com/presentation/d/e/2PACX-1vTaDacYCeEQKqj4Dn4P9j9ldgqAFPhyyKwHtA6TQNU05l3BlSCNRvDyK7wbA38xEbDaNGE4xIEcNb2D/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="389" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html> | |||
[https://docs.google.com/presentation/d/1f8DLoXa36TC3EASVWeTNLcqRPkA3Pf86NxkzKuXJSmg/edit#slide=id.g5c3be0ce2d_1_28 edit] | |||
=Links= | =Links= | ||
*[[UML Diagram]] | *[[UML Diagram]] | ||
Latest revision as of 01:47, 28 July 2025
What is an Ontology
Study of existence of things, and how we categorize them.
From John Zachman - "an ontology – a theory of the existence of a structured set of essential components of an object for which explicit expressions is necessary and perhaps even mandatory for creating, operating, and changing the object (the object being an Enterprise, a department, a value chain, a "sliver," a solution, a project, an airplane, a building, a product, a profession of whatever)"
More
- Epistemology - Study of knowledge. How do we know?
- Ontology - Who are we? (for example: Is it The Man, or Do we have agency?)
- Axiology - What is good? (values) (for example: Do we study things just to understand them, or to change the world for the better?)
https://www.youtube.com/watch?v=AhdZOsBps5o
Source
Good presentation: [1]- https://zachman.com/resources/zblog/item/enterprise-architecture-defined-architecture-abstractions
- Historical Evolution: https://www.zachman.com/ea-articles-reference/54-the-zachman-framework-evolution
- Zachman Foundation: https://www.zachman.org
Critique and Solution
- Critique - [2]
- Critique that too much unnecessary information is captured. This represents OSE's case, where Development Spreadsheets are in practice almost never completed - or are completed only by declaring that certain items do not need to be filled.
- Solution - Just Enough Enterprise Architecture - [3]
More
http://en.wikipedia.org/wiki/Zachman_Framework
For OSE, the relevance is the different perspectives for project reification. When developing a project, different people participate: designers, architects, entrepreneurs, managers, etc. Each view should be tailored for them.
OSE is expanding the Zachman Framework to include views that are particularly interesting to OSE development. OSE is separating the content from view of the content by using a database and writing computer scripts to display the database - for whatever audience is necessary.
For OSE, one particular view is the Organizational Learning View - where we teach our contributors various skills.
Design Diagrams
https://www.researchgate.net/figure/The-Zachman-Framework-for-Enterprise-Architecture_fig1_221508381
Working Doc