Making sense of engineering design review activities

Author(s):  
Gregory Huet ◽  
Stephen J. Culley ◽  
Christopher A. McMahon ◽  
ClÉment Fortin

AbstractEngineering design reviews, which take place at predetermined phases of the product development process, are fundamental elements for the evaluation and control of engineering activities. These meetings are also acknowledged as unique opportunities for all the parties involved to share information about the product and related engineering processes. For product development teams, the knowledge generated during a design review is not as secondary as it may seem; key design decisions, design experiences, and associated rationale are frequently made explicit. Useful work has been carried out on the design review process itself, but little work has been undertaken about the detailed content of the meeting activity; it is argued that understanding the transactions that take place during a meeting is critical to building an effective knowledge-oriented recording strategy. To this effect, an extensive research program based on case studies in the aerospace engineering domain has been carried out. The work reported in this paper focuses on a set of tools and methods developed to characterize and analyze in depth the transactions observed during a number of case studies. The first methodology developed, the transcript coding scheme, uses an intelligent segmentation of meeting discourse transcriptions. The second approach, which bypasses the time consuming transcribing operation, is based on a meeting capture template developed to enable a meeting observer to record the transactions as the meeting takes place. A third method, the information mapping technique, has also been developed to interpret the case study data in terms of decisions, actions, rationale, and lessons learned, effectively generating qualitative measures of the information lost in the formal records of design reviews. Overall, the results generated by the set of tools presented in this paper have fostered a practical strategy for the knowledge intensive capture of the contents of design reviews. The concluding remarks also discuss possible enhancements to the meeting analysis tools presented in this paper and future work aimed at the development of a computer supported capture software for design reviews.

Author(s):  
Oliver Tegel

Abstract A cradle for systematic approaches to product development processes, the Institute for Engineering Design at Technical University Berlin, Germany was one of the first trying to achieve a continuous and flexible computer support throughout the whole product development process. The history of the development of concepts and implementations is presented in this paper, and the major lessons learned during 15 years of research are presented.


Author(s):  
Sourobh Ghosh ◽  
Warren Seering

Since a series of academic case studies had revealed Toyota’s unique product development practices to the world, a flurry of research has been conducted into set-based design, also known as set-based concurrent engineering. In this paper, we review work related to set-based design across academic communities in efforts to find common themes and influences. After a review of this literature, we inductively arrive at two Principles of Set-Based Thinking: considering sets of distinct alternatives concurrently and delaying convergent decision making. These Principles allow us to articulate a working description of set-based design. We then examine these two Principles at work in a case example of a common theoretical construct in design.


1997 ◽  
Vol 13 (4) ◽  
pp. 379 ◽  
Author(s):  
S. Jenkins ◽  
S. Forbes ◽  
T.S. Durrani ◽  
S.K. Banerjee

Author(s):  
Amanda Prail ◽  
Michael J. Kahn

A Usability Inspection is a specific formal design review methodology to identify and prioritize potential usability defects in a given design. More formal than heuristic evaluations (Nielsen – Molich, 1990), less complex than cognitive walkthroughs (Polson et al., 1992), the methodology is a task-oriented review process that started as an adaptation of the Kepner-Tregoe Potential Problem Analysis and further evolved to heavily leverage a formal generic inspections methodology in use at Hewlett-Packard. This evolution by adaptation of standard generic methods already understood by engineers in Hewlett-Packard has been a conscious design strategy in the hope that this would ease the adoption process. The key question for a practitioner in the field is - does the method provide sufficient return on investment to be worth including in a product development process. There is some evidence that design review methods carried out by non-Human Factors engineers do successfully find defects (Nielsen – Molich, 1990, Lewis et al., 1990, Jeffries et al., 1991). Bailey (1992) raised the question as to whether heuristic evaluations may be counterproductive in that they actually may create work rather than save it. To date, the research has largely focussed on the contribution a method may provide to a specific product or interface. This paper argues the case for a wider definition and understanding of potential utility or contribution from a Human Factors method and further claims that usability inspections not only provide a sufficient payback to warrant their inclusion in a product development lifecycle but also provide the seeds of organization change that are needed to make usability engineering a reality.


Author(s):  
Benjamin Gerschütz ◽  
Marius Fechter ◽  
Benjamin Schleich ◽  
Sandro Wartzack

AbstractThe amount of new virtual reality input and output devices being developed is enormous. Those peripherals offer novel opportunities and possibilities in the industrial context, especially in the product development process. Nevertheless, virtual reality has to face several problems, counteracting reliable use of the technology, especially in ergonomic and aesthetic assessments. In particular, the discrepancies in perception between the real world and virtual reality are of great importance.Therefore, we discuss these most important issues of current virtual reality technology and highlight approaches to solve them. First, we illustrate the use cases of VR in the product development process. In addition, we show which hardware is currently available for professional use and which issues exist with regard to visual perception and interaction. Derived from the depiction of a perfect virtual reality, we define the requirements to address visual perception and interaction. Subsequently we discuss approaches to solve the issues regarding visual perception and evaluate their suitability to enhance the use of virtual reality technology in engineering design.


Author(s):  
Håkan Petersson ◽  
Damien Motte ◽  
Martin Eriksson ◽  
Robert Bjärnemo

When developing products, engineering designers often face the problem that their candidate for a technical solution, ranging from a concept to a detailed design, needs to be analyzed by a design analyst before it is approved or rejected and the engineering designer can continue his/her activities within the product development process. If engineering designers have to send every solution candidate to a design analyst, a lot of time and money is lost. To avoid this, some Swedish companies have started to allow their engineering designers to use the analysis capabilities imbedded in modern CAD/CAE software. In the literature on product development and on computer based design analysis (CBDA) both processes are fairly well described. However, this cannot be said about the interaction between the two processes. This is a growing issue as it represents core knowledge for developing efficient and effective integration concepts, which in turn can be developed into likewise efficient and effective approaches on how to assist the engineering designer to perform parts of the CBDA process on his/her own. Note that when we refer to CBDA here, this is confined to the use of FEM in the development of products, primarily based on working principles originating from the area of Mechanical Engineering. Since we have been working on a process model for the integration between engineering design and design analysis, this has inspired us to utilize findings from these efforts to propose a conceptual model for a design analysis process driven by the engineering designer to be integrated into the product development process. The proposed design analysis process model is based on the use of predefined analysis methods or templates. Templates are also utilized for QA (Quality Assurance) and monitoring of the analysis activities. Responsible for the development of the analysis methods and the templates are expert design analysts, who develop these tools within a technology development process. Before allowing the engineering designers access to them, these tools need to be approved by relevant bodies within the industrial enterprise and/or by external sources such as those responsible for certification and risk management. In this paper we present the development of the proposed integrated design analysis process model and an industrial case study, which incorporates a non-linear design analysis activity, utilizing the FEM-program Abaqus within the CAD-software Catia V5 and its imbedded optimization module.


2002 ◽  
Vol 9 (5/6) ◽  
pp. 419-432 ◽  
Author(s):  
CARLOS T. FORMOSO ◽  
PATRICIA TZORTZOPOULOS ◽  
RENATA LIEDTKE

The performance of the product development process has a critical influence on the efficiency and duration of building projects, as well as on the quality of the final product. Despite its importance, relatively little attention has been given to the management of this process, if compared with production. The main objective of this paper is to present some results of a research project which aimed to devise a general model for managing the product development process in small sized companies involved in the development and construction of residential and commercial buildings. This model consists of a template for the product development process, which can be used by different companies as a basis to devise their own models for managing individual projects. The development of the model was based on case studies carried out in two companies from the south of Brazil and also on a benchmarking study.


Sign in / Sign up

Export Citation Format

Share Document