Using the various modeling methods in ARIS Architect information can be viewed from different perspectives and made available to various target groups with a special focus. The e-business scenario is the starting point of these views. Details for specific target groups can be specified in its objects. In this way, an e-business project can be represented in its entirety. In addition, the various components of ARIS can be used to perform evaluations for the models created to ensure optimal support of projects in the e-business environment.

The first step is defining the objectives that are to be achieved by the planned e-business activities. This step can be performed with the help of the ARIS component Balanced Scorecard (see the chapter Balanced Scorecard method). This makes it possible to identify the processes that have to be optimized to achieve the objectives. In our example, the objective is identified as the development of a new distribution channel, namely the Internet. In order to pursue this new path optimally, precise documentation and planning are indispensable.

Not only must the process flow itself be taken into account, but also the organization of responsibilities, interfaces between various systems, and data security.

Starting point is the e-business scenario diagram. The business participants in our example are the company that implements the shop system and the customer who will use this offer. The entire process from 'entering the shop' to 'leaving' is broken down into subprocesses. The representation shows the view of the customer and that of the company. The e-business scenario diagram serves as an entry point to the implementation project. The following figure shows how the overall process is divided up.

The various process steps can now be refined by EPCs: for example, they can be verified with the Simulation component, displayed after optimization by means of pipeline diagrams, and converted into a finished shop system through Intershop Enfinity to be further improved.

If a shop is to be connected to an external ERP system (Enterprise Resource Planning system), the data to be transferred needs to be in the correct format. For this purpose, there are various ways of standardizing documents and data. One such standardization option is offered by the use of Extensible Markup Language (XML). When documents are created, DTDs can be assigned to help define their structure and required contents. Since XML is a language that is being developed along completely different paths, a uniform foundation is needed here. Different organizations, consisting of companies and scientific institutions, are involved in standardizing XML for various sectors.

The use of standardized XML documents facilitates the integration of ERP systems.

The problems arising from the need to harmonize various components have already been mentioned. The application system type diagram can serve to visualize the systems and can be assigned as a model to application systems or business components to explain the systems' interrelationships in more detail.

The new e-business activities will also affect the organizational structure. It may be necessary to define new responsibilities or make new allocations. The e-business scenario diagram can describe roles and organizational units for individual process steps. What position they take in the company's organization or in the process can be analyzed further by means of organizational charts.

Implementation begins with the realization of modeled content. If the Intershop method is used, the content modeled is converted into an operational system by means of Intershop Enfinity.