Previous Page  113 / 162 Next Page
Information
Show Menu
Previous Page 113 / 162 Next Page
Page Background

Single Window Systems

In the OIC Member States

103

Why does it matter?

Changes or integration of new functionalities with a hard coded approach is very costly and

complex. Changing hundreds of thousands lines of code with a many dependencies and linked

functionalities is an expensive and complex process that requires upmost effort, even for the

most skilled programmers.

2. Lack of Interoperability at the Data and Business Process Level

The IT architecture needs to have the ability to connect, integrate and support diverse and

legacy IT systems and applications. SWs therefore have to embed system-to-system connectivity

or services. This allows SWs to provide collaborative, networked and interconnected workflows

and business processes.

Interconnectivity has the following three dimensions:

process level whereby standardised and procedures build the foundation for a common

process and data model.

message interoperability whereby data is exchanged in a process based on the same

semantic structures and definitions.

technical interoperability, which translates into infrastructure requirements to support the

technical exchange of information.

Why does it matter?

The lack of interoperability is a major obstacle in view of compromising SW’s ability to provide

services, data and information to the users in a timely and accurate manner.

3. Ensure Data Protection

Security of the overall system and protection of stored data and data in transit is a crucial

requirement for SW. Data needs to be protected from unauthorized use with encryption

techniques used for all traffic from point-to-point. SWs must develop and maintain sophisticated

user authorizations system for both end-users and service providers.

Why does it matter?

Security is closely linked to the need for trust and is growing in importance sue to increase

public awareness. It is even more crucial when there is a direct linkage to the financial activities,

i.e. payment activities.

Policy Options

1. Re-use of Services

The re-use of services is the linking of individual services to one or more new or pre-existing

services. A service generally contains most or all of the presentation and process logic, and it

may also have same or similar data set. The majority of business processes in a SW application

and server layer are provided by services that were previously deployed and could therefore be