The role of software tools in risk assessment got froman accident and emissions of hazardous materials

The development of atmospheric dispersion models is an important step in the process of predicting, assessing and managing the risk of potential disasters. They are of particular importance in defining and analyzing risk zones in order to prevent endangering a large number of people, property, the environment and natural resources. Today, making a model is almost unthinkable without the use of appropriate software solutions. Numerous software tools for atmospheric dispersion modeling have been developed, the primary role of which is risk assessment, which includes the analysis of accident and emission pollution models used to simulate the transport and diffusion of various pollutants. As many industrial and development projects potentially cause unwanted consequences in the environment, by applying such tools the harmful consequences could be minimized. The development of sensor and computer technology has enabled the development of complex algorithms for the development of models that can be executed in real time, which enables their active role in managing the process of responding to an incident that has occurred. This paper presents the possibilities of modelling software tools through the example of the impact of chemicals on the environment in the case of emissions of hazardous gases due to an accident. The characteristics of the mathematical model and the simulation scenario made in the Aloha software tool are presented

A Survey on Usage and Diffusion of Project Risk Management Techniques and Software Tools in the Construction Industry

The area of Project Risk Management (PRM) has been extensively researched, and the utilization of various tools and techniques for managing risk in several industries has been sufficiently reported. Formal and systematic PRM practices have been made available for the construction industry. Based on such body of knowledge, this paper tries to find out the global picture of PRM practices and approaches with the help of a survey to look into the usage of PRM techniques and diffusion of software tools, their level of maturity, and their usefulness in the construction sector. Results show that, despite existing techniques and tools, their usage is limited: software tools are used only by a minority of respondents and their cost is one of the largest hurdles in adoption. Finally, the paper provides some important guidelines for future research regarding quantitative risk analysis techniques and suggestions for PRM software tools development and improvemen

Addressing challenges to teach traditional and agile project management in academia

In order to prepare students for a professional IT career, most universities attempt to provide a current educational curriculum in the Project Management (PM) area to their students. This is usually based on the most promising methodologies used by the software industry. As instructors, we need to balance traditional methodologies focused on proven project planning and control processes leveraging widely accepted methods and tools along with the newer agile methodologies. Such new frameworks emphasize that software delivery should be done in a flexible and iterative manner and with significant collaboration with product owners and customers. In our experience agile methodologies have witnessed an exponential growth in many diverse software organizations, and the various agile PM tools and techniques will continue to see an increase in adoption in the software development sector. Reflecting on these changes, there is a critical need to accommodate best practices and current methodologies in our courses that deliver Project Management content. In this paper we analyse two of the most widely used methodologies for traditional and agile software development – the widely used ISO/PMBOK standard provided by the Project Management Institute and the well-accepted Scrum framework. We discuss how to overcome curriculum challenges and deliver a quality undergraduate PM course for a Computer Science and Information systems curricula. Based on our teaching experience in Europe and North America, we present a comprehensive comparison of the two approaches. Our research covers the main concepts, processes, and roles associated with the two PM frameworks and recommended learning outcomes. The paper should be of value to instructors who are keen to see their computing students graduate with a sound understanding of current PM methodologies and who can deliver real-world software products.Accepted manuscrip

Technical Debt Prioritization: State of the Art. A Systematic Literature Review

Background. Software companies need to manage and refactor Technical Debt issues. Therefore, it is necessary to understand if and when refactoring Technical Debt should be prioritized with respect to developing features or fixing bugs. Objective. The goal of this study is to investigate the existing body of knowledge in software engineering to understand what Technical Debt prioritization approaches have been proposed in research and industry. Method. We conducted a Systematic Literature Review among 384 unique papers published until 2018, following a consolidated methodology applied in Software Engineering. We included 38 primary studies. Results. Different approaches have been proposed for Technical Debt prioritization, all having different goals and optimizing on different criteria. The proposed measures capture only a small part of the plethora of factors used to prioritize Technical Debt qualitatively in practice. We report an impact map of such factors. However, there is a lack of empirical and validated set of tools. Conclusion. We observed that technical Debt prioritization research is preliminary and there is no consensus on what are the important factors and how to measure them. Consequently, we cannot consider current research conclusive and in this paper, we outline different directions for necessary future investigations

Planning effort as an effective risk management tool

In project management, high levels of risk are considered to be a significant obstacle for project success. This paper investigates whether improving the project plan can lead to improved success for high-risk projects. A quality of planning index was designed to explore how the presence of high risk affects the quality of planning and project success. The index includes managerial aspects such as costs, human resources, procurement and quality, as well as organizational support aspects based on organization maturity models. In a field study based on data collected from 202 project managers regarding their most recent projects, it was found that the levels of risk at the beginning of projects has no effect on their final success. Drilling down to find an explanation for this surprising phenomenon, we found that in the presence of high risk, project managers significantly improve their project plans. Hence, in high-risk projects, better project plans improve all four dimensions of project success: schedule overrun, cost overrun, technical performance and customer satisfaction. However, in low-risk projects, better project plans did not contribute to reducing schedule or cost overruns. In other words, while endless risk management tools are developed, we found that improving the project plan is a more effective managerial tool in dealing with high-risk projects. Finally, the paper presents the most common planning tools currently being used in high-risk projects

Risk Profiles in Individual Software Development and Packaged Software Implementation Projects: A Delphi Study at a German-Based Financial Services Company

The aim of this paper is to compare risk profiles of individual software development (ISD) and packaged software implementation (PSI) projects. While researchers have investigated risks in either PSI projects or ISD projects, an integrated perspective on how the risk profiles of these two types of information system (IS) projects differ is missing. To explore these differences, this work conducted a Delphi study at a German-based financial services company. The results suggest that: First, ISD projects seem to be more heterogeneous and face a larger variety of risks than the more straightforward PSI projects. Second, ISD projects seem to be particularly prone to risks related to sponsorship, requirements, and project organization. Third, PSI projects tend to be predominantly subject to risks related to technology, project planning, and project completion. Finally, in contrast to available lists of risks in IS projects and irrespective of the project type, the paper found a surprisingly high prominence of technology and testing-related risks

Bringing Global Sourcing into the Classroom: Experiential Learning via Software Development Project

Global sourcing of software development has imposed new skill requirements on Information Technology (IT) personnel. In the U.S., this has resulted in a paradigm shift from technical to softer skills such as communications and virtual team management. Higher education institutions must, consequently, initiate innovative curriculum transformations to better prepare students for these emerging workforce needs. This paper describes one such venture between Marquette University (MU), U.S.A. and Management Development Institute (MDI), India, wherein IT students at MU collaborated with Management Information Systems (MIS) students at MDI on an offshore software development project. The class environment replicated an offshore client/vendor relationship in a fully virtual setting while integrating communications and virtual team management with traditional IT project management principles. Course measures indicated that students benefited from this project, gained first-hand experience in the process of software offshoring, and learned skills critical for conduct of global business. For faculty considering such initiatives, we describe the design and administration of this class over two semesters, lessons learned from our engagement, and factors critical to success of such initiatives and those detrimental to their sustenance

Rationale Management Challenges in Requirements Engineering

Rationale and rationale management have been playing an increasingly prominent role in software system development mainly due to the knowledge demand during system evaluation, maintenance, and evolution, especially for large and complex systems. The rationale management for requirements engineering, as a commencing and critical phase in software development life cycle, is still under-exploited. In this paper, we first survey briefly the state-of-the-art on rationale employment and applications in requirements engineering. Secondly, we identify the challenges in integrating rationale management in requirements engineering activities in order to promote further investigations and define a research agenda on rationale management in requirements engineering.