Table 1 The evidence and analysis for semantic interoperability l Technical

Table 1 the evidence and analysis for semantic

This preview shows page 3 - 6 out of 11 pages.

Table 1. The evidence and analysis for semantic interoperability. l Technical interoperability Technical interoperability refers to that two or more ICT systems, or applications can appropriately provide data communication standards, exchange data and perform a given task without additional operator intervention (Ec.europa.eu, 2012). For this kind of interoperability issues, the Chief Information Officer Branch (CIOB) considered: Evidence 1. “SOA is a standardization of their interfaces.” 2. “The initial set of standards will cover key areas such as registering new services, how to discover reusable services, service mediation, service negotiation and other interoperability issues.” 3. “Departments are therefore asked to keep these principles in mind when planning, defining, implementing or changing business services or any of their supporting processes or technical components.” Analysis The pieces of evidence demonstrate that CIOB has developed standards to guarantee interoperability of services. However, the case does not contain specific interfaces and protocols for information and service transmission. Table 2. The evidence and analysis for technical interoperability.
Image of page 3
4 © University of Melbourne 2018 l Organisational interoperability Organisational interoperability refers to that makes information easy to identify and available to facilitate collaboration between different organisations to achieve their mutually agreed goals. Organisations require to reach detailed agreements on the collaboration and synchronisation of their business processes to provide integrated services based on demands (Kubicek & Cimander, 2009). For this kind of interoperability issues, the Chief Information Officer Branch (CIOB) considered: Evidence 1. By broadening the scope of SOA to also encompass the business levels helps to ensure department can interoperate to deliver a more agile, effective and efficient government overall. 2. “The emphasis on service orientation is synergistic with a number of other TBS directives and is consistent with the TBS policy renewal process.” 3. “The GC SOA defines a uniform approach to layering computer applications and their components to enhance interoperability and reuse.” Analysis The pieces of evidence illustrate that CIOB defines some methods to collaborate with other business processes of the organisation through SOA, without conflict, to provide integrated services, which basically satisfy the requirements of organisational interoperability. Table 3. The evidence and analysis for organisational interoperability.
Image of page 4
5 © University of Melbourne 2018 Question 2 Consider the statement on Page 7 (Section 4.2. The Value of SOA): “One of the key goals of a service-oriented design is to cut through the current information silos, promote interoperability and enable services to be delivered more effectively and uniformly. SOA adoption has the potential to erase the barriers that separate the business and technology sides of any organization, dramatically improving productivity, and increasing overall harmony and agility.”
Image of page 5
Image of page 6

You've reached the end of your free preview.

Want to read all 11 pages?

  • One '14
  • Government, Service-oriented architecture, Canadian government

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture