Analysis about benefits of software-defined wide area network: a new alternative for WAN connectivity

This article is based on conducting research to analyze the benefits of emerging trends in communications and networking technology, such as software-defined wide area networks. Using Waterfall as a methodology, the main objective is to carry out a technical comparison at the design and configuration level, creating a virtual environment that simulates traditional and SDWAN (Software-Defined Wide Area Network) infrastructures. The results obtained verify that the benefits of SDWAN maintain business continuity, anticipate situations in which the infrastructure can act intelligently, optimize connectiv-ity while maintaining security, and provide improvements in the management of the entire infrastructure. People will be able to see the results obtained between both technologies and validate the benefits that SDWAN offers .Campus Lima Centr

Description and Experience of the Clinical Testbeds

This deliverable describes the up-to-date technical environment at three clinical testbed demonstrator sites of the 6WINIT Project, including the adapted clinical applications, project components and network transition technologies in use at these sites after 18 months of the Project. It also provides an interim description of early experiences with deployment and usage of these applications, components and technologies, and their clinical service impact

Development of HSE MS tool base on Shell Malaysia Trading oil depot operations

HSEis a compulsory aspect to be considered in any industry and even process for that matter. Various accidents and disasters have occurred due to negligence of HSE aspect. Few of the major ones are the Alpha Piper incident, Union Charbide Bhopal incident and the Longford incident HSE MS is the synergy of health, safety and environment aspect of industry. The implementation of HSE MS as structured set of controls for managing HSE; will ensure and to demonstrate the HSE objectives set in the policy are met. The purpose of this report is to represent the final output of study on Development of HSEMS tool base on Shell Malaysia Trading Bagan Luar oil depot operations. This HSE MS tool can also be define as information management model for HSE data. This paper presents the project focusing on the problem statement and the objective as well as the scope of study. It also covers the analytical review ofwritten materials HSE MS and the methodology that will be used in completing this project. The result and discussion of this project is also touched in this report. There is also an insight of conclusion and recommendations for this project

Early insights from statistical and mathematical modeling of key epidemiologic parameters of COVID-19

We report key epidemiologic parameter estimates for coronavirus disease identified in peer-reviewed publications, preprint articles, and online reports. Range estimates for incubation period were 1.8–6.9 days, serial interval 4.0–7.5 days, and doubling time 2.3–7.4 days. The effective reproductive number varied widely, with reductions attributable to interventions. Case burden and infection fatality ratios increased with patient age. Implementation of combined interventions could reduce cases and delay epidemic peak up to 1 month. These parameters for transmission, disease severity, and intervention effectiveness are critical for guiding policy decisions. Estimates will likely change as new information becomes available

Emergency Response Planning Prototype Based on Process Safety Management for Manufacturing Industry

The US Occupational Safety and Health Administration developed guidelines and regulations for an emergency action plan. However due to complex production processes involved in the manufacturing industry emergency planning is to be managed in a more systematic way. In order to enable planners to engage in a more systematic way of planning this research aim's to design a framework and prototype an emergency preparedness planning tool according to OSHA's guidelines and regulations. The framework is prototyped into a planning tool using Microsoft Excel, Microsoft Access and Microsoft Visio. This project work would be expected to contribute in assisting emergency planners in the manufacturing industry design better emergency plans based on OSHA's requirements. The tool is to assist planners by introducing information of the regulations in a stepwise manner for decision making compared to referring to guidelines which are arranged in categories. This concept for such a planning tool is relatively new for the manufacturing industry as OSHA's available tool doesn't use stepwise planning and is made for small businesses

Revision of the Computer Information Systems and Computer Science majors

Based on recent changes in our accreditation agency ABET’s criteria, the implementation of the SUNY Transfer Path program, and results from our internal program to assess our Student Learning Outcomes, the department needs to revise several aspects of all of our programs

Managing Technical Debt in Agile Software Development Projects

One of the key reasons that agile software development methods have gained popularity in recent years is because they enable organizations to produce software quickly to meet the needs of various stakeholders. However, this focus on delivering software quickly often encourages practitioners to incur technical debt – design or implementation constructs that are expedient in the short term but set up a technical context that can make future changes more costly or impossible. Worldwide, technical debt is estimated to be a trillion-dollar problem. This has prompted significant interest from both researchers and practitioners. In this dissertation, I present two essays that advance our knowledge of the causes of technical debt in agile software development projects and that offer potential solutions to manage the most important of these causes of technical debt. In my first essay, I conduct a ranking-type Delphi study of information technology (IT) project managers and software developers to identify and prioritize the most important causes of technical debt in agile software development projects. The findings from this study provide a verified list of 55 causes of technical debt in agile software development projects and offer 13 potential techniques to manage the causes of technical debt that were most important to the IT project managers and software developers in this study. In my second essay, I conduct a randomized experiment to examine the impact of software developers’ construal level, a cognitive process, on the unintentional accumulation of technical debt in software development projects. The findings from this experiment suggest that software developers at a high construal level are more likely to focus on developing the architecture or design than software developers at a low construal level. Collectively, the findings from these two essays deepen our understanding of the intentional and unintentional causes of technical debt in agile software development projects. Further, the findings offer potential techniques to manage the most important causes of technical debt for IT project managers and software developers