How sharptoolbox/ontology_modeling_framework works
This repository is a documentation-only ontology-driven modeling framework, not an executable application. Its principal workflow is to turn requirements into traceable YAML models that guide design and code generation. The graph captures the documented v6 model dependencies and the v9 synchronous subset; relationships are specification dependencies, not runtime calls. Source excerpts were unavailable, so edges rely on the README, and the individual specifications’ internal details are not inferred.
Main entry points: ontology_modeling_framework_v6.md Behaviors M2 · ontology_modeling_framework_v5.md Expanded v4–v5 · ontology_modeling_framework_v2.md Foundations v1–v2 · ontology_modeling_framework_v9.md Synchronous v9
Components 19
Framework versions
- Full framework v6
ontology_modeling_framework_v6.md - Synchronous v9
ontology_modeling_framework_v9.md - Foundations v1–v2
ontology_modeling_framework_v2.md - Expanded v4–v5
ontology_modeling_framework_v5.md
Core domain models
- Objects M1
ontology_modeling_framework_v6.md - Behaviors M2
ontology_modeling_framework_v6.md - Rules M3
ontology_modeling_framework_v6.md - Actors M5
ontology_modeling_framework_v6.md
Coordination models
- Events ME
ontology_modeling_framework_v6.md - Scenarios M4
ontology_modeling_framework_v6.md - Processes M6
ontology_modeling_framework_v6.md - Queries M7
ontology_modeling_framework_v6.md - UI MU
ontology_modeling_framework_v6.md
Boundary and persistence
- Data mapping MM
ontology_modeling_framework_v6.md - Interfaces MI
ontology_modeling_framework_v6.md
Other components
- System modeler
- Requirements
- System design
- Generated code
Connections 26
- System modeler → Requirements: models
README.md - Requirements → Full framework v6: specifies with
README.md - Full framework v6 → System design: guides
README.md - System design → Generated code: traces to
README.md - Foundations v1–v2 → Expanded v4–v5: evolves into
README.md - Expanded v4–v5 → Full framework v6: extends to
README.md - Full framework v6 → Synchronous v9: trims into
README.md - Behaviors M2 → Objects M1: acts on
README.md - Behaviors M2 → Rules M3: uses rules
README.md - Behaviors M2 → Actors M5: subject to
README.md - Events ME → Behaviors M2: depends on
README.md - Events ME → Rules M3: depends on
README.md - Scenarios M4 → Objects M1: depends on
README.md - Scenarios M4 → Behaviors M2: depends on
README.md - Scenarios M4 → Rules M3: depends on
README.md - Scenarios M4 → Events ME: depends on
README.md - Processes M6 → Scenarios M4: depends on
README.md - Processes M6 → Actors M5: depends on
README.md - Queries M7 → Objects M1: queries
README.md - Queries M7 → Behaviors M2: binds query
README.md - UI MU → Processes M6: maps screens
README.md - Data mapping MM → Objects M1: maps objects
README.md - Data mapping MM → Queries M7: supports SQL
README.md - Interfaces MI → Behaviors M2: binds calls
README.md - Interfaces MI → Events ME: supports events
README.md - Interfaces MI → Actors M5: aligns contracts
README.md