• Extensible libraries of modeling components, including current modeling language components (e.g. UML, BPMN, SOAML, SysML, BPMM, etc.)
  • Models can be build by sections (e.g. use case diagram, class diagram, sequence diagram, etc.)
  • Imposes no prescribed diagram constraints (e.g. classes and objects can be combined with use cases and actors, etc.)
  • Models are integrated and whole
  • Projection (e.g. viewpoint and perspective) specifications determine the views
  • Viewpoints position the stakeholder and the center of interest or viewing angles (e.g. what part or cross-section of the model is considered)
  • Perspectives select how the viewed cross section is projected and viewed (e.g. depth, notation, projection mode, templates)
  • View notation can be 2D graphical like is common today, or 3D, or text, for example in logic-based facts/assertion form (e.g. validation, proofing)
  • Export formats (e.g. XMI, RDF, XML) are also projection notations selected with the perspective and projection mode


  • Knowledge architecture paradigm
  • Based on knowledge resources
  • Unlimited granularity
  • Executable models
  • Context rule engine and support
  • Reverse (e.g. automated) modeling support


  • Complete separation of concerns support
  • Support for multiple integrated model notation systems/interfaces
  • Support for multiple projected view notation systems/interfaces
  • Innovative, structured, and decoupled MVC architecture
  • The View layer supports defining and managing modeling components, models, viewpoints, perspectives, views, invoking the projection engine, and model execution, reverse modeling
  • The Controler layer is based on high performance and scalability parallel transformation pipelines for streaming content and resources, providing the required “back-end” functionality, including transformation, projection, execution, and reverse modeling
  • The Model layer integrates and abstracts repositories, data access, virtual resources and profiles, as well as interface with multiple distributed repositories and storage systems, with access security control

As is typical throughout the document/site, the logic flow follows the order of the titles in the menus and we recommend, at least initially, following them in sequence. As usual, feedback is appreciated.