Information integration is considered a source of competitive advantage in the capital projects industry. While it has been broadly implemented, many organizations appear to have achieved only limited benefits from their efforts. This dissertation investigates the complementarity relationship between information technology (IT) use and project execution processes and practices. It asserts that rather than directly improving an organization’s competitive advantage, IT serves instead as a mode to improve existing processes and practices which in turn serve to improve the bottom line. Building from this foundation, the dissertation proceeds to expand its findings to document mechanisms by which various resources influence the complementarity relationship. Topics within this dissertation are investigated with both quantitative and qualitative approaches. Using capital projects data, evidence of complementarity is established quantitatively between general use of IT and best practices. The benefits of complementarity in terms of cost, schedule, and rework project performance measures are documented. Data analyses show that more use of IT is associated with more use of best practice; and, projects that intensively implement IT and best practice tend to show superior project performance. Furthermore, by investigating the use of a specific technology, this dissertation presents a thorough statistical analysis showing that IT use affects the use of practices, which together support improved project performance. Next, this dissertation lists organization resources that may affect complementarity. Using sixteen actual information integration cases, the major resources consistently affecting complementarity are identified. Illustrations of seven case studies present how the resources are managed. The case studies are also used when discussing the interaction of IT use and processes generating complementarity. The primary contribution of this research is to provide a quantitative evidence of IT’s indirect impact on construction project performance via practices. A broad discussion citing the range of resources affecting the complementarity and identifying the major ones in the capital projects industry is another contribution of this research. / text

La presente tesis de investigación se orientó en la aplicación de las Buenas Prácticas de Ingeniería, como herramienta para reducir las mermas dentro de las líneas de producción en el procesamiento de vidrios laminados de la Corporación Miyasato. Para ello se analizaron los síntomas y causas que ocurren dentro de los procesos y se determinó la problemática principal. Se utilizó la metodología de las 5S para mejorar la percepción de la calidad de los trabajadores, se organizaron espacios y se fomentaron programas de capacitación del recurso humano. Como resultado final se obtuvo una reducción de las mermas hasta en 30.8%. This thesis research was aimed at implementing the Good Engineering Practices as a tool to reduce waste in the production lines in the processing of laminated glasses Miyasato Corporation. To do the symptoms and causes occurring within processes and it determined the main problem analyzed. 5S methodology was used to improve the perception of the quality of workers, space programs were organized and training of human resources is encouraged. As a final result in reduced shrinkage was obtained. The final result was the reduced of waste. Was obtained up to 30.8%.

Both distributed work and DevOps are on an upward trend. There is a slight resemblance between the problems that DevOps is trying to find answers to, the solutions, and the common problems that geographically distributed work faces. Mainly, they are related to isolated environments that have difficulties in mutual understanding and communication, collaboration. All this leads to inefficiencies and costs that affect the overall efficiency of companies. This report identifies how DevOps engineering principles and implementations provide solutions to common problems in globally distributed work environments. It uses a literature systematic literature search and review to extract the recent and relevant academic data in the scope of the two research questions. Then, a proof-of-concept is implemented for DevOps, which confirms the literature. In parallel, a survey addressed to Swedish companies provides subject-related data from the professional environment, which largely supports the literature and brings extra knowledge. All of this is considered in data analysis and formulation of conclusions, showing DevOps features that can improve and support work in globally distributed environments and outlining the importance of the tailored organizational culture for the modern need of large-scale distributed work.

In 2013, a new set of science standards was introduced for K-12 science education, called the Next Generation Science Standards (NGSS), which focused on three dimensions of science learning that work together: disciplinary core ideas, crosscutting concepts, and science and engineering practices. These standards are novel in their emphasis on students needing more than only content knowledge to learn science and engineering. The NGSS science and engineering practices (SEPs) stress the importance of students engaging in the authentic practices of scientists and engineers to help them think like a scientist, practice science themselves, and overcome the misconception that science is a collection of isolated facts (NRC, 2012a). These SEPs include: asking questions and defining problems, developing and using models, planning and carrying out investigations, analyzing and interpreting data, using mathematics and computational thinking, constructing explanations and designing solutions, engaging in argument from evidence, and obtaining, evaluating, and communicating information. We performed a qualitative study to determine the conceptions of undergraduate students, the majority of whom were enrolled in STEM majors, about the SEPs. With a theoretical framework of phenomenography guiding our study's design, we conducted deep, open-ended interviews with 59 undergraduate students. The analysis consisted of transcribing interviews, coding transcriptions, writing descriptions of the codes to identify a limited number of distinct categories that describe how students viewed individual SEPs, and analyzing relationships among these categories to create outcome spaces for the ways students viewed the SEPs. In the current dissertation, we present the students' specific conceptions of each of the SEPs. Although the students had a better understanding of some of the SEPs than others (e.g., they understood planning and carrying out investigations and using mathematics and computational thinking best), we found that undergraduates did not have a high level of understanding of any SEP. This is similar to conceptions of undergraduates in the literature, which mostly consisted of preservice teachers. The undergraduates in this study conflated many of the SEPs, misinterpreted SEPs based on the everyday meaning of terms in the practices (i.e., they discussed an everyday meaning of words like "questions" instead of focusing on the unique meaning of "questions" in a scientific context), and perceived that the structured learning activities in which they engage in their current coursework limit their abilities to engage in the SEPs. These results suggest that STEM students need more opportunities to authentically engage in the SEPs in open-ended environments, coupled with explicit instruction that emphasizes the difference between everyday usages of words in the SEPs and their scientific meanings.

Context: Companies adopt many software reuse practices, such as software product line, reuse verbatim, and systematic reuse, to improve their internal software development and maximize the benefits. Contemporary software engineering (SE) practices, such as microservices and InnerSource, influence internal software reuse. Objective: In this thesis, we aim to improve internal software reuse in the context of contemporary SE practices. To do that, we want to 1) understand the state-of-the-art and the state-of-the-practice of software reuse costs and benefits and the challenges that companies are currently facing and 2) identify interventions to improve internal software reuse.  Methods: We conducted a systematic literature review to understand the state-of-the-art of software reuse costs and benefits. We performed two exploratory case studies to understand the state-of-the-practice of software reuse costs and benefits, challenges, and improvement areas in the context of contemporary SE practices.  We performed another follow-up improving case study to investigate the medium-sized case company's readiness of adopting InnerSource for software reuse. Results: Existing literature reported more software reuse benefits than costs. The most reported software reuse benefits are better product quality and improved productivity. Verbatim reuse and systematic reuse result in more reuse benefits. Most of the included primary studies are of moderate quality, with only four having high quality. Practitioners think that software reuse costs in developing reusable assets will be paid off when developers start to reuse them. Challenges in software reuse in the context of contemporary SE practices differ between medium-sized and large-sized companies. Both of the companies perceive that InnerSource can help improve internal software reuse. Asking practitioners about both current and desired InnerSource reuse status helps identify the needed InnerSource improvements, thus helping companies succeed in adopting InnerSource for reuse.   Conclusion: Both existing literature and our two case studies investigating software reuse in the context of contemporary SE practices showed that software reuse improves quality and productivity and has costs in developing and integrating reusable assets. However, the overall benefits outweigh the costs. Both case companies faced challenges in improving their internal reuse, where the most common challenges were about developing and maintaining reusable assets. The results showed that InnerSource helps develop and maintain reusable assets and further improves internal software reuse. / <p>Chapters 2 and 4 are papers submitted to journals and therefore removed from the fulltext file.</p>

The purpose of this study was to characterize a methodological framework for preparing science educators to implement design-based engineering practices to intentionally teach targeted science content. Using a modified Delphi the study looked to answer the following research questions (RQs): RQ1: How should teacher educators prepare K-12 pre-service science teachers to define engineering problems as one of eight NGSS practices all students should acquire through science education?, RQ2: How should teacher educators prepare K-12 pre-service science teachers to design engineering solutions as one of eight NGSS practices all students should acquire through science education? and , RQ3: How should teacher educators prepare K-12 pre-service science teachers to intentionally teach targeted science content using their newly acquired abilities to define engineering problems and design engineering solutions? During Round 1 a panel of 20 (8 science and 12 technology) education experts responded to 5 open-ended questions that focused on identifying the competencies and instructional strategies used to prepare K-12 pre-service science teachers to intently teach science using engineering design. Each question resulted in identifying approximately 50 themes per question. These themes were then used to construct the Round 2 Questionnaire. During Round 2 panelists reached agreement on 283 characteristics of a framework for preparing future science educators. In Round 3, panelists were sent 87 contested Round 2 items. Results of the Round 3 data analysis indicted an additional 31 framework characteristics. The results of this study identify the essential characteristics of a methodological framework that can serve to prepare science educators on the implementation of design-based engineering practices that intentionally teach targeted science content. / Ph. D.

Object-oriented languages have made a shift towards incorporating functional concepts such as lambdas. Lambdas are anonymous functions that can be used within the scope of other functions. In C++ lambdas are considered difficult to use for inexperienced developers. This implies that there may be problems with lambdas in C++. However, studies about lambdas in C++ repositories are scarce, compared to other object-oriented languages such as Java. This study aims to address a knowledge gap regarding how lambdas are used by developers in C++ repositories. Furthermore, examine how developer experience and software engineering practices, such as unit testing and in-code documentation, correlates with the inclusion of lambdas. To achieve this we create a set of tools that statically analyse repositories to gather results. This study gained insight into the number of repositories utilising lambdas, their usage areas, and documentation but also how these findings compare to similar studies’ results in Java. Further, it is shown that unit testing and developer experience correlates with the usage of lambdas. / Objektorienterade språk har gjort en förskjutning mot att integrera funktionella begrepp som lambdas. Lambdas är anonyma funktioner som kan användas inom ramen för andra funktioner. I C ++ anses lambdas vara svåra att använda för oerfarna utvecklare. Detta innebär att det kan vara problem med lambdas i C ++. Emellertid är studier på lambdas i C ++ repositorier mindre vanliga jämfört med andra objektorienterade språk som Java. Denna studie syftar till att ta itu med ett kunskapsgap beträffande hur lambdas används av utvecklare i C++ repositorier. Dessutom undersöks hur utvecklarvanor och sedvänjor i programvaruutveckling, till exempel enhetstestning och dokumentation, korrelerar med inkluderingen av lambdas. För att uppnå detta skapar vi en uppsättning verktyg som statiskt analyserar repositorier för att samla resultat. Denna studie fick inblick i antalet repositorier som använder lambdas, deras användningsområden och dokumentation men också hur dessa resultat jämför sig med liknande studieresultat i Java. Vidare har det visats att enhetstestning och utvecklaren erfarenhet korrelerar med användningen av lambdas.