The relationships defined in the access diagram (physical) between objects of the organization view and the function view answer the following questions:

In order to illustrate these dependencies, the is platform of and can be platform of relationships can be modeled between the application system objects of the implementation level (application system, module, program module, etc.) or the design specification level (application system type, module type, etc.) and the Hardware component object type of the organization view.

An example is shown in the following figure.

While the design specification level is the level for defining the users that access certain application system types, the implementation level allows for defining this relationship for specific application systems (individual licenses). For example, it is possible that in one company multiple licenses of the ARIS Architect application system type are available with different configurations. An access diagram (physical) can show which user is using which license. For this purpose, the Organizational unit, Position, and Person object types may be linked with the Application system and Module object types via the uses connection. The following figure illustrates an example.

The design specification can use the Application system type - Location relationship to define which application system types may be situated at specific locations in the company. For the purpose of specifying exactly where in the company individual licenses assigned to an application system type are used, the access diagram (physical) may serve to link locations with the Application system, Module, and IT function object types.

An example is shown in the following figure.

The ARIS Method – Tables manual (ARIS Method tables.pdf) on your installation media lists all relationships available in the access diagram (phys.).