Modeling tools used for systems ([[SysML]]), functions ([[IDEF0]]), processes ([[IDEF3]], [[BPMN]]), and [[Enterprise Architecture]]s ([[UAF]], [[Archimate]]) _could_ be used as a framework for a company’s knowledge base/[[Semantic Wikis]]. This approach offers a number of advantages to exploit and, similarly, drawbacks to mitigate. There is a [[Gap Between Modeling and Writing]] that feels like a market opportunity. > [!warning] Regarding [[OWL]]: > This note isn't really considering the [[OWL|Web Ontology Language]], which _is_ actually a modeling language for representing knowledge. [[OWL]] might get folded in properly later if I feel like it. # Advantages - scalability due to - [[Referential Integrity]] - Enforced constraints - Model validation mechanisms - in-built [[Ontology, Semantics, and Syntax|Semantics]] - [[modularity]] - the same model may be used to produce numerous types of outputs (e.g. .docx, .html) based on numerous types of views of the same underlying model - special tool-specific features may be used - simulation - code generation # Disadvantages - modeling tools aren’t designed to be knowledge bases, you’re working against your tools - modeling languages’ [[Ontology, Semantics, and Syntax|syntax]] aren’t user friendly - modeling tools are not good for presentation, and require either mass installation or the utilization of reporting ## Mitigations - **Reporting** - essentially every modeling tool has reporting mechanisms. Good ones have _good_ reporting mechanisms. These are, however, still less easy than simply **** ## Source - self ## Related