Knowledge Architecture Tool Implementation Guidelines

  • Decoupling:Supporting multiple notations and projecting from one to the other, requires solid semantics, infrastructure, and notation or representation decoupling
  • Qualified Relations:Atomized semantics and constraints are related into conceptual modeling components, which are further related to notational modeling components (e.g. glyphs). These binding relations are defined and managed through qualified relation resources
  • Atomization:To support the varying complexities and structures of notational modeling components, especially in supporting from multiple modeling dialects, languages, or notations, conceptual component semantics must be modularized and atomized.
  • Conceptual Modeling Components:Parametrized conceptual modeling components are defined as atomized semantics associations.
  • Notational Modeling Components:Notational modeling components are assigned to conceptual modeling components
  • Modeling Resources:In fact, modeling components semantics are typically meta-data resources, dynamically associated to conceptual modeling component resources, through qualified relation resources, and conceptual modeling components are further qualified and related into notational component resources.
  • Generalization:This is most important as it is the key to modeling generalization as well as to enabling model projection and execution
  • Run-time Metadata:Meta-data and the associated qualified relations, defining classification, structure, bindings, capability, and semantics, are dynamic "run-tme" resources, naturally supported by the underlying REMMS Knowledge Architecture Paradigm (KAP)
  • Aggregated Conceptual Models:Conceptual model elements or sections, typically inferred by notational modeling component input, aggregate conceptual modeling component (e.g. semantics) resources. Conceptual model sections are further recursively aggregated into "higher-level" models by more qualified relation resources. Models, which are really always conceptual, are graphs of conceptual modeling components.
  • Model Projections:Virtual models can be projected to virtual views, by specifying viewpoints and perspectives that respectively define what parts of the model should be viewed, as well as how they should be viewed (e.g. considered).
  • Notational Views:Projection modes are specified to select effective notation dialects and constraints, used to map virtual views to effective notational views
  • Circular Modeling:The modeling process is circular as generated output from the modeling process, notational views can also be used as inputs to the modeling process, to further infer conceptual or virtual models and model sections.
  • Model Execution:Modeling semantics are also required to support model and model component execution. Execution actions include resource instantiation, context rules, dynamic key indicators, process orchestration, notification, work-flow control patterns.
  • Integration:Supporting the integratedintegrating paradigmoperations, the semantics layer is built on the REMMS Knowledge Architecture Paradigm (KAP), as well as powered by the REMMS Knowledge Processing Architecture Paradigm (PAP)framework, to provide the required modeling semantics management and consistency.