3.3.1 Consumer product development: A systems engineering approach to the derivation of design requirements from stakeholder needs

INCOSE International Symp

Longstaff

Childs

et al. 2006

Self Cite

Abstract. This paper reports results of research carried out in the context of a co-ordination action funded by the European Commission that dealt with the gathering and evaluation of state of the art tools, best practice methods and techniques deployed by leading manufacturers in developing appealing consumer products. Data was gathered through questionnaires and semistructured interviews. Analysis of the data showed that the design of appealing products involves an intricate web of relationships amongst understanding consumer needs, determining and verifying product characteristics, and validating products that excite consumers. The need for a systems engineering approach in rationalising such an intricate web of relationships is described based on the research findings. A number of challenges associated with the implementation of such an approach are discussed.

Section: Discussionmentioning

confidence: 99%

Section: Figure 1 (A) Malsow's Hierarchy Of Needs and (B) The Kano Mmentioning

confidence: 99%

11.2.1 Challenges in the application of systems engineering principles to the design of appealing consumer products

INCOSE International Symp

Longstaff

Childs

et al. 2006

Self Cite

“…Furthermore, the relationships between the different types of customer data need to be explicitly articulated. A key to innovation in product design is the decoupling of specific needs from specific solutions or specific design ideas (Agouridas et al, 2001(Agouridas et al, , 2004. There are two issues here that should be taken into account (Agouridas, Yagou, et al, 2006): 1.…”

Section: The Importance Of Establishing Intentional Structures In Desmentioning

confidence: 99%

“…Underlying or latent customer needs can be identified in a systematic and traceable manner by decoupling specific needs from specific solutions (Agouridas et al, 2004;Agouridas, Marshall, et al, 2006). This is where leap innovation can take place.…”

Section: The Importance Of Establishing Intentional Structures In Desmentioning

confidence: 99%

Antecedence and consequence in design rationale systems

Simons

2008

AIEDAM

Self Cite

Identification of latent or unarticulated customer and other stakeholder needs has been a significant barrier to improving the efficiency and effectiveness of the front-end phase of new product development processes. In-depth determination of stakeholder needs entails analysis of their intentions; the overall aim of the work reported in this article is to establish a framework of intentional analysis, and its associated methods and techniques for improving traceability of design practice during the early phases of the design process. The specific aim of this article is to present a conceptual framework for design rationale systems. The framework built upon the cross-fertilization of approaches and methods drawn from systems engineering and philosophy, focussing on the notions of antecedence and consequence. It was developed in the course of tackling design problems originating in industrial contexts. The methods developed were thus evaluated, updated, and refined in real applications. Two application cases are described that have been drawn from the aerospace and power sectors, respectively. The applications showed that the framework's central antecedent/consequent scheme provides a cell from which to develop either a history of actual successive changes, or a tree of alternative possible projected designs.

“…2. Table 1 defines the concepts required for the purposes of this paper; apart from the mapping relationship, all of these concepts have been introduced by Agouridas et al [90]. Next, Fig.…”

Section: The Systematic Derivation Of Design Requirements From Stakeholder Needsmentioning

confidence: 99%

Early alignment of design requirements with stakeholder needs

Proceedings of the Institution of Mechanical Engineers, Part B:

Winand

McKay

et al. 2006

Informality of design requirements is a problem, especially in distributed design teams, because it impacts upon the ability of a team to communicate. Since design requirements drive the design process, their miscommunication results in serious problems; for example, new products that do not align with the needs of the range of stakeholders to whom they are targeted. This, in turn, has a detrimental impact on traditional business performance indicators, such as market share, volume of sales, and profit. The research reported in this paper explored the applicability of requirements engineering and management techniques, traditionally used in the development of software-intensive systems, to the development of electromechanical consumer products. The motivational rationale traceability matrix (MoRal™) is introduced as a means to support the initial analysis of stakeholder needs and attributes, and the derivation of corresponding design requirements. The applicability of MoRalTM is demonstrated through application to a power solution case study. In this instance, the MoRalTM proved to be a powerful means of supporting the derivation of design requirements that are aligned with customer and other stakeholder needs, and are traceable to stakeholder intents.