In the access diagram, you can establish the relationships between the object types of the organization view and data view and the application system types, module types, and IT function types specified in the application system type diagram (see chapter Access diagram). In this model type, you cannot directly represent the allocation of functions of the requirements definition. This allocation is realized in the application system type diagram. Similarly, possible chronological-logical operational sequences of application system types, module types, and IT function types cannot be illustrated directly. Strictly following the ARIS architecture, you can trace these links only by navigating through a number of model types.

However, in the system design environment, model types (e.g., program flow charts (PF)) have been established that allow an integral view of all aspects of the system design.

For this reason, ARIS provides the Program flow chart model type. It enables you to model all relationships to application system types, module types, and IT function types available in other ARIS model types, regardless of the ARIS breakdown into views. Moreover, you can represent the chronological-logical operational sequence of the object types mentioned. For this purpose, events are provided in this model type. Similar to arranging functions and events in the EPC, you can define module sequences in the program flow chart. In this context, the event is seen as a trigger that activates module types or application system types. Branches can be represented by the rules known from the EPC. Unlike in an EPC, you can also define operational sequences in the program flow chart without the use of events.