Knowledge Architecture Tool Functional Guidelines

  • Models:Knowledge Architecture tools enable knowledge architecture operations by first supporting the input, definition, and integration of knowledge models. Although these models can be input or defined by using various notations, the models themselves are virtual or conceptual. Only through projection, they can be mapped to views and representations. Models can also be executed, instantiating and orchestrating their components into knowledge applications
  • Views:Views are model representations through viewpoints, perspectives, and notations
  • Projection:The model projection process is used to project virtual models to views, using selected viewpoints, perspectives, and projection modes that include notation selection
  • Viewpoint:Viewpoints are modeled resources that specify stakeholder (e.g. viewer) position, angle of view, and center of interest. Viewpoints determine what aspects and parts of the model are to be viewed (e.g. considered, projected)
  • Perspective:Stakeholders define perspectives (e.g. perspective modeling resources) to define how the viewpoint selected model aspects and resources should be viewed. Perspectives define perspective mode or templates, focus, granularity, and resolution adjustments, as well as the field of view depth, width, and height (e.g. specifying various summary and detail levels)
  • Notation:The projection mode is typically used to define the notation (e.g. UML, BPMN, facts/assertions) to use, as well as, when applicable, the notation mode, including things like 2D or 3D for graphics, or a specific natural language for text based views (e.g. English, French)
  • Execution:While some models are mostly conceptual, many others are designed to manage knowledge resources. Consequently, defined model components need to be instantiated into managed resources. More so, many of those modeled resources are dynamic executable resources and systems, with context rules and key indicators, for example. Governance of the resulting systems and resources is enforced by managing, controlling, and orchestrating the executing processes through control parameters, dynamic indicators, and context rules, for example. Governed by their underlying semantics, executable models serve many purpose and take many forms, requiring appropriate support, including for resource capability and behavior, work-flow patterns, scheduling, notification, messaging, and others
  • Reverse Modeling:Because knowledge architecture and application are better managed by effective modeling, the dynamic modeling of existing components (e.g. reverse modeling) constitutes another fundamental knowledge architecture and management tool operation
  • Circular Modeling:Modeling is often an iterative process where views from one model can typically serve to define or extend other models. This can be accomplished when output notations are also recognized as input notations. This provides flexible model import and export functionality. The primary keys to achieving circular modeling, are related to the strong semantics of the virtual models, and the extended support for structured input and output notations.
  • Sharing:Sharing knowledge and models is also a fundamental knowledge architecture tool operation, requiring entitlement and access control and tracking