webMethods and Intelligent Business Operations 10.2 | Designing and Implementing Business Process Models | ARIS Method manual | Modeling within the views and levels of the ARIS concept | Process view | Design specification | Access diagram | Linking organization with function
 
Linking organization with function
The fact that the organizational aspects are linked to the functional aspects defined at the design specification level basically answers the following questions:
*Who (which organizational unit, position, person, etc.) is responsible for the application system types and module types specified in the function view at the design specification level, or who uses these systems?
*Which locations (organization view) within the company use which application system types or module types?
*Which platforms available in the company (hardware component types (organization view)) are suitable to run which application system types?
In order to answer the first question, connections can be drawn in the access diagram between the organizational units of the organizational chart (organizational units, positions, and persons) and the objects of the application system type diagram (application system type, module type, IT function, etc.). While doing this, the significance of this relationship can be specified more precisely. We distinguish the following:
*An organizational unit may be responsible for an application system type as far as the technical aspects are concerned.
*An organizational unit may be responsible for the development of an application system type.
*An organizational unit may be a user of an application system type.
The question of location may be solved by assigning locations from the organization view to application system types, module types, and IT function types.
In the design specification we are not dealing with individual application systems in the sense of individual licenses, but with application system types. Therefore, no actual locations of application systems are defined by means of this relationship (this is realized at the implementation level), but possible locations of a particular application system type are pointed out.
The design specification of the organization view defines the hardware component types available in a company. In the control view, the relationship between these hardware component types and the application system types can be established. This is how the hardware platforms for running certain application system types, module types, or IT function types are determined. At this stage, the graphical user interface types, operating system types, and DBMS types included in the function view can be assigned to the hardware component types, as well.
A list of relationships that are available in an access diagram is provided in the ARIS Method – Tables manual (ARIS Method tables.pdf) on your installation media.
The following figure shows examples of relationships.
Access diagram (excerpt)

Copyright © 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release