Documentation of the planning, process steps, and results of software development and implementation.

ARIS support: The main project phases can be described as a procedure model by a value-added chain diagram.

Individual project activities during development and implementation and their operational sequence can be documented by means of EPCs.

The organizational assignment of people and units involved in the project can be represented in organizational charts.

The task is to show the structure of an information system based on system requirements.

ARIS support: The use cases of the software system to be developed can be identified by means of the use case diagram. Furthermore, the system users can be defined and then assigned to individual use cases. Often, the use case diagram is the starting point for detailed process modeling. Process models can be assigned to individual use cases.

The application system type diagram may serve to describe the hierarchical structure of application systems at type level using module types and IT function types.

Concrete occurrences describing specific types in more detail can be represented in the application system diagram.

The task is to describe the chronological-logical operational sequence of processes within and across modules.

ARIS support: IT processes can be modeled in program flow charts.

The task is to develop and document a user interface.

ARIS support: The structural and functional organization of a screen (window) can be described with a screen diagram. Similar to the transition from an ERM to a relations diagram, the screen diagram is the basis for deriving the program code.