2.1 Sinnar case study
Sinnar is located in the south-eastern part of Sudan, bordered to the north by Gezira State, to the south by Blue Nile State, to the east by Gadaref State and the Sudanese-Ethiopian border, while to the west by the White Nile State and the borders of the State of South Sudan. The location results in Sinnar’s unique characteristics, as it is the main passage between different states. Sinnar state oriented to making use of information technology since 2006, when established its official authority (Sinnar Information Center (SIC)) responsible of information technology in general and e-government initiatives in particular. SIC has its own regulations, issued since 2008, then modified in 2013, as a result SIC became under supervision of Information consultant. In 2017 the law modified again and clarified to make SIC under supervision of State Government General Secretariat directly, and the regulations has been approved from state ministers’ council (Nesrein, A. 2017).
2.2 Data Analysis Procedure
Content analysis is consulted so as to be used in this study to identify. General themes through descriptive coding grounded around participants responses were defined taken from interview transcripts and documents, where code is defined as a word or short phrase that symbolically assigns a summative, salient, essence-capturing, and/or evocative attribute for a portion of language-based or visual data, whereas descriptive coding also called “topic coding” summarizes in a word or short phrase, the topic is what is talked or written about [15]. The interview questions were framed and divided into main five dimensions to reflect several aspects that may affect implementing and improving e-government i.e. IT infrastructure, standards and software integration, organizational aspects including managerial problems and cultural issues etc. as the research followed several steps to analyze the data started with preparing data where transcribing interviews, translating them into English and organizing documents, then reading data, writing up ideas, information and farming respondents’ thoughts. Identifying general themes and interpreting the meanings of data. The following are the results:
2.2.1 Information Technology infrastructure in Sinnar state
Figure (3.1) shows the percentage of respondents regarding to IT infrastructure in Sinnar state investigating the reality of network, websites, online services and corresponding evaluation of the existing websites. The sample participants taken form SIC staff member as well as IT technicians and managers from ministries, Sinnar and Singa localities, the original data came from interviews transcripts which has coded and transmitted into general themes to facilitate content analysis. The answers of participants have grouped into four main categories of responses as shown in figure (3.1); this wide range of response categories arises because the respondents have different backgrounds and diverse technological knowledge. Most of interviewees (78%) agreed that there is an existence of good networks, but only at headquarters in different institutions as they need an extension to cover other parties. It is obvious that there is a responsible IT infrastructure, as there are many computer networks but needs to expand to cover all governmental units in the state. In the other hand there is a lack of websites and online services.
2.2.2 Organization (human capabilities, change management and top management)
Figure (3.2) shows the organizations nature and its related factors which may influence implementing e-government in a proper manner such as culture, human capabilities, change management and top management. The results shows low percentage of IT competences of staff as well as the extent of top management awareness and commitment to e-government initiatives at (22%), (33%) respectively, as the organizations suffering from losing skilled staff with prorate of 89%. All this negatively affects the stability of organizations in general and their e-government initiatives in particular.
2.2.3 Challenges and barriers faces adopting e-government initiatives in Sinnar state institutions
Figure (3.3) illustrates the respondents’ views regarding to challenges that barriers implementing e-government effectively in Sinnar state, its noticed that funding is a key challenge that barriers e-government implementation. As interviewees mentioned very important points which maybe a key factors and main challenges that needs to be highlighted such as security issues, E-participation issues, Illiteracy, customs and traditions, resistance of IT innovations by old employees and politicians negative opinions about IT innovations.
It is worth mentioning that before conducting interviews in Sinnar state, NIC was included to take a general view at national level because it is an official authority responsible for e-government all over the country and serves as a policy maker and advisor for states information centers. Some valuable information gained from NIC, regarding to reusability the respondents agreed that there is no methodology used to reuse these systems or software, and the evidence for this is that there are many similar systems in government units which lead to wasting state money. While the main challenges of integration process could be: Lack of regulations, security issues, data sharing, heterogeneity, as different government units use different types of technologies and management issues, as there is a resistance from other organization related to integration.
2.3 SOA Methodology for e-government Applications
This section introduces the methodological steps that form the SOA approach for e-government, which can address most of the requirements of the current E-government system development in Sinnar state. The focus is to propose organized steps which leads to a set of well-defined web services that would adapt to the way in which government services are provided in general, and services that common to government unit in particular. Also the proposed methodology takes into consideration the good practices from industry experience to create integrated and coherent web services.
2.3.1 Implementation and Design
The following is the sequential steps of the methodology for web services development to integrate e-government systems as well as to enhance software components reusability.
2.3.1.1 Web Services Development Steps
The figure (3.4) shows the empirical steps used to develop web services form selected business process domain, as it represent a development workflow.
Consequently, the phases identified to be suitable for web services lifecycle phases are: requirement, analysis, design, implementation, test and deployment.
2.3.2 Design Scope
In this step business process scope defining carefully for analysis purposes, the analysis affords the basis for verification of completeness of the design [16]. This step identifies relevant business process and participants. Figure (3.5) illustrates the general design framework.
Figure (3.5) shows sequential steps begins with business function decomposition and the goal of this step is to decompose the business process into elementary business functions, identifying sub-functions, activities and actions. This method will maximize the cohesion as basic business functions typically realize a single concrete task. Next step is to define group of services corresponding to the basic business functions identified in a previous step, Services should allocate in a separate manner according to their specific functionality to ensure reusability. Then define group of operation for each service according to the business logic with their input and output messages to form the service interface. In this step, the services are designed and named; typically the service consists of the service name, message type where there are two types of message (input and output) and then message name must be specified to determine whether the operation status is request or response.
While the definition of service interface is the specification of services operations and assigning input and output parameters to individual operations are performed in this step to form service interfaces. So interface definition specifies operation name, message type, message name to determine whether the message is for request or response and finally the message content which is typically contains attributes in case of request status or return value in case of response message.
2.3.3 Implementation Architecture
An enterprise service bus (ESB) is one of middleware that used as implementation architecture, also it is used to route a mange messages between service provider and service consumer. ESB provides different virtualization patterns; one of them is an interface The ESB pattern can be either hardware or software middleware products [17].
Figure (3.6) describes the logic of the implementation architecture which using publish-subscribe strategy , as services can be published via bus engine and registered to ESB, so it provide alternatives to service consumers in case of the target endpoint is not available. The implementation architecture scenario in the context of this research, SIC the service provider deploying available web services which symbolizes common shared services among deferent governmental units into main servers (ESB). Using description and specification of the web services the governmental services expose and use suitable ones to their business functions to realize certain functionality in their systems. This way the governmental units are able to build their systems through assembling functionalities offered by these reusable web services, and it does not need to worry about technological details used to define and realize these web services, since its lay on open standards which makes them interoperable components.
To sum up all: the proposed methodology is comprised of three main stages with different activities as shown in table (3.1).
Table 3.1: SOA methodology stages
Stage
|
Elements (activities)
|
Service Identification
|
Web service development steps.
|
Web service development lifecycle.
|
Service Specification
|
Principles and guidelines.
|
Design scope.
|
Business function decomposition.
|
Defining services.
|
Defining service interface.
|
Realization
|
Implementation architecture.
|
Table (3.1) shows the three stages of SOA methodology and its associated activities, it begins with service identification where standard web service development steps followed and its lifecycle considered then specifying web services by decomposing business function to facilitate the definition of services and their interfaces considering industry experience and best practices. The last stage concerns with the realization step, where decision taken about certain implementation architecture.
Although the proposed methodology, didn’t addressed managerial aspects. However, it remains a very important aspect to take into account when intending to develop e-government applications, as it may affect the process as whole positively or negatively. Managerial aspects need to be implicitly considered in working in e-government projects e.g. preparing budgets and top management support as well as IT infrastructure.