Data requirements for "What are our architectural dependencies?"

Application

Name

Necessary for the visualization.

Version

Necessary for the visualization.

Object State

Required for business question

Describes the use of the application in the real word. This can be understood as the operational status of the application. Possible values are:

Start Date

The start date is the date when the application is actively used.

End Date

The end date is the date when the application is no longer actively used.

Status

Specifies the approval status of an application and determines whether or not the application can be edited or deleted. Possible values are:

• Draft: The application has only mandatory data defined.
• Under Review: The application is documented and being reviewed. An application with this release status cannot be deleted.
• Approved: The application has been approved by the responsible stakeholders. An application cannot be deleted when it has an approved release status. An application with this release status cannot be deleted.
• Data imported: The data regarding this application has been imported from an external system. Additional changes may be required to improve the data quality. An application with this release status can be deleted.
• Trash: The application is no longer valid and can be deleted.

Architecture Type

Required for business question

The architecture type of the application: Possible values are:

• Client-Server: The application divides tasks or workloads between the providers and consumers of a resource or service.
• Cloud-Based: The application runs on SaaS cloud environments. The cloud infrastructure could be local or remote to the organization.
• Distributed: The application runs on multiple computers within a network. The network boundary can extend from private intranets to public clouds.
• External Webpage: The application is an external resource represented through a web link.
• Mainframe: The application is used by large organizations to carry out critical processing tasks such as bulk processing of data, transactions, planning or statistical activities.
• Stand-Alone: The application is a self-contained application that does not rely on external entities to complete a task.
• Unknown: The architecture type has not yet been assessed.

Development Type

Required for business question

The application development type.

• Bespoke: The application was created specifically to address a unique use case.
• COTS - Configured: A commercial off-the-shelf application that has been configured or supports configuration to fulfill the requirements of the enterprise and is fully supported and upgrade-stable.
• COTS - Customized: A commercial off-the-shelf application that is customized or contains organization-specific code/programming to suit the requirements of the enterprise.
• Unknown: The application development type has not yet been assessed.

Authentication

Required for business question

The authentication method used for the application.

• Autonomous: The application supports autonomous methods such as Direct Autonomous Authentication (DAA) for authentication. This can be carried out through mobile or remote authentication systems.
• Basic Access: The applications support basic authentication based on a username and password. Protocols and layers such as HTTPS, SSL. or TLS could be used to enhance security, but these are not mandatory.
• Multi-Factor: The application requires more than one method of authentication from independent verification sources to verify the transactional identity.
• Multi-Factor & SSO: The application supports both multi-factor authentication (MFA) and single sign-on (SSO) authentication methods.
• No Authentication: The application does not support authentication.
• Single Sign-On: The application supports the use of a single ID and password to gain access to several related or unrelated systems.
• Unknown: The authentication mode has not yet been assessed.

Recommendation

Required for business question

The strategic recommendation regarding future investment for the application. Possible values are:

• Tolerate: Invest in the application.
• Invest: Consider the application as a migration candidate.
• Migrate: Sundown the application.
• Eliminate: Discontinue the application.

Information Flow

Name

The name is a concatenation of <Source Application> >> <Target Application>.

Connection Method

Required for business question

A connection method describes the mode of transfer used by a specific information flow to transfer business data between the two associated applications or their respective components. Preconfigured connection methods include: Middleware, P2P, Other

Connection Frequency

Required for business question

A connection frequency describes how often a specific information flow is used to transfer business data between the two associated applications or their respective components. Preconfigured connection frequencies include: Hourly, Daily, Weekly, Monthly, Quarterly, Yearly, Real Time, On Demand, Other

Connection Data Format

Required for business question

A connection data format describes the data format used for the transfer of business data via a specific information flow.

Preconfigured connection data formats include: ASCII, Binary, CSV, IDoc, Other

Connection Data Type

Required for business question

A connection type describes the mode of transfer used by a specific information flow to transfer business data between the two associated applications or their respective components.

Preconfigured connection types include: Asynchronous, Synchronous, Other

Source Application

An information flow requires an application that is the source of the connection.

Target Application

An information flow requires an application that is the target of the data exchange.