0
Research Papers: Design Theory and Methodology

Mapping Software Augments Engineering Design Thinking

[+] Author and Article Information
Nathan Eng

Department of Mechanical Engineering,
Imperial College London,
Exhibition Road, South Kensington Campus,
London SW7 2AZ, UK
e-mail: pointlinebox@gmail.com

Marco Aurisicchio

Dyson School of Design Engineering,
Imperial College London,
Exhibition Road, South Kensington Campus,
London SW7 2AZ, UK
e-mail: m.aurisicchio@imperial.ac.uk

Rob Bracewell

Rolls-Royce plc.,
7 Thomas Court,
Derby DE1 1AJ, UK
e-mail: rob.bracewell@gmail.com

1Corresponding author.

Contributed by the Design Theory and Methodology Committee of ASME for publication in the JOURNAL OF MECHANICAL DESIGN. Manuscript received February 11, 2016; final manuscript received February 9, 2017; published online April 4, 2017. Assoc. Editor: Shapour Azarm.

J. Mech. Des 139(5), 051103 (Apr 04, 2017) (16 pages) Paper No: MD-16-1117; doi: 10.1115/1.4036129 History: Received February 11, 2016; Revised February 09, 2017

Maps are visual design representations used by engineers to model the information behind a design. This paper evaluates the application of mapping methods supported by the Decision Rationale editor (DRed) in aerospace engineering industry. Specifically, the research investigates what DRed mapping methods are used, where engineers find them useful and why. DRed was selected because it has been formally embedded in the design processes of the partner company and all engineering staff have access to it. The tool was investigated using semistructured interviews with 14 engineers, each already trained with DRed through their work and representing diverse departments and experience levels. Nineteen use cases were collected, ranging from high-profile, multistakeholder projects to everyday individual work. Collected cases were analyzed for the methods applied, common contexts of use, and reasons for use. The results validate baseline DRed mapping methods to capture design rationale and analyze the root causes of engineering problems. Further, it provides empirical evidence for new DRed mapping methods to manage requirements, analyze functional interactions in complex systems and manage personal information. The contexts where mapping methods are most used involve: system-level information that cuts across subsystem boundaries; irregular intervals between map applications; dealing with loosely structured information; individual use or small team collaborations; and addressing on-going problems. The reasons stated by engineers for using maps focus on engineering design thinking, communication, and planning support. Using empirical evidence of its recurrent use, this research establishes that DRed is a powerful and versatile tool for engineers in industry and its mapping methods aid important and otherwise unsupported work. The range and impact of the use cases found in practice suggest that engineers need better support for work with loosely structured information. Organizations involved in the design of complex systems should make greater use of semiformal, graph-based visual tools like DRed. The understanding of mapping software gained through this research demonstrates a shift in emphasis from the enrichment of the engineering record to the provision of immediate cognitive benefits for engineers. The results also support an incremental, adaptive approach for deploying this emerging class of tools in other organizations.

FIGURES IN THIS ARTICLE
<>
Copyright © 2017 by ASME
Your Session has timed out. Please sign back in to continue.

References

Figures

Grahic Jump Location
Fig. 1

Example of IBIS map implemented in DRed to visualize an engineering design problem [9,10]

Grahic Jump Location
Fig. 2

Mind map using Freemind [38]; Spatial hypertext map in designVUE [39]; Concept map generation process using IHMC CmapTools [24]; Hypermedia diagramming in Compendium [40]

Grahic Jump Location
Fig. 3

Elements and links in DRed maps

Grahic Jump Location
Fig. 4

Situation of study within DRM

Grahic Jump Location
Fig. 5

Design rationale capture example map

Grahic Jump Location
Fig. 6

Root cause analysis example map

Grahic Jump Location
Fig. 7

Function analysis diagram example map

Grahic Jump Location
Fig. 8

Requirements management example map

Tables

Errata

Discussions

Some tools below are only available to our subscribers or users with an online account.

Related Content

Customize your page view by dragging and repositioning the boxes below.

Related Journal Articles
Related eBook Content
Topic Collections

Sorry! You do not have access to this content. For assistance or to subscribe, please contact us:

  • TELEPHONE: 1-800-843-2763 (Toll-free in the USA)
  • EMAIL: asmedigitalcollection@asme.org
Sign In