Define query

You can output the interrelationships between database items as graphics and in a table with the help of queries. Queries are defined based on graphics.

The package contains numerous default queries. You can use these as a basis for creating your own queries. To do this, make changes to copies of default queries as the original files are overwritten when updating the program.

Procedure

  1. Click New New > Query Query. The Query Wizard opens.
  2. Select the database for which you want to define the query.
  3. Log in, if required.
  4. The Query 1 tab opens. Make sure that the Ad hoc analysis Query, Result Result, and Spreadsheet Spreadsheet bars are active.
  5. In the Start box, enter the name of the query item for which you want to start the query. For example, this can be a database, a database group, a model or model type, or an object or object type.

    A list of suggestions is generated during input. If you click an entry, it is entered into the Start box. The type of this query item defines the starting point. Users can start the query by entering a name of any item of this type.

    In the Successors tab all of the possible successors for the start item are listed in a bulleted list. You can Right arrow expand and Down arrow collapse the bullets. If you move the mouse pointer to an entry, you see the API name from ARIS Method. This helps you to pick the right item if you have multiple items with the same name.

  6. Click on a successor or bullet in the list.

    The successor is added to the query. If you have clicked on a bullet all of the items subordinate to this bullet are added as a step. You can also select a specific relationship between people and functions, for example, carries out.

  7. Add any number of steps or already existing queries to this query. All items are represented graphically on the Definition tab.

    By default, queries relate to object definitions. Therefore, the Definition level Definition level icon is displayed. If you want to use occurrences instead, select the occurrence level for the relevant items.

  8. Select the corresponding query items and click Occurrence level Occurrence level in the Start tab bar. You can also double-click the icons in query items.

    If your selection meets all the prerequisites, the items are marked with the icon. All object occurrences are taken into account for these items.

    Otherwise, possible items are selected automatically and you have to confirm the change.

  9. For each step you can define conditions so that only items that meet these conditions are found. Using the Hierarchy tab, you can speed up the runtime by increasing the level to be analyzed.
  10. Click Start simulation run Start query on the Query tab bar. The Select starting point dialog opens.
  11. Enter the name of the start item. All items of this type are offered for selection while you type. During query definition, the type for any starting points was specified. It is uniquely identified by its name and the API name from ARIS Method. For example, if a query can be started from an application system type, this box is named Application system type (OT_APPL_SYS_TYPE).

    You receive information about individual items when you move the mouse over a step or select a step and click Properties Properties or Attributes Attributes in the Start tab bar. This way you can also show and edit attributes and adjust the object appearance. You can navigate via the properties to for example, the models in which objects occur.

    All of the items added are represented in bold type in the list. If you click a bold entry the step is deleted from the query.

  12. Select the layout for the result.
  13. Create a table output for presentation purposes. You can evaluate query items in a table and save the results in a model of the Spreadsheet type or export the tables and sheets to Excel.
  14. Define the sort order for the table output to be used.
  15. Save the query.

Users with management privileges can share private queries with other users. Queries can be edited, for example, after new method items were defined and need to be added to queries.