Status

Owner
StakeholdersThe business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Introduction

Purpose

The purpose of this document is to outline the application architecture of Signavio.

Scope & Objectives

This document will describe the high-level architecture of Signavio application.

Out of Scope:

  • Since Signavio is a SaaS aaplication, network and infrastructure architecture will be considered as out of Scope.
  • Product documentation and information can be found online will not be documented here. 

Key Decisions and Requirement

DescriptionRationale
Configure SSO for Signavio.As part of SyWay project, a common authentication mechanism (e.g., SAML) will be adopted for ease of access and unified user experience.
Users must access Signavio using HTTPS.

Based on SyWay implementation approach, all data in transit must be encrypted. 

Application Architecture

Overview

Signavio is deployed in Syensqo to model, analyze, and optimize business processes. It assists in detailing processes using BPMN 2.0 and identifying areas for process improvement. Process Manager and Process Collaboration Hub modules are activated in Syensqo's Signavio tenant.

Signavio is integrated with Lean IX to to replicate application and business process as shown below. Signavio is configured to perform SAML SSO with Syensqo's Entra ID.

 

Business process replication from Signavio to LeanIX is planned to be activated after SyWay design phase is completed.

Hosting Details

RegionRegion IDData Center IDInfrastructure Provider

Germany: Frankfurt

XAFEU10AWS

Network Architecture

Signavio is a SaaS application and can be access over the internet. 

System Landscape

Since Signavio is a tool to model business process, 1 productive instance has been deployed in Syensqo.

Application Security

User access


Authentication

Provide the details of authentication architecture used for the application

Communication Security

Provide the details of the communication security controls implemented based on the classification

Data Security

Provide the details of the data security controls implemented based on the classification

Other Controls

Provide the details of any other controls implemented based on the classification


Operation Architecture

Change and Configuration Management

This section will include the details related to change and configuration management of SAP and non-SAP systems.

Monitoring

This section will include the details related to monitoring enabled for the application

Sizing

Provide the details of sizing approach and the future recommendations

High Availability & Disaster Recovery

Provide the details of Disaster Recovery. You may provide a reference to other document or attach a document, if the section contains lot of content

Backup/Restore

Provide the details of Backup/Restore. You may provide a reference to other document or attach a document, if the section contains lot of content

Release & Maintenance Plan

Provide the details of system and application maintenance plan. This should follow the upgrade strategy


Exceptions

This section covers any exceptions to the reference architecture. Some Applications may have limitations and may not meet the Enterprise Architecture, Reference Architecture and IT Policy guidelines. All exceptions should be included in this section.


See also

Provide links or references to relevant documents for further context on this architecture decision and its impact. Listing related architectural decisions here can clarify dependencies.


Change log

Workflow history