What are the different levels of Interoperability? Explain.

-

 Levels of Interoperability

The interoperability levels related to the sharing of information in IFEG are mainly classified into:-

• Organisational Interoperability (like process-re-engineering including Government-Orders, Process Changes, Organisational Structures),

• Semantic Interoperability (Enabling data to be interpreted & processed with the same meaning, etc.) and

• Technical Interoperability (like technical issues in interconnecting ICT systems and services, information storage and archival, protocols for information exchange and networking, security, etc.); in general, technical interoperability was considered for classifying the standards into various layers or domains (eg. Presentation domain, Network domain, Data Interchange domain, etc.) in earlier versions of IFEG/GIF documents from various countries.


Description of Figure

It provides an overall view of the levels of the interoperability system. This helps define how applications and re-usable services will be developed and their interaction with other ICT systems. As indicated in the Figure, Organisational Interoperability is supported by Semantic Interoperability, which in turn is supported by Technical Interoperability. Hence Technical Interoperability forms the basis for the IFEG. Governance facilitates and enforces the implementation of IFEG.

 


Influencing Factor of E-Government  Interoperability Model/ Multilateral mechanism for IFEG

The Multilateral mechanism for IFEG is influenced or the influencing factor by the following key sub-areas:

1) Political – For strategy-related issues. In the Political context, support and commitment from an authority, provisioning of policies/guidelines, strategies over different levels of interoperability are expected.

2) Legal – For issues like IPR / Copy Right, content regulation, privacy, freedom of information, electronic identities, etc; these are context-sensitive. Legal factors include legal power assigned to a system for data protection and privacy information of the citizen, governance issues related to information management, executive orders, and laws related to e-Governance services, citizen services driven by administrative procedures, enforcement, etc.

3)  Managerial – For issues like training, motivation, reorientation of concerned staff from public agencies.

4) Economic – For funding-related issues.

5)  Social/Cultural – For social/cultural characteristics of system stakeholders. Social / Cultural factors like differences in culture, working practices, issues of trust, timings, social exclusion issues have more influence. Cultural and linguistic diversity in India introduces additional administrative constraints like naming conventions, multiple local official languages, language-dependent format, etc.

This mechanism should be defined (i) with transparent, consensual, collaborative open- environments and (ii) also through the participation from all stakeholders.



Description of Level of  E-Government  Interoperability Model

a)Organizational Interoperability

  • Organizational Interoperability enables a multilateral mechanism to ensure proper management and implementation of IFEG by identifying and addressing any possible barriers (including legal, political, managerial, and economic). The multilateral mechanism means organizational structures, appropriate processes, adequate resources, facilities, autonomy, and authority.
  • For coordination and managing implementation of IFEG, it is necessary to have a cross-departmental organizational structure that has a clear set of processes. By setting up these processes and activities, interoperability can be achieved both at a strategic and technical level. 
  • The organizational structure widely used is established in two ways:

       1)  Inter-agency and inter-ministry committee: This committee will be responsible for defining the enforcement policies for their department. This committee will ensure that the IFEG policy and standards are applied within the department/ministry.

       2) Operational group: This group will be responsible for executing and implementing IEFG and report to the concerned inter-ministry committee. The group will predominantly handle the technical adoption of IFEG. The group should be managed by persons with a technical background in ICT and ICT project management methodologies. The group would also coordinate and provide support to ICT projects and agencies related to interoperability.


b) Semantic Interoperability

  • Semantic Interoperability addresses the requirement of understanding the meaning of data by different stakeholders in the same way while exchanging data.
  • The purpose of Semantic Interoperability is to build the capability of all stakeholders involved in the delivery of e-Services, with the following functionalities:

1. Discover information requirements for the delivery of quality e-Services.

2. Explicitly describe the meaning of data to be shared multilaterally among the stakeholders.

3. Process the received information in a manner consistent with its intended purpose.

Basic elements of Semantic Interoperability are:

• Semantic description of data, which may have contextual meaning

• Semantic Mediation to resolve conceptual meanings differences, while exchanging data

• Semantic discovery of desired assets for seamless exchange of data

Semantic interoperability will require an agreement on the precise meaning of exchanged information among the e-Governance systems for the delivery of integrated e-Services.



c) Technical Interoperability

  • To knit different kinds of e-Governance infrastructure and their services together through a catalog of technical standards and specifications to achieve interoperability in e-Governance systems; this is done by exchanging information across various boundaries (applications, interfaces, libraries, levels of administration including vertical and horizontal, etc.) and storage/archival of the information.

Comments

Post a Comment

Popular posts from this blog

Discuss classification or taxonomy of virtualization at different levels.

-
Image
Taxonomy of virtualization Virtualization is mainly used to emulate the execution environment, storage, and networks. The execution environment is classified into two: – Process-level – implemented on top of an existing operating system.  – System-level – implemented directly on hardware and does not or minimum requirement of the existing operating system. OR,  Virtualization covers a wide range of emulation techniques that are applied to different areas of computing. A classification of these techniques helps us better understand their characteristics and use  V irtualization is mainly used to emulate  ● Execution Environments: To provide support for the execution of the programs eg. OS, and Application.  ○ Process Level: Implemented on top of an existing OS that has full control of the hardware  ○ System Level: Implemented directly on Hardware and do not require support from existing OS.  ● Storage: Storage vi...
Read more

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

-
Image
a) A Snowflake Shema is shown in figure below: b) The specific OLAP operations to be performed: 1. Roll-up on course from course_id to department. 2. Roll-up on a student from student_id to university. 3. Dice on course, student with department ="CS" and university = "biguniversity" 4. Drill-down on a student from the university to student_name. c) N = 4 dimensions The cube will contain 54 = 625 cuboids.
Read more

Suppose that a data warehouse consists of the three dimensions time, doctor, and patient, and the two measures count and charge, where a charge is the fee that a doctor charges a patient for a visit. a) Draw a schema diagram for the above data warehouse using one of the schemas. [star, snowflake, fact constellation] b) Starting with the base cuboid [day, doctor, patient], what specific OLAP operations should be performed in order to list the total fee collected by each doctor in 2004? c) To obtain the same list, write an SQL query assuming the data are stored in a relational database with the schema fee (day, month, year, doctor, hospital, patient, count, charge)

-
Image
Solution: a) Star Schema is shown in the figure below: b) First, we should use the roll-up operation to get the year 2004(rolling-up from the day then month to a year). After getting that, we need to use the slice operation to select (2004). Second, we should use roll-up operation again to get all patients. Then, we need to use the slice operation to select (all). Finally, we get a list of the total fee collected by each doctor in 2004. So, 1. roll up from day to month to year 2. slice for year = “2004” 3. roll up on patient from the individual patient to all 4. slice for patient = “all” 5. get the list of the total fees collected by each doctor in 2004 c) Select doctor, Sum(charge) From fee Where year = 2004 Group by doctor
Read more