7 research outputs found

    Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 2: Characterization of the IPAD system, phase 1, task 1

    Get PDF
    The aircraft design process is discussed along with the degree of participation of the various engineering disciplines considered in this feasibility study

    Continuous improvement: A bibliography with indexes, 1989-1991

    Get PDF
    This bibliography contains 198 annotated references to reports and journal articles entered into the NASA Scientific and Technical Information Data base during 1989 to 1991

    How to be FAIR with your data

    Get PDF
    This handbook was written and edited by a group of about 40 collaborators in a series of six book sprints that took place between 1 and 10 June 2021. It aims to support higher education institutions with the practical implementation of content relating to the FAIR principles in their curricula, while also aiding teaching by providing practical material, such as competence profiles, learning outcomes, lesson plans, and supporting information. It incorporates community feedback received during the public consultation which ran from 27 July to 12 September 2021

    How to be FAIR with your data

    Get PDF
    This handbook was written and edited by a group of about 40 collaborators in a series of six book sprints that took place between 1 and 10 June 2021. It aims to support higher education institutions with the practical implementation of content relating to the FAIR principles in their curricula, while also aiding teaching by providing practical material, such as competence profiles, learning outcomes, lesson plans, and supporting information. It incorporates community feedback received during the public consultation which ran from 27 July to 12 September 2021

    Understanding and Mitigating Flaky Software Test Cases

    Get PDF
    A flaky test is a test case that can pass or fail without changes to the test case code or the code under test. They are a wide-spread problem with serious consequences for developers and researchers alike. For developers, flaky tests lead to time wasted debugging spurious failures, tempting them to ignore future failures. While unreliable, flaky tests can still indicate genuine issues in the code under test, so ignoring them can lead to bugs being missed. The non-deterministic behaviour of flaky tests is also a major snag to continuous integration, where a single flaky test can fail an entire build. For researchers, flaky tests challenge the assumption that a test failure implies a bug, an assumption that many fundamental techniques in software engineering research rely upon, including test acceleration, mutation testing, and fault localisation. Despite increasing research interest in the topic, open problems remain. In particular, there has been relatively little attention paid to the views and experiences of developers, despite a considerable body of empirical work. This is essential to guide the focus of research into areas that are most likely to be beneficial to the software engineering industry. Furthermore, previous automated techniques for detecting flaky tests are typically either based on exhaustively rerunning test cases or machine learning classifiers. The prohibitive runtime of the rerunning approach and the demonstrably poor inter-project generalisability of classifiers leaves practitioners with a stark choice when it comes to automatically detecting flaky tests. In response to these challenges, I set two high-level goals for this thesis: (1) to enhance the understanding of the manifestation, causes, and impacts of flaky tests; and (2) to develop and empirically evaluate efficient automated techniques for mitigating flaky tests. In pursuit of these goals, this thesis makes five contributions: (1) a comprehensive systematic literature review of 76 published papers; (2) a literature-guided survey of 170 professional software developers; (3) a new feature set for encoding test cases in machine learning-based flaky test detection; (4) a novel approach for reducing the time cost of rerunning-based techniques for detecting flaky tests by combining them with machine learning classifiers; and (5) an automated technique that detects and classifies existing flaky tests in a project and produces reusable project-specific machine learning classifiers able to provide fast and accurate predictions for future test cases in that project

    A comparative analysis of supply chain management practices by Boeing and Airbus : long-term strategic implications

    Get PDF
    Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Civil and Environmental Engineering, February 2007.Includes bibliographical references (p. 127-131).The goal of this research is to develop an improved understanding of supply chain management strategies and practices being pursued by Boeing and Airbus in the 787 Dreamliner and the A380 Navigator programs, respectively, and to identify their long-term strategic implications for supply chain management in the future. The research takes as its point of departure a review and synthesis of supply chain management principles and practices, with particular emphasis on lean supply chain management concepts. Guided by this review, the research focuses on the common set of suppliers supporting both programs and employs a questionnaire survey, followed by telephone interviews with representatives of selected suppliers. The research also makes extensive use of the open source information on both companies, on both programs and on the common suppliers.(cont.) A major finding is that Boeing's new supply chain model in the 787 program represents a significant break with past practices in the aerospace industry, allowing major partnering suppliers an unprecedented role in terms of design, development, production and after-market support, where they are integrated early in the concept development stage and are incentivized to collaborate with Boeing, as well as among themselves, as risk-sharing partners with deep responsibility for system integration, involving detailed interface control at the system and subsystem levels. Airbus, as well, is found to rely heavily on its major suppliers in connection with the A380 program, but acting as the primary system integrator in the more traditional mode and exercising much greater control of all design interfaces. Also, both Boeing and Airbus have been outsourcing more and more activities to suppliers located in non-traditional regions, such as Eastern Europe and the Asia-Pacific region. Finally, aerospace manufacturers, in general, are aggressively adopting information technologies (e.g., EDI, PLM, 3-D Digital Model, RFID) to facilitate greater data sharing and communications with their partners and lower-tier suppliers dispersed in many geographical regions, as part of a broader trend involving more collaborative supplier relationships reaching down to the subtier level.by Tzu-Ching Horng.S.M

    How to be FAIR With Your Data: a Teaching and Training Handbook for Higher Education Institutions

    Get PDF
    This handbook was written and edited by a group of about 40 collaborators in a series of six book sprints that took place between 1 and 10 June 2021. It aims to support higher education institutions with the practical implementation of content relating to the FAIR principles in their curricula, while also aiding teaching by providing practical material, such as competence profiles, learning outcomes, lesson plans, and supporting information. It incorporates community feedback received during the public consultation which ran from 27 July to 12 September 2021
    corecore