Applications

Modeling applications in Docusnap365 on an abstract level – independent of specific installations or technical components. The focus is on structured capture and linkage within the business architecture.

  2 minute read  

Objective

In Docusnap365, applications can be defined as independent objects on an abstract level – regardless of whether they are locally installed software, cloud-based solutions, or hybrid systems.

The goal is to represent core applications such as Salesforce, SAP, or Microsoft Dynamics NAV functionally and link them to relevant business, organizational, and technical contexts – without modeling the complexity of individual installations.

This chapter explains how applications are captured and used as part of the enterprise architecture in Docusnap365.

Scope of Functionality

The current functionality for modeling applications includes:

  • Creating applications

    • Manually via the user interface or automated via the REST API

  • Linking to other objects, such as:

    • Business services supported by the application
    • Processes in which the application is used
    • Departments that work with the application
    • People related to the application

  • Dependency diagram

    • Visualization of the modeled relationships between an application and other objects
    • Supports understanding of the functional integration in the overall model – without detailing technical infrastructure like installation locations, databases, or components

Example Use Cases

  • Which business services are supported by an application?

    • Visible through the modeled relationship

  • In which processes is the application involved?

    • Traceable via the process linkage

  • Which department uses a particular application?

    • Derivable through the organizational assignment

  • Which people are linked to an application?

    • Can be shown, e.g., for usage context or analysis