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

Toward a risk framework in prioritizing ancillary transportation assets for management.

A growing number of transportation agencies have begun to manage selected ancillary transportation assets systematically--culverts, guardrails, pavement markings, sidewalks and curbs, street lighting, traffic signals, traffic signs, utilities and manholes, earth retaining structures, and environmental mitigation features. Given prevailing budget limitations, several agencies are interested in prioritizing these assets for inclusion in their existing management systems. This paper discusses critical elements of a framework for assessing the risks, benefits and costs of incorporating ancillary assets in existing Transportation Asset Management programs. The paper reviews some basic elements of a risk theory, examines risk applications in transportation asset management, water mains, and storm water management, and identifies the basic elements of a risk-benefit-cost framework for prioritizing ancillary assets for management. These elements can be used as a basis for developing a decision analysis framework to make a business case for the formal management of ancillary transportation assets and to prioritize them for inclusion in existing Transportation Asset Management programs. Using these elements, we have developed a risk ranking model that can be used by transportation officials to prioritize their ancillary asset classes for management. A demonstration of the model is presented in this paper to show its effectiveness. The study concludes that tracking and documentation of ancillary transportation asset failures would help agencies better understand the risks associated with failure. Tracking and documenting the failures of ancillary transportation assets would also help in identifying trends/probability of failure as well as quantifying the consequences associated with these failures. Such information could also be used to estimate risk factors to prioritize individual asset classes for inclusion in existing management systems.MSCommittee Chair: Amekudzi, Adjo; Committee Member: Hunter, Michael; Committee Member: Meyer, Michae

Maintenance Knowledge Management with Fusion of CMMS and CM

Abstract- Maintenance can be considered as an information, knowledge processing and management system. The management of knowledge resources in maintenance is a relatively new issue compared to Computerized Maintenance Management Systems (CMMS) and Condition Monitoring (CM) approaches and systems. Information Communication technologies (ICT) systems including CMMS, CM and enterprise administrative systems amongst others are effective in supplying data and in some cases information. In order to be effective the availability of high-quality knowledge, skills and expertise are needed for effective analysis and decision-making based on the supplied information and data. Information and data are not by themselves enough, knowledge, experience and skills are the key factors when maximizing the usability of the collected data and information. Thus, effective knowledge management (KM) is growing in importance, especially in advanced processes and management of advanced and expensive assets. Therefore efforts to successfully integrate maintenance knowledge management processes with accurate information from CMMSs and CM systems will be vital due to the increasing complexities of the overall systems. Low maintenance effectiveness costs money and resources since normal and stable production cannot be upheld and maintained over time, lowered maintenance effectiveness can have a substantial impact on the organizations ability to obtain stable flows of income and control costs in the overall process. Ineffective maintenance is often dependent on faulty decisions, mistakes due to lack of experience and lack of functional systems for effective information exchange [10]. Thus, access to knowledge, experience and skills resources in combination with functional collaboration structures can be regarded as vital components for a high maintenance effectiveness solution. Maintenance effectiveness depends in part on the quality, timeliness, accuracy and completeness of information related to machine degradation state, based on which decisions are made. Maintenance effectiveness, to a large extent, also depends on the quality of the knowledge of the managers and maintenance operators and the effectiveness of the internal & external collaborative environments. With emergence of intelligent sensors to measure and monitor the health state of the component and gradual implementation of ICT) in organizations, the conceptualization and implementation of E-Maintenance is turning into a reality. Unfortunately, even though knowledge management aspects are important in maintenance, the integration of KM aspects has still to find its place in E-Maintenance and in the overall information flows of larger-scale maintenance solutions. Nowadays, two main systems are implemented in most maintenance departments: Firstly, Computer Maintenance Management Systems (CMMS), the core of traditional maintenance record-keeping practices that often facilitate the usage of textual descriptions of faults and actions performed on an asset. Secondly, condition monitoring systems (CMS). Recently developed (CMS) are capable of directly monitoring asset components parameters; however, attempts to link observed CMMS events to CM sensor measurements have been limited in their approach and scalability. In this article we present one approach for addressing this challenge. We argue that understanding the requirements and constraints in conjunction - from maintenance, knowledge management and ICT perspectives - is necessary. We identify the issues that need be addressed for achieving successful integration of such disparate data types and processes (also integrating knowledge management into the “data types” and processes)

Assessing architectural evolution: A case study

This is the post-print version of the Article. The official published can be accessed from the link below - Copyright @ 2011 SpringerThis paper proposes to use a historical perspective on generic laws, principles, and guidelines, like Lehman’s software evolution laws and Martin’s design principles, in order to achieve a multi-faceted process and structural assessment of a system’s architectural evolution. We present a simple structural model with associated historical metrics and visualizations that could form part of an architect’s dashboard. We perform such an assessment for the Eclipse SDK, as a case study of a large, complex, and long-lived system for which sustained effective architectural evolution is paramount. The twofold aim of checking generic principles on a well-know system is, on the one hand, to see whether there are certain lessons that could be learned for best practice of architectural evolution, and on the other hand to get more insights about the applicability of such principles. We find that while the Eclipse SDK does follow several of the laws and principles, there are some deviations, and we discuss areas of architectural improvement and limitations of the assessment approach

Machine criticality assessment for productivity improvement: Smart maintenance decision support

Purpose\ua0The purpose of this paper is to increase productivity through smart maintenance planning by including productivity as one of the objectives of the maintenance organization. Therefore, the goals of the paper are to investigate existing machine criticality assessment and identify components of the criticality assessment tool to increase productivity.Design/methodology/approach\ua0An embedded multiple case study research design was adopted in this paper. Six different cases were chosen from six different production sites operated by three multi-national manufacturing companies. Data collection was carried out in the form of interviews, focus groups and archival records. More than one source of data was collected in each of the cases. The cases included different production layouts such as machining, assembly and foundry, which ensured data variety.Findings\ua0The main finding of the paper is a deeper understanding of how manufacturing companies assess machine criticality and plan maintenance activities. The empirical findings showed that there is a lack of trust regarding existing criticality assessment tools. As a result, necessary changes within the maintenance organizations in order to increase productivity were identified. These are technological advancements, i.e. a dynamic and data-driven approach and organizational changes, i.e. approaching with a systems perspective when performing maintenance prioritization.Originality/value\ua0Machine criticality assessment studies are rare, especially empirical research. The originality of this paper lies in the empirical research conducted on smart maintenance planning for productivity improvement. In addition, identifying the components for machine criticality assessment is equally important for research and industries to efficient planning of maintenance activities

Energy retrofit decision support model for existing educational buildings in Egypt

This thesis presents a framework for developing a local decision support model that helps decision makers in Egypt to select the best and optimal scenario to retrofit existing buildings factoring in a predefined budget. This model provides a method to manage budget against proposed retrofits taking energy efficiency and return on investment into consideration. The simulation model is developed using Designbuilder software which depends on different data categories collected from the building preliminary survey, retrofit decision scenario information from interviews with the operations team, energy bill readings, and the relevant- building- construction technical data. Twelve retrofit measures typically proposed by the Facilities and Operations team were assessed and utilized for the development of the Energy Retrofit Decision Support System (ERDSS) optimization model based on the proposed framework. Using LabVIEW software, the retrofit options are qualified, ranked and optimized according to the highest calculated savings to investments ratios where a case study has been selected from an educational institution at Cairo, Egypt. The aim of this case study is to examine the applicability of ERDSS and functionality of the simulation model in the context of the budget constraints and technical limitations. An optimum retrofit scenario was recommended by ERDSS analysis, the model prioritized the possible retrofit actions within the allocated budget and according to savings to investment ratio results for each criterion. The results show that the model delivered the expected output and provided the initially forecast plan

A hierarchical distributed control model for coordinating intelligent systems

A hierarchical distributed control (HDC) model for coordinating cooperative problem-solving among intelligent systems is described. The model was implemented using SOCIAL, an innovative object-oriented tool for integrating heterogeneous, distributed software systems. SOCIAL embeds applications in 'wrapper' objects called Agents, which supply predefined capabilities for distributed communication, control, data specification, and translation. The HDC model is realized in SOCIAL as a 'Manager'Agent that coordinates interactions among application Agents. The HDC Manager: indexes the capabilities of application Agents; routes request messages to suitable server Agents; and stores results in a commonly accessible 'Bulletin-Board'. This centralized control model is illustrated in a fault diagnosis application for launch operations support of the Space Shuttle fleet at NASA, Kennedy Space Center