Evaluating the Role of Requirements Engineering Practices in the Sustainability of Electronic Government Solutions

Abstract

The efficacy of electronic government (E-Government) initiatives relies significantly on requirements engineering (RE). Every government wants sustainable solutions in the implementation of E-Government projects. The current research has adopted a mix of research methods. After conducting a comprehensive systematic literature review (SLR), the author conducted a case study to evaluate the proposed model. This research conducts an SLR of the contemporary literature on the success and failure factors of E-Government projects. Additionally, there is an association between the failure factors and the utilization of RE practices. A comprehensive search of electronic databases yielded a total of 71 pertinent articles. After meticulous screening and quality assessment, the data were extracted for analysis. A total of 62 papers were eventually selected. The SLR addressed the distinct hurdles encountered by government bodies. The findings indicated a positive relationship between the utilization of RE practices and the attainment of project success. Various aspects, such as project management practices, stakeholder engagement, and effective communication, were identified as factors that can reduce failures in E-Government projects. The deficiencies observed in E-Government initiatives were linked to inadequacies in implementing RE practices. The other issues identified were insufficient requirement elicitation, limited stakeholder involvement, and inadequate validation and verification of requirements. This study also presented a conceptual framework illustrating the difficulties in E-Government and the practices of RE. Statistical data analysis techniques were employed to examine this conceptual framework. This study suggests that managers examine and evaluate their E-Government project failure reasons and factors on a periodic basis to sustain and continuously enhance E-Government project success.

1. Introduction

E-Government has historically been defined as the application of Information and Communication Technologies (ICTs) to increase agency efficiency and deliver services via the internet. “Online government services” and “exchange of information and services electronically with businesses, citizens, and other departments of government” are two examples of the term E-government [1,2]. Determining the objectives, capabilities, and limitations of hardware and software systems is the primary objective of RE, a sub-discipline of software engineering and systems engineering. What needs to be produced in a software system is determined through the process of software RE [3,4]. RE plays a crucial role in the development of E-Government initiatives. It encompasses the identification, analysis, documentation, validation, and management of project requirements to ensure that the final output aligns with stakeholder needs and expectations. Its scope also covers a broad spectrum of activities, including online access to government information and services, electronic voting, digital procurement, and the management of digital documents. Notably, these services are generally more cost-effective than conventional face-to-face services [5].

These technologies foster improved connections between governments and their constituents, thus promoting transparency and reducing corruption by minimizing citizens’ direct interactions with government personnel [6]. Over the past few decades, the prominence of E-Government has surged due to the growing significance of information system (IS) solutions in enhancing individual well-being, bolstering the efficiency of governmental organizations, and encouraging greater civic engagement [7]. Its appeal in both practical and research spheres has also captured substantial academic attention in recent years, owing to the distinctive attributes that define E-Government. These attributes extend beyond administrative and legal factors, encompassing various qualitative elements that demand a specialized scientific and practical approach [8].

During the creation of E-Government systems, the implementation of RE methods frequently entails close collaboration with government institutions to comprehend their requirements and those of the citizens who will utilize the systems. This procedure might encompass collecting requirements via interviews, workshops, and other techniques, as well as clearly and succinctly documenting these demands [9]. It is equally crucial to authenticate the requirements to guarantee their comprehensiveness, coherence, and viability, while also overseeing any alterations to the requirements during the development phase [10].

Nonetheless, the utilization and integration of E-Government systems can be impeded by various challenges encountered within diverse software development methodologies. These hurdles can be interconnected with requirements engineering practices, which involve delineating and documenting the specifications for a system or product and guaranteeing that these criteria are fulfilled throughout the developmental and implementation stages [11]. Ensuring that E-Government systems are user-friendly, compatible, and secure necessitates meticulous planning and design, with addressing these issues being pivotal for the triumph of E-Government initiatives. The employment of RE practices can ensure that E-Government systems cater to the needs and anticipations of citizens and government entities. By identifying and tackling probable obstacles and prospects during the preliminary phases of the development process, RE practices can facilitate the successful integration and utilization of E-Government systems.

This research systematically examines the published literature to identify and use both success and failure factors for E-Government projects. Furthermore, this study’s outcomes offer valuable insights and recommendations to scholars, highlighting areas where additional research is warranted concerning the usage of RE practices within E-Government projects. The section on the research methodology outlines the approach to the SLR adopted when conducting this study. Lastly, the findings section discusses the results of the SLR in addressing the research inquiries. This study commenced by investigating the causes of project failures and the factors capable of mitigating E-Government project risks. Subsequently, the research identified contemporary RE practices aimed at reducing E-Government project failures. An assessment of the effectiveness of these RE practices was also conducted. Furthermore, the research identified challenges in E-Government projects documented in the literature, suggesting a need for further industry studies to explore potential solutions.

2. Background

E-Government, historically characterized as the utilization of information and communication technologies (ICTs), aims to enhance agency efficiency and provide services through the Internet. Examples of E-Government include online government services and the electronic exchange of information and services with businesses, citizens, and other government departments. To ensure their efficacy, these systems need to be meticulously tailored to meet the requirements of the diverse stakeholders involved, including citizens, government personnel, and other public entities. RE encompasses various stages, such as requirement elicitation; the documentation, verification, and validation of requirements; and requirement management and planning. It is vital to iteratively conduct RE, involving multiple stakeholders throughout the software development life cycle [12]. Typically, RE is initiated at the outset of the software system development process. While this may be suitable for shorter-term projects, sustaining stable requirements over an extended period for large-scale and long-lasting E-Government initiatives to meet public needs is a formidable task. Long-lasting E-Government initiatives may be affected by different factors, such as minimizing system redundancy and waste [13,14], compliance with regulatory and environmental standards [15,16], feedback loops and continuous improvement [17,18], data security, and privacy considerations [19,20].

2.1. Lack of Best Practices

Prior studies have highlighted the absence of established best practices in RE for E-Government initiatives. This exacerbates the challenges encountered by project teams, given the inherent complexities and the influence of political and legislative demands in E-Government projects [21]. These include the ongoing consideration of citizen-centric requirements and satisfaction [9], the need for supporting legacy systems and transitioning data to modern technology [22], and the necessity for usability features such as system error prevention, intuitive navigation, and consistent user interface design [23,24], as well as security and performance efficiency requirements.

2.2. Bureaucratic Procedural Barriers

Government IT departments encounter additional challenges related to bureaucratic and procedural obstacles, particularly within the procurement process. Consequently, there has been a surge in the adoption of commercial off-the-shelf (COTS) products, which can become expensive to maintain over prolonged periods. Moreover, the reliance on proprietary technology within COTS products often leads to poor interoperability, owing to vendor lock-in strategies. One possible solution to address this issue is for E-Government entities to develop customized or tailored solutions. However, research has indicated that government initiatives are significantly affected by scope creep, risk-averse decision-making, and employee turnover, which can alter the project objectives [25].

2.3. Cultural Impact on RE

Communication is central to successful RE practices. Cultural nuances significantly influence interpersonal dynamics and task execution, thereby impacting RE procedures. The risk of project failure can be notably mitigated by addressing cultural discrepancies between requirements experts and clients. Strategies such as conflict resolution through compromise, fostering trust, acknowledging uncertainty, maintaining transparency, and assuming accountability are effective in this regard. Conversely, issues such as hidden agendas, administrative interference, and client-driven technological solutions that directly impact project deliverables have been observed to be prevalent and challenging for RE practitioners. These challenges can potentially affect the efficiency of RE activities. As a result, early requirement validation should be incorporated into multiple project cycles to ensure smoother processes [26]. It is evident from the above discussion that RE practices in the domain of E-Government projects are a challenging area, and it is required to elicit the state of the art in both theory and practice.

3. Research Methodology

The chosen research approach for this study is an SLR. The primary objective of the SLR methodology is to comprehensively explore, assess, and synthesize all the existing literature on a particular subject (Salahuddin and Ismail, 2015). The research adhered to the guidelines outlined in [27], with specific adaptations made to suit the unique context of this investigation. This process encompasses all aspects, from the preparation of the review to the presentation of the review’s findings. The subsequent sections detail each of these phases.

The research methodology of this study is illustrated in Figure 1. The methodology involves the following stages: (i) formulating the research question; (ii) identifying rel-evant studies; and (iii) selecting and evaluating relevant studies.

The main objectives of this review are to assess the latest successful practices in requirements engineering (RE) and to aid E-Government professionals in enhancing the implementation of past, current, and future RE practices in E-Government systems. The author asserts that while requirement processes are integral to public sector systems, professionals often overlook their systematic implementation and the specific requisites and challenges inherent to the public and governmental spheres. To achieve the research objectives, the author conducted an SLR, encompassing relevant publications released from 2004 to 2023. The subsequent sections of this article are structured as outlined below. The background segment will delve into the complexities associated with employing RE practices in E-Government environments. A comprehensive examination and analysis of various studies dedicated to the application of requirement methodologies and principles to E-Government will ensue. In light of the scarcity of research in this area, recent studies addressing challenges encountered by public agencies unrelated to the requirements process will also be explored. Through the analysis and evaluation of successful RE approaches, this research seeks to pinpoint effective strategies and methodologies that can improve the development and implementation of E-Government projects. Implementing these best practices can streamline the collection, documentation, validation, and management of requirements for E-Government practitioners, ultimately resulting in more efficient and effective E-Government solutions. This study extensively utilizes various relevant sources, such as academic research, industry publications, and case studies, to comprehensively delineate the current panorama of RE practices within the realm of E-Government.

Information about Figure 1 is given below:

• Formulating the research questions. The following research questions (RQs) were developed to meet the research goals:
  RQ1: What RE techniques have been most recently used in E-Government projects?
  RQ2: How effective are the practices for RE in producing successful project outcomes?
  RQ3: What are the key factors that contribute to the reduction in failures in E-Government projects?
  RQ4: How are the failure factors in E-Government projects linked to the utilization of RE practices?
  RQ5: What are the existing gaps in the current literature pertaining to the application of RE practices in E-Government projects?
  The following research questions (RQs) were developed to help attain these objectives:
• Identifying relevant studies. Identifying relevant studies. During the second step, “identifying relevant studies”, a comprehensive search was conducted in seven electronic databases, namely, Google Scholar, Scopus, IEEE Xplore, ACM Digital Library, Science Direct, Springer Link, Taylor and Francis Online, and Springer. The search encompassed titles, abstracts, topics, and keywords to minimize the possibility of overlooking pertinent articles. These databases were selected due to their inclusion of influential journals and conference proceedings in the domains of software engineering and information systems, specifically within the context of E-Government and RE practices. After an initial exploration of the selected databases and subsequent reference cross-checking to ensure comprehensive coverage, a meticulous selection of relevant studies was made. Various combinations of keywords were employed to form search strings, with the primary keywords including “RE best practices”, “project failure”, “reasons for project success and failure”, and “E-Government”, utilizing the AND and OR combination of these keywords. Their synonyms enabled the extraction of pertinent research articles. During this phase, the process of identifying relevant studies initially resulted in 71 pertinent articles.
• Selecting and evaluating relevant studies. This step included two criteria: (a) inclusion criteria and (b) exclusion criteria. It was ensured that the database search included titles, abstracts, topics, and keywords in order to reduce the chance of missing relevant papers. The inclusion and exclusion criteria were as follows:

  (a)

  Inclusion criteria:

  The following criteria were used to add publications to the SLR: (1) the publication was written in English, (2) the publication was peer-reviewed, and (3) the publication discussed E-Government projects’ failures, successes, or any practices related to this area. As a result of applying inclusion criteria, the number of relevant papers was reduced to 68 papers.

  (b)

  Exclusion criteria:

  The following criteria were used to reject publications from the SLR: (1) the publication was written in a language other than English; (2) the publication was unable to provide information about E-Government projects’ failures, successes, or any practices related to this area; (3) the publication was conducted without peer review; (4) the publication had copyright or information sharing issues to full-text access. To facilitate the review process, each publication was systematically examined by assessing the abstracts to determine whether they met the inclusion criteria [24], which were as follows:

  • Publications in the English language within the period from 2004 to 2023, focusing on failure or success factors in the sphere of E-Government, were considered for this review
  • The articles needed to be composed from the perspective of executing requirements engineering practices in E-Government initiatives.

  As a result of applying inclusion criteria, the number of relevant papers was reduced from 68 to 65 papers.

  (c)

  The criteria employed in this procedure included attributes such as digital library, title, source, number of citations, research method, data analysis method, data collection method, analysis technique, outcomes, and limitations of the publication. Following the execution of the data extraction and synthesis process, the author selected the most relevant 62 studies.

  (d)

  Reporting results:

  Finally, in the fifth step, “Reporting results”, the author concluded the findings and reported them in a structured way.

4. Results

Here, we unveil the findings of our research efforts. We delve into the conclusions drawn from the literature review by addressing the research inquiries outlined in the introduction.

RQ1: What RE techniques have been used most recently in E-Government projects?

RE is a pivotal procedure in the progression of E-Government projects, encompassing the identification, analysis, documentation, validation, and management of project requirements to guarantee that the end result aligns with stakeholder needs and expectations. Numerous investigations have explored the RE methodologies employed in E-Government endeavors. The results of these studies are outlined as follows:

The following are some of the most recent RE techniques used in E-Government projects:

• Stakeholder Analysis: This process entails identifying and analyzing the needs, concerns, and expectations of stakeholders. This makes sure that the opinions of all parties involved are taken into account and recognized in the finished work.
• User Stories: Because they precisely identify user requirements and ensure that the final product fits those needs, user stories are an effective framework for developing requirements.
• Agile Methodologies: Scrum and other agile methodologies have been increasingly popular in recent years due to their adaptability in addressing changing demands and their emphasis on stakeholder involvement. These strategies provide continuing input and iterative development, assisting in ensuring that the developed system fulfills the needs of stakeholders.
• User-Centered Design: Understanding end user demands and developing solutions that meet them are the main goals of user-centered design. This strategy guarantees that the system is usable and accessible for people with different degrees of technical knowledge while working on E-Government initiatives.
• Requirements Traceability: The core goals of user-centered design include under-standing end user needs and creating solutions that address them. This method ensures that the system is accessible to users with various degrees of technical competence in E-Government initiatives and is user-friendly.
• Use of Prototypes: Stakeholders can offer comments on a rudimentary prototype of the system before the final system is constructed. While guaranteeing that the final system satisfies the criteria of the stakeholders, this procedure can lower the chance of expensive mistakes.
• Risk Management: Risk management includes both identifying possible project hazards and developing mitigation plans. You can ensure that the project stays on schedule and any difficulties are resolved before they worsen by putting this approach into place.
• Automated RE: Automated methods, such as natural language processing and machine learning, can be utilized to scrutinize and identify requirements from diverse sources, including citizen feedback, social media, and other online platforms.
• Model-Driven RE: In E-Government projects, model-driven approaches are employed to depict and illustrate requirements, often utilizing languages such as the unified modeling language (UML) or Business Process Model and Notation (BPMN). This aids in minimizing the possibility of ambiguity in requirements and enhancing their understanding.

The aforementioned practices can guarantee the effectiveness of E-Government initiatives and meet the requirements of stakeholders.

Table 1. RE practices for E-Government.

Serial	Description
1	Stakeholder analysis [28,29,30,31,32]
2	User stories [33]
3	Use of agile methodologies [34,35,36,37,38]
4	User-centered design [38,39]
5	Requirements traceability [40,41,42,43]
6	Use of prototypes [44,45,46,47,48]
7	Risk management [49,50,51,52]
8	Automated RE [17,53,54,55]
9	Model-driven RE [56,57,58,59]

outlines nine RE practices suitable for the implementation of E-Government projects.

RQ2: How effective are the practices for RE in producing successful project outcomes?

Effective RE practices are essential for the success of E-Government projects. These practices aid in the identification, documentation, and efficient management of stakeholder requirements, thereby reducing the risk of project failure and enhancing the prospects of project success. Some of the benefits of integrating robust RE practices into E-Government projects include the following:

• Improved stakeholder satisfaction: By ensuring that the system being developed meets their requirements, RE processes can enhance stakeholder satisfaction with the final product.
• Reduced development costs: RE practices can reduce the costs associated with rework and prevent costly errors by identifying and addressing requirements prior to the development process.
• Reduced project risk: RE practices can help mitigate the risk of project failure and increase the likelihood of project success by identifying and managing risks in the early stages of the development process.
• Improved project management: RE practices can aid in project management by providing a formal framework for handling and evolving requirements, thereby ensuring that the project stays on track.
• Improved system quality: RE practices can enhance the quality of the final product by ensuring that the system under development meets the expectations of stake-holders.

Table 2. Benefits of RE practices.

Serial	Description
1	Improved stakeholder satisfaction [43,60]
2	Reduced project risk [22,61]
3	Improved project management [62,63]
4	User-centered design [38,39]
5	Improved system quality [64,65]

outlines five advantages of RE practices. To summarize, proficient RE methods can enhance the progress of E-Government endeavors. Nevertheless, the precise outcomes may vary depending on the practices utilized and the context in which they are applied.

RQ3: What are the key factors that contribute to the reduction in failures in E-Government projects?

Insufficient planning, ineffective management, limited stakeholder engagement, and technological challenges represent only a few of the hurdles that E-Government projects may confront. Several factors can enhance the prospects of project success and diminish the risk of failure. Some of these pivotal factors include:

• Effective planning: Establishing a clear plan that outlines the project’s aims, scope, schedule, and resources ensures that the project remains on track and that all stakeholders are aligned with its goals and objectives.
• Stakeholder involvement: Engaging and consulting stakeholders throughout the project’s life cycle, including residents, officials, and other relevant parties, helps uncover and address their needs and requirements.
• The use of appropriate technology: The project’s success can be enhanced by selecting appropriate and reliable technologies that meet the specifications of its needs and requirements.
• Robust RE practices: Employing effective RE methods, such as requirements elicitation, analysis, validation, and verification, can help guarantee that the project meets stakeholder needs and that the system is fit for the intended purpose.
• Project management: An effective project management framework ensures the successful handling of the project and prompt resolution of any arising issues.
• Change management: Change management practices can mitigate the risk of scope creep and project delays by effectively identifying, documenting, and managing changes to project requirements or objectives.
• Risk management: Throughout the project, possible risks can be identified and mitigated to reduce the likelihood of failure.

These measures can enhance the likelihood of success for E-Government projects and aid in meeting the requirements of all stakeholders.

Table 3. Factors contributing to minimizing E-Government project failures.

Serial	Description
1	Effective planning [66,67]
2	Stakeholder involvement [68,69,70,71]
3	Use of appropriate technology [72,73,74]
4	Robust RE practices [75,76,77,78]
5	Project management [78,79,80,81]
6	Change management [77,80,82,83,84,85]
7	Risk management [52,68,86,87,88]

outlines seven key factors that can reduce the failure of E-Government Projects.

RQ4: How are the failure factors in E-Government projects connected to the implementation of RE practices?

The failure factors in E-Government projects are frequently associated with the execution of RE practices. Proficient RE is pivotal for project success, ensuring that the system meets the demands and expectations of stakeholders. The inadequate implementation of RE practices may result in various complications, including the following:

• An inadequate understanding of stakeholder needs: Failure to sufficiently collect and assess stakeholder demands can lead to a system that fails to meet their ex-pectations, resulting in inadequate user adoption and eventual project failure.
• Poor system design: Incorrect system design can lead to problems such as difficulties in scaling, system failures, and various technical issues that can significantly impact the project’s achievements.
• Scope creep: Insufficiently defined requirements can lead to scope creep, which involves a sudden expansion of the project’s scope beyond its initial limits due to an increase in requirements. Inadequately specified requirements can be a major cause of this result. This can lead to project delays, increased costs, and other adverse outcomes that can jeopardize the project’s success.
• A lack of stakeholder engagement: A lack of early stakeholder involvement in the project’s initial stages may generate irrelevant requirements, resulting in a solution that does not align with user needs and, consequently, leading to the failure of the E-Government project.

Implementing the best RE practices, however, can help mitigate many of these risks and increase the likelihood of project success. For example, by accurately gathering and assessing stakeholder requirements, the system can be tailored to meet those objectives, thus enhancing user adoption and satisfaction. Similarly, defining requirements and managing scope can aid in the successful management of the project, thereby reducing the risk of delays and budget overruns. Engaging stakeholders throughout the project’s life cycle can ensure alignment on the project’s goals and objectives, consequently fostering buy-in and ownership, as well as reducing resistance to change

Table 4. Failure reasons for E-Government projects.

Serial	Description
1	Inadequate understanding of stakeholders’ needs [89,90,91,92]
2	Poor system design [21,93,94,95,96]
3	Scope creep [97,98,99,100,101,101]
4	Lack of stakeholder engagement [67,92,102,103,104]

outlines four key causes of failure in E-Government projects.

RQ5: What are the existing gaps in the current literature pertaining to the application of RE practices in E-Government projects?

Despite the extensive literature on RE practices in E-Government projects, there remain several areas that have not been adequately addressed. Some of these gaps include the following:

• A lack of empirical studies: Existing research on E-Government solutions reveals a dearth of empirical studies examining the effectiveness of RE practices. Most of the current literature is reliant on case studies or expert opinions, potentially limiting a comprehensive understanding of the outcomes of E-Government solutions.
• Limited focus on specific E-Government domains: The majority of research on RE techniques in E-Government solutions concentrates on general E-Government areas, such as healthcare or public services.
• A lack of standardization: There is no standardized framework or set of procedures for RE practices in the world of E-Government systems. Comparing and ranking various RE methodologies is difficult in the absence of standards.
• Limited focus on stakeholder engagement: Although the value of stakeholder involvement in RE is well acknowledged, the best ways to include stakeholders in E-Government efforts are still not well known. To determine the best practices for incorporating stakeholders in E-Government initiatives, further study is required.
• Limited focus on cultural and social factors: Cultural and social factors, such as linguistic complexity and social conventions, frequently have an impact on E-Government projects. Only a small number of studies have examined how cultural and social norms impact RE techniques used in E-Government systems.

Addressing these gaps in the current literature can enhance our comprehension of RE practices employed in E-Government initiatives and facilitate the development of effective methodologies for RE within these projects. The present study has also organized the discoveries from the existing literature and formulated a conceptual model. Figure 2 illustrates the conceptual model of E-Government challenges and RE practices.

Table 5. Interlinking failure factors, failure reasons, and specific RE practices.

E-Government Project Failure Factors	E-Government Project Failure Reasons	RE Practices for E-Government Project Success
Insufficient planning	Inadequate understanding of stake-holders’ needs	Stakeholders analysis Requirements traceability Model driver RE
Incomplete stakeholders’ involvement	Lack of stakeholders’ engagement	Stakeholders analysis User stories
Use of inappropriate or outdated technology	Poor design	User-centric design Prototype Model driver RE
Robust and insufficient RE practices	Scope creep Inadequate scoping	Risk or change management Requirement traceability Model driver RE
Poor project management	Scope creep Uncontrolled scope changes	Agile methodology Risk management
Inadequate change management	Scope creep Inadequate scope changes	Change management Requirement traceability
Risk management	Scope creep Lack of stakeholder engagement Poor Design	Risk management Automated RE

presents the interlinking among factors and failure reasons, as well as the particular RE practices related to them. Below, Table 5 is discussed in detail.

Table 5 presents the reasons of E-Government projects.

1.

Effective Planning (Failure Factor) and Inadequate Understanding of Stakeholders’ Needs (Failure Reason):

Connection: Inadequate understanding of stakeholder needs often results from insufficient planning, where requirements are not thoroughly analyzed.

RE Practices for Prevention:

• Stakeholder Analysis: Conducting comprehensive stakeholder analysis during planning to ensure all perspectives are considered.
• Requirements Traceability: Implementing traceability to link requirements back to stakeholder needs, ensuring alignment throughout the project.

2.

Stakeholder Involvement (Failure Factor) and Lack of Stakeholder Engagement (Failure Reason):

Connection: A lack of stakeholder engagement leads to incomplete involvement, thus impacting decision making and requirement definition.

RE Practices for Prevention:

• Stakeholder Analysis: Conducting stakeholder analysis early to identify key stakeholders and ensure their continuous involvement.
• User Stories: Utilizing user stories to directly capture stakeholder perspectives and requirements from them.

3.

Use of Appropriate Technology (Failure Factor) and Poor Design (Failure Reason):

Connection: Poor design often results from selecting inappropriate or outdated technology that does not align with stakeholder requirements.

RE Practices for Prevention:

• User-Centric Design: Focusing on user-centric design principles to ensure technology aligns with user needs.
• Prototyping: Using prototypes to validate technology choices and ensure they meet stakeholder expectations.

4.

Robust RE Practices (Failure Factor) and Scope Creep (Failure Reason):

Connection: Insufficient RE practices can lead to inadequate scoping, causing scope creep and project deviations.

RE Practices for Prevention:

• Change Management: Implementing robust change management processes within RE to control scope changes effectively.
• Requirements Traceability: Using traceability to evaluate the impact of proposed changes on the initial project scope.

5.

Project Management (Failure Factor) and Scope Creep (Failure Reason):

• Individuals responsible for ensuring project quality and adherence to requirements.

Connection: Poor project management can lead to inadequate monitoring and control of scope, contributing to scope creep.

RE Practices for Prevention:

• Agile Methodology: Embracing agile practices to accommodate changes and iterations within a controlled framework.
• Risk Management: Incorporating risk management to anticipate and mitigate scope-related risks during project management.

6.

Change Management (Failure Factor) and Scope Creep (Failure Reason):

Connection: Inadequate change management processes can lead to uncontrolled scope changes, contributing to scope creep.

RE Practices for Prevention:

• Change Management Processes: Implementing structured change control mechanisms within RE to manage scope changes effectively.
• Requirements Traceability: Using traceability to assess the impact of change requests on the project’s scope and objectives.

7.

Risk Management (Failure Factor) and Various Failure Reasons:

Connection: A lack of proper risk management can contribute to multiple failure reasons, including scope creep, inadequate stakeholder engagement, and poor design due to unanticipated challenges.

RE Practices for Prevention:

• Risk Management: Integrating risk management practices within RE to identify and mitigate risks early in the project lifecycle.
• Automated Requirements Engineering: Employing automated tools for risk assessment and analysis during RE processes.

By interlinking failure factors, failure reasons, and specific RE practices, it becomes evident how robust RE practices play a pivotal role in preventing or mitigating various failure factors and reasons within E-Government projects. These practices ensure alignment with stakeholder needs, effective management of project scope, and the selection of appropriate technologies, thereby enhancing project success and minimizing failure risks.

4.1. Description of Experimental Design

This study’s conceptual research model is the result of a thorough evaluation of the literature, with citations included for each construct. Table 1, Table 2 and Table 3 provide detailed documentation of this thorough synthesis, with a thorough cataloging of references linked to each construct. In order to ensure a solid foundation for examining the interactions of different constructs within the research framework, this model’s con-struction required a thorough examination and assimilation of pertinent concepts and theories present in scholarly discourse.

Figure 3 led to the formulation of the following claims:

H1: 

A positive relationship is present between E-Government project failure reasons and RE practices for E-Government project success.

H2: 

A positive relationship is present between factors minimizing E-Government project failures and RE practices for E-Government project success.

Extensive analysis was conducted on the theories and methodologies employed to delineate the independent and dependent components within the study framework. The exploration into the intricacies surrounding the success and failure of E-Government initiatives was facilitated through a questionnaire that examined a diverse range of variables and procedures. Using Likert-scale questions to gauge participant perspectives and opinions, a carefully crafted questionnaire was used to gather crucial data for this study. In total, 208 individuals represented different positions in E-Government companies. The various positions included the following:

Participant roles and positions:

1.

Project managers:

• Individuals overseeing E-Government projects.

2.

Software engineers/developers:

• Those involved in the technical implementation and development aspects.

3.

Business analysts:

• Individuals responsible for analyzing project requirements and translating them for technical teams.

4.

Government officials:

• Personnel working directly within government departments utilizing or commissioning E-Government projects.

5.

Quality assurance/testing specialists:

• Individuals responsible for ensuring project quality and adherence to requirements.

The spectrum of independent variables encompasses both the factors contributing to project success and the root causes of failure. The scrutiny of elements such as scope creep, inadequate system design, and a deficiency in understanding stakeholder needs occurred when delineating E-Government project failure reasons. In contrast, independent variables contributing to E-Government project failure factors include robust RE techniques, effective planning, stakeholder involvement, the adept use of technology, project management, change management, and risk management. All these factors play a pivotal role in shaping the outcomes of E-Government projects.

In the analysis, the dependent variable is the compilation of RE practices for E-Government project success. This compilation encompasses aspects such as requirements traceability, automated RE, model-driven RE, user stories, stakeholder analysis, the application of agile methodologies, user-centered design, the utilization of prototypes, and the incorporation of risk management. Through this comprehensive exploration, trends and insights are unveiled, enhancing the understanding of the outcomes of E-Government projects in a more nuanced manner.

A preliminary test was carried out after the tool’s development to evaluate its dependability and internal consistency. The process of calculating Cronbach’s alphas was essential to achieving strong internal consistency. The following table displays the Cronbach’s alpha values obtained. These values offer valuable insights into the tool’s reliability, thereby bolstering its internal coherence and guaranteeing its efficacy in measuring the intended constructs.

4.2. Reliability Analysis

Reliability, as defined by [105], pertains to the consistency of results. To evaluate the data’s reliability, Cronbach’s alpha values are utilized.

Table 6. Findings from the reliability analysis.

Construct Name	No of Items	Cronbach’s Alpha
E-Government project failure reasons	4	0.913
Factors minimizing E-Government project failures	7	0.842
RE practices for E-Government project success	9	0.863

displays the results of the reliability analysis.

Cronbach’s alpha is a widely recognized reliability measure employed to evaluate the consistency of constructs. For an instrument to be deemed reliable, Cronbach’s alpha for each construct should be greater than 0.70 [106]. As illustrated in the preceding Table 6, the alpha values exceed 0.5.

4.3. Summary of hypotheses

Below Table 7 outlines is a summary of hypotheses testing based on structural model analysis.

Table 7. Summary of Hypotheses.

Sr.	Hypothesis	Conclusion
H1	A positive relationship is present between E-Government project failure reasons and RE practices for E-Government project success	Accepted (significant)
H2	A positive relationship is present between factors minimizing E-Government project failures and RE practices for E-Government project success	Accepted (significant)

Table 7. Summary of Hypotheses.

Sr.	Hypothesis	Conclusion
H1	A positive relationship is present between E-Government project failure reasons and RE practices for E-Government project success	Accepted (significant)
H2	A positive relationship is present between factors minimizing E-Government project failures and RE practices for E-Government project success	Accepted (significant)

$$\begin{array}{cc}\hfill & \mathrm{RE}\mathrm{Practices}\mathrm{for}\mathrm{E}-\mathrm{Government}\mathrm{Project}\mathrm{Success}=b_0+\hfill \\ \hfill & b_1\left(\mathrm{E}-\mathrm{Government}\mathrm{Projects}\mathrm{Failure}\mathrm{Reasons}\right)+\hfill \\ \hfill & b_2\left(\mathrm{Factors}\mathrm{Minimizing}\mathrm{E}-\mathrm{Government}\mathrm{Project}\mathrm{Failures}\right)\hfill \end{array}$$

Table 8. ANOVA.

Model	Sum of Squares	df	Mean Square	F	Sig.
Regression	276.762	2	138.381	605.447	0.000
Residual	46.855	205	0.229
Total	332.616	207

displays the results of the ANOVA test. Since the significance value of the ANOVA table is less than 0.05, we can conclude that the independent variable(s) predicted the dependent variable.

Table 9 presents findings related to coefficients.The statistically significant value of E-Government project failure reasons is below 0.05. However, the negative beta coefficient implies that factors minimizing E-Government project failure reasons have an adverse effect on the RE practices for E-Government project success. This suggests that a one-unit change in E-Government project failure reasons will lead to a decrease in the RE practices for E-Government project success by 0.143 points. Similarly, the statistically significant value of factors minimizing E-Government project failures is also less than 0.05, and its positive beta coefficient suggests that a one-unit change in the factors minimizing E-Government project failures will increase RE practices for E-Government project success by 0.849 points.

Table 9. Coefficients.

Model	B	Std. Error	t	Sig.
(Constant)	1.362	0.221	6.184	0.000
Factors minimizing E-Government project failures	0.849	0.026	32.055	0.000
E-Government project fail-ure reasons	−0.143	0.051	−2.827	0.005

Table 9. Coefficients.

Model	B	Std. Error	t	Sig.
(Constant)	1.362	0.221	6.184	0.000
Factors minimizing E-Government project failures	0.849	0.026	32.055	0.000
E-Government project fail-ure reasons	−0.143	0.051	−2.827	0.005

$$\begin{array}{cc}\hfill & \mathrm{RE}\mathrm{Practices}\mathrm{for}\mathrm{E}-\mathrm{Government}\mathrm{Project}\mathrm{Success}=1.362-\hfill \\ \hfill & 0.143\left(\mathrm{E}-\mathrm{Government}\mathrm{Projects}\mathrm{Failure}\mathrm{Reasons}\right)+\hfill \\ \hfill & 0.849\left(\mathrm{Factors}\mathrm{Minimizing}\mathrm{E}-\mathrm{Government}\mathrm{Project}\mathrm{Failures}\right)\hfill \end{array}$$

5. Conclusions

In this paper, an evaluation of RE practices significant for the success of E-Government solutions was conducted. The research commenced by exploring the reasons for project failures. The variables that may reduce the failure of an E-government project were then recognized, and the most recent requirements engineering practices that could reduce the failures of E-government projects were then decided based on those reasons. This article also pinpointed the challenges of E-government projects existing in the literature, necessitating further industry studies to explore their solutions. Additionally, the effectiveness of requirements engineering practices was examined through a case study. Overall, it was concluded that there are four major reasons for E-Government project failures. These include (1) an inadequate understanding of stakeholder needs, (2) poor system design, (3) scope creep, and (4) a lack of stakeholder engagement. To address these issues, it is crucial to implement effective project planning, encourage maximum stakeholder involvement during the RE process, and utilize prototyping to gather initial user feedback, thus fostering a shared understanding of requirements among stake-holders. Moreover, E-Government projects should establish robust processes for risk management, project management, and change management. Lastly, nine requirements engineering practices implemented in E-Government solutions were identified to help overcome the challenges of E-Government project failures. A requirements engineering team should carefully analyze project stakeholders and gather feedback from different user groups. The use of agile methodology practices, such as user stories, contributes positively to eliciting comprehensive and clear requirements. Similarly, user-centered design and prototyping aid in reducing scope creep and minimizing late-breaking requirements. The introduction of automated RE and model-driven requirements engineering techniques facilitates the rapid elicitation and validation of software requirements for E-Government solutions. The analysis results indicated the factors that reduce the failure of E-Government projects and identified the causes of project failure that significantly impact the success of E-Government projects. From a practical standpoint, these findings recommend that government agencies focus on enhancing project success by addressing critical failure-contributing factors, such as insufficient system design, scope creep, etc. Augmenting stakeholder analysis capabilities, adopting agile methodologies, and implementing other essential practices also contribute to the success of E-Government projects. These practices involve effective planning, stakeholder involvement, and proficient project management.