Stuart Pugh

Last updated

Stuart Pugh
Born1929
Halifax, UK
Died9 October 1993 (aged 64)
NationalityBritish
Known for Total Design and Pugh Concept Selection
Scientific career
Fields Product design and development, engineering and management
Institutions University of Strathclyde, Glasgow, Scotland – Design Division
Loughborough University

Stuart Pugh (1929 - 9 October 1993) was a British product designer from Halifax, UK. He is known for redefining Total Design (methodology), which had previously been coined by Ove Arup regarding integrated architecture and structural engineering, [1] to instead map a structured and integrated process in the field of product design and development that included market and production processes. [2]

Contents

Biography

Stuart Pugh was a design engineer and manager. His experience in industry led him to pursue a secondary career in academia, where he published on 'Total Design'.

Stuart Pugh graduated from London University with a degree in Mechanical Engineering and became a graduate apprentice for the British Aircraft Corporation. In 1956 he worked in the Warton Aerodrome as a project engineer for the Mach 6 Wind Tunnel. In 1963 he became the Chief Designer of the Mechanical Product Division at the Marconi Company. In the later stages of his industrial career, Pugh worked within the English Electric Company as Chief Designer in the Hydraulic Equipment Division, ultimately progressing to become Divisional Manager.

Pugh left industry in 1970 and began his academic career as a 'Smallpeice' Reader in Design for Production at Loughborough University of Technology. Later, he became the Director of the 'Engineering Design Centre'.

Pugh moved to Scotland and in 1985 became the 'Babcock Professor of Engineering Design' and the head of the 'Design Division' at the University of Strathclyde in Glasgow. The Design Division merged in 1989 with the Department of Production Management and Manufacturing Technology to create the Department of Design, Manufacture and Engineering Management (DMEM), of which Pugh remained head until his death in 1993. It was here that Pugh produced his seminal book, 'Total Design: Integrated Methods for Successful Product Engineering’, published in 1990. Pugh Introduced and taught Total Design across the faculty of engineering at Strathclyde University. He ran multidisciplinary design classes which included students of architecture and law. He also contributed to the MBA program and taught short courses on Total Design to Industrial managers.

Soon after Pugh published his book 'Total Design', Professor Don Clausing (MIT) and Professor Ken Ragsdell (University of Missouri) encouraged Pugh to publish his collection of papers to make his work readily available to design engineers and managers. However, Pugh's untimely death from illness ultimately led Don Clausing and Ronaldo Andrade (Universidade Federal de Rio de Janeiro, Brazil) to complete Pugh's book 'Creating Innovative Products Using Total Design: The Living Legacy of Stuart Pugh’.

Total Design

Definition of Total Design

“Total Design is the systematic activity necessary, from the identification of the market/user need, to the selling of the successful product to satisfy that need – an activity that encompasses product, process, people and organisation.” – Stuart Pugh [3]

The design process previous to the total design methodology was very much ad hoc which Pugh described as ‘partial design’. Engineers and designers focused on their part within the total design of a product, rarely becoming part of the full product development process. This often led to commercial failure, due to the lack of consideration of the market, the user needs and the resources of the organisation (non-technological factors). Total design offers a visible operational structure which allows for the integration of technological and non-technological parts enabling efficient and effective product development.

Design Activity Model

“Total design may be construed as having a central core of activities, all of which are imperative for any design, irrespective of domain. Briefly, this core, the design core, consists of market (user need), product design specification, conceptual design, detail design, manufacture and sales. All design starts, or should start, with a need that, when satisfied, will fit into an existing market or create a market of its own.” – Stuart Pugh [3]


The design core separates the design process into six iterative stages. This structure enables the seamless flow of information between stages while enabling the formation of multi-disciplined project teams.

Product Design Specification (PDS)

"From the statement of the need – often called the brief – a product design specification (PDS) must be formulated – the specification of the product to be designed. Once this is established, it acts as the mantle or cloak that envelopes all the subsequent stages in the design core. The PDS thus acts as the control for the total design activity, because it places the boundaries on the subsequent designs." – Stuart Pugh [3]


A PDS is a dynamic document that evolves during the design process. At the end of the design activity the design must be in balance with the final version of the PDS. Pugh devised a structure for a PDS that has 34 elements, however some elements may not be applicable to certain projects.

Concept Selection – Method of Controlled Convergence

Pugh's most famous work, "Concept Selection – A Method that Works", [4] describes Pugh's innovative 'controlled convergence' technique that was put to the test so successfully for General Motors' Saturn project.

"A major advantage of controlled convergence over other matrix selection methods is that it allows alternative convergent (analytic) and divergent (synthetic) thinking to occur, since as the reasoning proceeds and a reduction in the number of concepts comes about for rational reasons, new concepts are generated." – Stuart Pugh [5]

The "Pugh method" of concept selection is a form of decision matrix, associated with the QFD method. It is implemented by establishing an evaluation team and constructing the matrix which contains evaluation criteria versus alternative concepts. A baseline concept is selected and the other concepts are scored against the criteria relative to the baseline. The scoring is done in symbol form, of either a positive, negative or neutral scoring. The scores are then combined to give a numerical output for each concept, the highest score being the most compatible.

Publications

Books

See also

Notes

  1. Uihlein, M.S. (3 March 2016). "Ove Arup's total design, integrated project delivery, and the role of the engineer". Architectural Science Review. 59 (2): 102–113. doi:10.1080/00038628.2014.963022. ISSN   0003-8628. S2CID   110888459.
  2. Backhouse, Christopher J. (September 1991). "A review of: " Total Design. " By STUART PUGH. (Addison Wesley, 1991) [Pp. 278] Paperback, £16.95. Level: Designer/design lecturer". International Journal of Computer Integrated Manufacturing. 4 (5): 321. doi:10.1080/09511929108944508. ISSN   0951-192X.
  3. 1 2 3 Pugh 1991, p. 5.
  4. S. Pugh (1981) Concept selection: a method that works. In: Hubka, V. (ed.), Review of design methodology. Proceedings international conference on engineering design, March 1981, Rome. Zürich: Heurista, 1981, blz. 497 – 506.
  5. Pugh 1991, p. 74.

Related Research Articles

<span class="mw-page-title-main">Computer program</span> Instructions to be executed by a computer

A computer program is a sequence or set of instructions in a programming language for a computer to execute. It is one component of software, which also includes documentation and other intangible components.

<span class="mw-page-title-main">Application-specific integrated circuit</span> Integrated circuit customized for a specific task

An application-specific integrated circuit is an integrated circuit (IC) chip customized for a particular use, rather than intended for general-purpose use, such as a chip designed to run in a digital voice recorder or a high-efficiency video codec. Application-specific standard product chips are intermediate between ASICs and industry standard integrated circuits like the 7400 series or the 4000 series. ASIC chips are typically fabricated using metal–oxide–semiconductor (MOS) technology, as MOS integrated circuit chips.

In software engineering, a software design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design. It is not a finished design that can be transformed directly into source or machine code. Rather, it is a description or template for how to solve a problem that can be used in many different situations. Design patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system.

Software design is the process by which an agent creates a specification of a software artifact intended to accomplish goals, using a set of primitive components and subject to constraints. The term is sometimes used broadly to refer to "all the activity involved in conceptualizing, framing, implementing, commissioning, and ultimately modifying" the software, or more specifically "the activity following requirements specification and before programming, as ... [in] a stylized software engineering process."

Rapid application development (RAD), also called rapid application building (RAB), is both a general term for adaptive software development approaches, and the name for James Martin's method of rapid development. In general, RAD approaches to software development put less emphasis on planning and more emphasis on an adaptive process. Prototypes are often used in addition to or sometimes even instead of design specifications.

Software development is the process used to conceive, specify, design, program, document, test, and bug fix in order to create and maintain applications, frameworks, or other software components. Software development involves writing and maintaining the source code, but in a broader sense, it includes all processes from the conception of the desired software through the final manifestation, typically in a planned and structured process often overlapping with software engineering. Software development also includes research, new development, prototyping, modification, reuse, re-engineering, maintenance, or any other activities that result in software products.

"No Silver Bullet—Essence and Accident in Software Engineering" is a widely discussed paper on software engineering written by Turing Award winner Fred Brooks in 1986. Brooks argues that "there is no single development, in either technology or management technique, which by itself promises even one order of magnitude [tenfold] improvement within a decade in productivity, in reliability, in simplicity." He also states that "we cannot expect ever to see two-fold gains every two years" in software development, as there is in hardware development.

In software development, agile practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s), Popularized in the 2001 Manifesto for Agile Software Development, these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.

<span class="mw-page-title-main">Ivar Jacobson</span>

Ivar Hjalmar Jacobson is a Swedish computer scientist and software engineer, known as major contributor to UML, Objectory, Rational Unified Process (RUP), aspect-oriented software development and Essence.

In agile principles, timeboxing allocates a maximum unit of time to an activity, called a timebox, within which a planned activity takes place. It is used by agile principles-based project management approaches and for personal time management.

Richard Turner is a distinguished service professor in the School of Systems and Enterprises of Stevens Institute of Technology in Hoboken, New Jersey.

Object-oriented analysis and design (OOAD) is a technical approach for analyzing and designing an application, system, or business by applying object-oriented programming, as well as using visual modeling throughout the software development process to guide stakeholder communication and product quality.

Design methods are procedures, techniques, aids, or tools for designing. They offer a number of different kinds of activities that a designer might use within an overall design process. Conventional procedures of design, such as drawing, can be regarded as design methods, but since the 1950s new procedures have been developed that are more usually grouped together under the name of "design methods". What design methods have in common is that they "are attempts to make public the hitherto private thinking of designers; to externalise the design process".

<span class="mw-page-title-main">Design management</span> Field of inquiry in business

Design management is a field of inquiry that uses design, strategy, project management and supply chain techniques to control a creative process, support a culture of creativity, and build a structure and organization for design. The objective of design management is to develop and maintain an efficient business environment in which an organization can achieve its strategic and mission goals through design. Design management is a comprehensive activity at all levels of business, from the discovery phase to the execution phase. "Simply put, design management is the business side of design. Design management encompasses the ongoing processes, business decisions, and strategies that enable innovation and create effectively-designed products, services, communications, environments, and brands that enhance our quality of life and provide organizational success." The discipline of design management overlaps with marketing management, operations management, and strategic management.

In programming languages, an abstract type is a type in a nominative type system that cannot be instantiated directly; by contrast, a concrete typecan be instantiated directly. Instantiation of an abstract type can occur only indirectly, via a concrete subtype.

Design thinking refers to the set of cognitive, strategic and practical procedures used by designers in the process of designing, and to the body of knowledge that has been developed about how people reason when engaging with design problems.

<span class="mw-page-title-main">IDEF6</span>

IDEF6 or Integrated Definition for Design Rationale Capture is a method to facilitate the acquisition, representation, and manipulation of the design rationale used in the development of enterprise systems. This method, that wants to define the motives that drive the decision-making process, is still in development. Rationale is the reason, justification, underlying motivation, or excuse that moved the designer to select a particular strategy or design feature. More simply, rationale is interpreted as the answer to the question, “Why is this design being done in this manner?” Most design methods focus on what the design is.

<span class="mw-page-title-main">Donald Firesmith</span>

Donald G. Firesmith is an American software engineer, consultant, and trainer at the Software Engineering Institute.

Specification by example (SBE) is a collaborative approach to defining requirements and business-oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements. It is applied in the context of agile software development methods, in particular behavior-driven development. This approach is particularly successful for managing requirements and functional tests on large-scale projects of significant domain and organisational complexity.

<span class="mw-page-title-main">University of Strathclyde Faculty of Engineering</span>

The Faculty of Engineering is one of the four faculties which make up the University of Strathclyde in Glasgow, Scotland. The faculty contains multiple departments offering many different undergraduate and postgraduate courses. These range from BEng, MEng and MSc courses to doctorates throughout the faculty.

References