Differences

This shows you the differences between two versions of the page.

--- start [2020/02/08 09:03]
anwlur created
+++ start [2020/07/04 01:33] (current)
anwlur rationalize vision with technical constraints.
@@ Line 1: / Line 1: @@
 ====== MODEL OF KNOWLEDGE ======
 You look upon the multitude of loose notes, notebooks, electronic documents, digital spreadsheets either piling on your desk or scattered among your hard drive and you think, there must be a better way. Model Based Systems Engineering, at its essence, is built on a coherent source of truth from which you can slice and dice all you want but the truth remains. Why not apply the MBSE approach not only to Systems, those man-made things of steel, electrons and bytes, but to Knowledge itself?
-There are many Books of Knowledge out there including the Project Management BOK ([[https://www.pmi.org/pmbok-guide-standards/foundational/pmbok|PMBOK]]), Systems Engineering BOK ([[https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK)|SEBOK]]) and the biggest of them all, [[https://www.wikipedia.org|Wikipedia]], however they have some fundamental deficiencies not because of their content but because architecture:
+There are many excellent Books of Knowledge out there including the Project Management BOK ([[https://www.pmi.org/pmbok-guide-standards/foundational/pmbok|PMBOK]]), Systems Engineering BOK ([[https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK)|SEBOK]]) and the biggest of them all, [[https://www.wikipedia.org|Wikipedia]], however they have some fundamental deficiencies not because of their content but because architecture - an architecture built around documents.
-  - Change management and propagation in a networked document is difficult
+Documents and webpages are views of information from particular viewpoints (for example look up '[[https://en.wikipedia.org/wiki/Trigonometry|trigonometry]]' on wikipedia), maybe asking slightly different questions (and offering the answer) about the the main topic. Deficiencies of a document, connected or otherwise, include:
+  - Change management and propagation is difficult
   - Inevitable inconsistencies between terms and definition (e.g. processes, frameworks, methods)
+  - Static nature of documents means that a reader would need to either 'stitch' together different viewpoints, 'generalize' a document if too specific or 'specialize' a document if too general. Rarely would you find a document that satisfies your use case.
+**Our vision** is to transform how knowledge is delivered, not through a collection of documents but through a Model of Knowledge (MoK) that supports different views so that a master and an apprentice can examine the same class of problems from different perspectives and gain understanding.
+Though I have a model editor native to my PC I have not yet identified how to upload that model on [[https://www.fitzgeraldsystems.com/|Fitzgerald Systems]]. Knowing the deficiencies of BoKs I readily admit that documents are better than nothing at all and with this in mind I take a step back from the above vision to then create and maintain this wiki as a means to organize and consolidate the knowledge that I have gained. With content readily available I will at an undisclosed time, migrate this BoK to the MoK. A thousands miles start with a single step.
+[[toc|Table of Contents]]
-At Fitzgerald Systems applied systems thinking is at the core of what we do. That's why we are using a model approach to develop a repository for knowledge that is augmented by the different BOK out there and, where these external resources fall short, by this wiki you are now reading. That repository is 'captured' in periodically automatic generated HTMLs which can be viewed [[http://fitzgeraldsystems.com/model/document_analysis.htm|here]].

Model of Knowledge by Fitzgerald Systems

User Tools

Site Tools

Differences

Page Tools