ARIS provides the following views of an information system:

Each of these views is subdivided into the Requirements definition, Design specification, and Implementation descriptive levels. These are based on the lifecycle of an information system and their proximity to information technology.

The design specification and implementation levels essentially describe the software system. The concepts and terms of these levels are closely interrelated and their 'translation' is unproblematic.

This is not the case with the transition between the requirements definition and the design specification. When creating the design specification, the business management view must be aligned with the standard software. This requires both business management expertise and data processing knowledge (see Scheer, A.-W., ARIS - Business Process Frameworks, 1998, 3rd edition, p. 7).

The information system view (IS view) in IT City Planning can assist as a mediator between levels. In ARIS, the object types of the IS view are located at a level between functions and application systems, thus extending the function view in ARIS. Like functions, IS elements are associated with the various constructs from the familiar views of the ARIS House. These extensions mainly relate to process view and data view. In the following, the term IS view refers to the model types from the function and process views of the ARIS House, which describe relationships between IS elements or give a detailed description of IS elements seen in the context of the other ARIS views.

Application system types, IT function types, and sockets are considered as elements of the IT (information technology) view. In analogy to the IS view, the IT view includes all model types in which relationships between application system types, IT function types, and the new Socket object type are described, or which are used to describe one of these elements in detail.