No abstract

No abstract

Software-defined networking (SDN) is an agile, modern networking approach that facilitates innovations in the networking paradigm. The abstracted and centralized network operating system facilitates the network management and reduces operational expenditure (OPEX). The open nature and simplicity of the data-forwarding plane dramatically reduces capital expenditure (CAPEX) by leveraging commodity servers and switches. SDN also lends itself very well to address major cloud computing issues and complement cloud services, especially in terms of network virtualization and networking as a service (NaaS).As a new technology, SDN does involve certain security challenges, which include distributed denial of service (DDoS) threats, build and run time injected malware, insider (tenant) attacks, and security holes resulting from controller misconfigurations. These are severe threats that can cripple an entire network. It is crucial to address the SDN vulnerabilities to ensure its successful deployment in private data center networks, on cloud platforms and beyond. Some security solutions leverage the built-in features of SDN, such as its controller software component, while other solutions provide external SDN applications running above the controller. This study reviews the security solutions for the vulnerabilities of state-of-the-art SDN controllers and the available countermeasures. Furthermore, an in-depth analysis of the SDN features that support security is presented, and some unresolved research issues on SDN controllers are identified.

No abstract

Today, artificial intelligence is a key tool for turning a city into a smart city, and advances in information and communication technology (ICT) have led to the development of smart cities with many different parts. Smart Health is one of these components and is used to improve healthcare by providing services such as disease forecasting, early diagnosis, and others. There are various machine learning algorithms available now that can help with S-Health services, but which is better for disease forecasting? Gedaref State, for example, has some of Sudan's heaviest rains, and malaria and pneumonia are widespread throughout the year. Predicting future trends for these diseases has been a major focus for researchers in order for Gedaref's administration and the state's ministry of health to design effective ways to prevent and control the development of these diseases, as well as to prepare an adequate stock of medicine. As a result, it is necessary to establish a trustworthy and accurate forecasting model to aid Gedaref's government in developing economic and medical strategies for dealing with these diseases, as well as taking action on medical resource allocation. This study uses a time series dataset collected from the state's ministry of health to estimate malaria and pneumonia as common diseases in Gedaref state, Sudan, five months later. To comprehend the overall number of cases of diseases, two forecasting methodologies, namely the ARIMA and Prophet models, are applied to the disease's dataset. The performance of the ARIMA and FB-Prophet forecasting systems in predicting malaria and pneumonia diseases in Gedaref State is compared in this study. The data was collected from the state's ministry of health between January 2017 and December 2021. The results reveal that the ARIMA technique outperforms the FB-Prophet forecasting method in both malaria (RMSE: 182.8, MAE: 141.6, MAPE: 0.0057, and MASE: 0.0537) and pneumonia (RMSE: 1400.3, MAE: 1001.4, MAPE: 0.0513, and MASE: 0.9136).

phase in the Software Development Life Cycle (SDLC). The design phase follows it. Traceability is one of the core concepts in software engineering; it is used to follow updates to make consistent items. This paper aimed to cover consistency through bi-directional traceability between requirements and design phase in a semi-automatic way. The Natural Language Processing (NLP) was used to analyze the requirements text and generate a class diagram; then, the generated items can be traced back to requirements. We developed a novel process to support consistency and bi-directional traceability. To ensure our proposed process's practical applicability, we implemented a tool named as Requirements and Design Bi-directional Traceability (RDBT). RDTB receives textual format requirements, performs NLP tasks (Tokenization, Part-of-Speech Tagging, etc.), generates UML class diagram, and finally performs traceability management to ensure consistency of requirements and UML class diagram. The work evaluation reveals good results, which indicates it can be used efficiently as a guide to generate the UML class diagram semi-automatically and manage traceability.

phase in the Software Development Life Cycle (SDLC). The design phase follows it. Traceability is one of the core concepts in software engineering; it is used to follow updates to make consistent items. This paper aimed to cover consistency through bi-directional traceability between requirements and design phase in a semi-automatic way. The Natural Language Processing (NLP) was used to analyze the requirements text and generate a class diagram; then, the generated items can be traced back to requirements. We developed a novel process to support consistency and bi-directional traceability. To ensure our proposed process's practical applicability, we implemented a tool named as Requirements and Design Bi-directional Traceability (RDBT). RDTB receives textual format requirements, performs NLP tasks (Tokenization, Part-of-Speech Tagging, etc.), generates UML class diagram, and finally performs traceability management to ensure consistency of requirements and UML class diagram. The work evaluation reveals good results, which indicates it can be used efficiently as a guide to generate the UML class diagram semi-automatically and manage traceability.