Technology Management Desktop | QualiWare Center of Excellence

Being on the Technology Management Desktop, Architects and Business Users can define and manage logical as well as physical business object and infrastructures. Manage Infrastructure risk and technology lifecycles.

Desktop Journey

With QualiWare’s purpose driven desktops, users are enabled to have centralized workspaces for each area within the QualiWare Enterprise Architecture and GRC platform. Doing so allows users to use preconfigured reports and dashboards as they populate their repositories and start on their respective journeys. The journeys all carry a methodology of Plan, Do, Check, Act which encapsules:

Getting Started for content creation, and import of data
Overview for establishing overview and maintaining relationships
Evaluate for analyzing the content from different perspectives
Planning, communication and review for creating change initiatives, tracking and implementing change

Getting started

Each Desktop has a “Getting Started” tile that provides easy access to the most relevant features in relation to the focus on the desktop.

Establish an overview of current situation

Overview of all the organisations Business Object Models.
Listview of all firewall and their contract and the organisations Computers and their attributes.
Understand the organisations infrastructure Diagrams and related Risk Impact.
Stay on top of the Technology lifecycles and plan accordingly.

Read more about the Desktops

Explore the general introduction to desktops using the links:

API Architecture Metamodel

An Application Programming Interface (API) is a construct that enables communication between systems. Integration between systems in complex environments continues to be a business priority to support automation activities. An API can be purpose-built for a bespoke integration (typical of legacy systems), or alternatively a standard connector can be developed between industry standard systems such as ERP’s and Service Management platforms. Managing these integrations becomes a complex operational task as updates and new releases to the integrated systems (and enabling technologies), can lead to intensive release management and testing activities. Security is also of utmost concern when managing integrations as the API provides a potential entry-point from either system integration direction – the API has become a preferred target for malicious attacks on systems and networks.

Account Context Diagram

The purpose of the Account Context Diagram is to enable financial risk management by illustrating which processes create transactions on a given account, and which risks are related to this transaction.

Desktops

[vc_row][vc_column][vc_column_text css=""] Su...