What is a model?

The model governs how you document and structure your information. When you document in Ardoq, you have to create a workspace, that uses a model for structuring you information. There is a one-to-one relationship between models and workspaces; every model is associated with one workspace, and vice versa.

You can think of a model as a database schema that defines the hierarchy of pages and valid relationships between the pages inside a workspace. The model allows Ardoq to automatically create visualizations, as well as validate input.

If you use the “Application Service” model it looks like this:

A basic hierarchy showing how applications are the top level “parent” and services are their “child” component. Using the example in the image above, let’s look at what we know:

Application:

  • Can have multiple Services Services:
  • Services can link to other services (as represented by the arrow)

Other links are always possible, but if they break the model they are determined to be “implicit” type links. This allows you to link across models, and capture non-traditional links that may exist despite predefined rules and designs.

For each type, you also specify if the component type can return a value or what component types it can link to.

See the Model Editor for more information on how you can edit models.

Available models

The following models are available out-of-the-box:

  • .Net
  • Application Service
  • ArchiMate Application Layer
  • ArchiMate Business Layer
  • ArchiMate Implementation & Migration Layer
  • ArchiMate Motivation Layer
  • ArchiMate Physical Layer
  • ArchiMate Strategy Layer
  • ArchiMate Technology Layer
  • Blank Workspace
  • Business Process
  • Chapter Model
  • Corporate Vision
  • Data Flow
  • Enterprise Integration Model
  • Infrastructure
  • JavaDoc
  • Master Data
  • Microservice
  • Process Flow
  • Requirements
  • Role Based Process
Did this answer your question?