Design Performance Measurement in the Construction Sector: A Pilot Study

This paper examines the role and deployment of design performance measurements (DPMs) in the construction industry, focusing on the consulting engineering sector, the design 'heart' of construction. Compared with manufacturing, there has been very little research on the use of DPMs in construction, and firms often struggle to find appropriate performance indicators. Using results from structured questionnaires, the paper shows that the few DPMs which do exist focus mainly on cost. Other measures are needed to address quality, innovative performance and client satisfaction. In contrast to manufacturing, DPMs in construction also need to address the project-based, multi-firm and non-routine nature of construction design, as well as the separation of design from manufacturing, build and operation. Interviews and workshops with industrialists were used to identify recent DPM practices in construction and combine these with lessons from other sectors. The resulting DPM tools provide guidance on how to: (a) integrate design into wider business processes in construction; (b) identify key design indicators, at both project and firm level; and (c) use DPMs to provide a balanced scorecard for design performance.performance indicators, design integration, design indicators, construction industry

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

CESEC Chair – Training Embedded System Architects for the Critical Systems Domain

Increasing complexity and interactions across scientific and tech- nological domains in the engineering of critical systems calls for new pedagogical approach. In this paper, we introduce the CESEC teaching chair. This chair aims at supporting new integrative ap- proach for the initial training of engineer and master curriculum to three engineering school in Toulouse: ISAE, INSA Toulouse and INP ENSEEIHT. It is supported by the EADS Corporate Foundation. In this paper, we highlight the rationale for this chair: need for sys- tem architect with strong foundations on technical domains appli- cable to the aerospace industry. We then introduce the ideal profile for this architect and the various pedagogical approaches imple- mented to reach this objective

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results: The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.Peer ReviewedPostprint (published version

Preliminary Results in a Multi-site Empirical Study on Cross-organizational ERP Size and Effort Estimation

This paper reports on initial findings in an empirical study carried out with representatives of two ERP vendors, six ERP adopting organizations, four ERP implementation consulting companies, and two ERP research and advisory services firms. Our study’s goal was to gain understanding of the state-of-the practice in size and effort estimation of cross-organizational ERP projects. Based on key size and effort estimation challenges identified in a previously published literature survey, we explored some difficulties, fallacies and pitfalls these organizations face. We focused on collecting empirical evidence from the participating ERP market players to assess specific facts about the state-of-the-art ERP size and effort estimation practices. Our study adopted a qualitative research method based on an asynchronous online focus group

Total Cost of Ownership Model: A Framework for Hanover

Financial pressures are forcing companies to focus on calculating Total Cost of Ownership (TCO) of Information Technology (IT) assets and their business value. Hanover Insurance had attempted to develop a TCO model in the past. This model was not implemented due to a limited set of defined metrics. This project proposes a TCO model that includes a larger set of metrics, which allows the company to calculate the costs derived by IT assets and the business value these assets generate

Implementing product platforms in the global enterprise : Lessons from an LED industry leader

Peer reviewedPostprin

Visualizing and Measuring Enterprise Application Architecture: An Exploratory Telecom Case

We test a method for visualizing and measuring enterprise application architectures. The method was designed and previously used to reveal the hidden internal architectural structure of software applications. The focus of this paper is to test if it can also uncover new facts about the applications and their relationships in an enterprise architecture, i.e., if the method can reveal the hidden external structure between software applications. Our test uses data from a large international telecom company. In total, we analyzed 103 applications and 243 dependencies. Results show that the enterprise application structure can be classified as a core-periphery architecture with a propagation cost of 25%, core size of 34%, and architecture flow through of 64%. These findings suggest that the method could be effective in uncovering the hidden structure of an enterprise application architecture