Document 130

SEBoK *Ontology Development*, Distilled

framework

SEBoK Ontology Development, Distilled

Fourth-batch SEBoK distillation, batch 2 doc 3. SEBoK has no dedicated Ontology Development page; the topic is treated through the reference-citation page On Ontology, Ontologies, Conceptualizations, Modeling Languages, and (Meta)Models (Guizzardi 2007), the Ontology (glossary) entry, and as feeder material for System Modeling Concepts, Representing Systems with Models, and What is a Model?. The Guizzardi page identifies a four-layer stack (ontology / conceptualization / modeling language / model) plus the metamodel layer above — five rungs of representational abstraction in nested universal-sibling lattice (Cluster A) at the representation-layer rung. The hypostatic boundary (Cluster H) is the load-bearing form: the article distinguishes ontology-as-philosophical-discipline from ontologies-as-engineering-artifacts; SEBoK's discipline keeps the engineering ontologies functional and refuses metaphysical inflation. Doc 372 binds sharply. Capability Engineering's "incremental hybridization of heterogeneous case studies to develop an ontology" is the canonical SE-side worked example. Three clusters compose; structural surprise is that ontology development is treated as cited reference rather than knowledge area.

I. Source

II. Source Read

The source is a citation page for Guizzardi, G. 2007, "On Ontology, Ontologies, Conceptualizations, Modeling Languages, and (Meta)Models," Proceedings of the 2007 conference on Databases and Information Systems IV. SEBoK uses this reference to ground three downstream topics: Representing Systems with Models, What is a Model?, and System Modeling Concepts. Subject matter is "a treatment of the topic of modeling languages and metamodeling concepts." The Guizzardi paper distinguishes (1) ontology as philosophical discipline, (2) ontologies as engineering artifacts capturing domain conceptualizations, (3) conceptualizations as the cognitive content being captured, (4) modeling languages as the formal vehicle for expressing ontologies, (5) (meta)models as descriptions of modeling languages themselves. Adjacent SEBoK use: Capability Engineering article's "incremental hybridisation of heterogeneous case studies to develop an ontology for Capability Engineering"; Boehm's ontology of system quality attributes for tradeoff analysis. The Ontology (glossary) entry defines ontology in the engineering-artifact sense.

III. Structural Read

Cluster A (universal-sibling lattice, Doc 572 Appendix D), at the representation-layer rung. Guizzardi's stack distinguishes five layers: ontology (philosophical) / conceptualization (cognitive) / ontology-as-artifact (engineering) / modeling language (expression vehicle) / metamodel (description of modeling language). Each layer binds every modeling engagement aspect-wise; the discriminator is representational abstraction-level. Five-rung nested lattice. Cluster A gains a representation-stack instance.

Cluster H (hypostatic boundary, Doc 372), load-bearing. The Guizzardi article is structurally about preventing the conflation of philosophical ontology (what is) with engineering ontologies (formal representations of domain conceptualizations). Doc 372's discipline is built into the article's title — the comma-separated list (ontology, ontologies, conceptualizations, modeling languages, (meta)models) is explicitly a hypostatic-boundary enforcement device. SEBoK adopting Guizzardi as primary reference inherits the discipline. Cluster H binds maximally.

Cluster D (co-production, Doc 573). Capability Engineering's "incremental hybridisation of heterogeneous case studies" is co-produced ontology-construction across multiple case-study contributors; no single keeper authors the ontology. Cluster D binds at the ontology-construction rung.

Cluster F (pulverization, Doc 445). Boehm's ontology of system quality attributes for tradeoff analysis is forward-pulverization at the quality-attribute rung — every quality attribute is a pulverization-bin against which tradeoff costs are computed. Cluster F binds.

IV. Tier-Tags

  • Guizzardi 2007 citation — π / α as cited.
  • Ontology / ontologies / conceptualizations / modeling languages / metamodels four-or-five-layer distinction — π / α as cited; μ / β under Doc 572 Appendix D at representation-layer rung.
  • Hypostatic-boundary discipline (philosophical vs. engineering ontology) — π / α as cited; μ / β under Doc 372.
  • Capability Engineering ontology incremental hybridization — π / α as cited; μ / β under Doc 573 co-production.
  • Boehm ontology of quality attributes — π / α as cited; μ / β under Doc 445 pulverization.

V. Residuals

No dedicated Ontology Development page (structural surprise). SEBoK treats ontology development through (i) a citation page for Guizzardi 2007, (ii) a glossary entry, and (iii) feeder use in three system-modeling-concept articles. The corpus notes this as an editorial gap and accepts the citation-and-feeder pattern as SEBoK's de-facto knowledge-area structure for the topic.

Hypostatic boundary is exceptionally clean here. The Guizzardi reference is structurally a hypostatic-boundary enforcement device. The corpus accepts and notes that Doc 372 is one-to-one with the article's framing; this is the cleanest SEBoK adoption of Cluster H discipline observed.

VI. Provisional Refinements

Cluster H canonical worked example. The Guizzardi article supplies the cleanest SEBoK case of a hypostatic-boundary enforcement device. Cluster H synthesis should treat ontology-vs-ontologies-as-artifacts distinction as the canonical worked example. Aligns with SE-039 §VII.6 sixteen formalized refinements at the hypostatic-boundary slot.

Five-rung representation-stack as Cluster A instance at meta-modeling rung. Adds the meta-modeling rung to Cluster A's confirmed populations. Density signal modest (one instance) but the rung is novel.

VII. Cross-Links

Form documents. Doc 372 (hypostatic boundary, canonical worked example), Doc 572 Appendix D (universal-sibling, representation-layer rung), Doc 573 (co-production, ontology-construction rung), Doc 445 (pulverization, quality-attribute ontology).

Part-level reformulation. SE-009 (Part 6 cross-references for Modeling and Simulation, Capability Engineering).

Related distillations. SE-033 (Capability Engineering, ontology incremental hybridization). SE-112/695 (System Security and quality attribute ontology adjacent).

Adjacent SEBoK concepts (per source). System Modeling Concepts, Representing Systems with Models, What is a Model?, Modeling Standards, Model-Based Systems Engineering (MBSE), Capability Engineering, Ontology (glossary).

Methodology refinement candidates. Cluster H synthesis with Guizzardi article as canonical hypostatic-boundary worked example.

Appendix: Originating Prompt

"Apply refinements" / "Continue next knowledge base entrancement"

(SE-130 is the third of the fourth-batch SEBoK distillation sweep, Batch 2/5. Structural surprise: SEBoK has no dedicated Ontology Development page; Guizzardi 2007 citation page is the closest coverage and supplies the cleanest hypostatic-boundary worked example observed.)

Referenced Documents

More in framework