Early alignment of design requirements with stakeholder needs

Agouridas, Vassilis; Winand, H.M.A.; McKay, Alison; Pennington, Alan de

doi:10.1243/09544054jem404

Cited by 20 publications

(19 citation statements)

References 70 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Design rationale, as captured using tools such as Rationale™ [5,55,73] and DRed [11], is a means by which designed physical structures are related to intended functional structures. Design intent, for example as captured using advanced requirements management techniques [2], enables intended functional structures to be related to stakeholder intents and so aspects of what Vermaas and Houkes refer to as use plans. An initial analysis of requirements for the definition of physical products and services is provided in Table 1.…”

Section: Definitions Of Physical Products and Service Productsmentioning

confidence: 99%

“…Product (service) definition parallels Product Specification: Requirements and links to stakeholder needs [2] For services, Service Level Agreements, Performance Indicators (PIs) and Key Performance Indicators (KPIs) constitute a service specification Product Definition: What is defined depends upon the kind of product and the product development process being used: specifically, the information required at each stage gate and through key process steps Service designs (including ''to be'' service processes) are equivalent to product definitions. Drawing parallels with physical product development, understanding of the Service Development Process, for example ABB Full Service Ò [1], which provides process phases and decision points is needed to determine the scope and coverage of service definitions Product Definition/Representation: Product structure and relationships are key information [44].…”

Section: Product (Artefact-goods) Definitionmentioning

confidence: 99%

See 1 more Smart Citation

A representation scheme for digital product service system definitions

McKay

Kundu

2014

Advanced Engineering Informatics

View full text Add to dashboard Cite

a b s t r a c tThe growing trend for delivering physical products to customers as parts of product service systems (PSS) is creating a need for a new generation of Computer Aided Design (CAD) system to support the design of PSS: so-called ''PSS-CAD''. Key research issues in the development of such systems include building understanding of the kinds of applications that designers of PSS might need and the establishment of well-founded representation schemes to underpin and support communication between PSS-CAD systems. Recent literature includes numerous descriptions of integrated PSS development processes, PSS-CAD tools to support these processes and early meta-models to provide information support. This paper complements this work by proposing a representation scheme that is a key prerequisite to achieving the interoperability between PSS-CAD systems which would be necessary to support the deployment of integrated PSS development processes in industry.The representation scheme, a form of meta-model, draws on learning from the product definition community that emerged in the 1970s in response to a need for interoperability between the different shape-based CAD systems that were being developed at the time. The initial focus on shape representation has developed to digital product definitions that define the design of a product coupled with meta-data recording details of processes by which the design was created and, more recently, supported through-life. Similarly, PSS-related information includes both PSS definitions, to support the lifecycles of physical products and associated services, and meta-data needed to support the management of PSS development processes.This paper focuses on information requirements for the definition of service elements of PSS and relationships with product elements and service actors. These requirements are derived from earlier work on the use of service blueprinting for the visualisation and mapping of service activities to deliver different types of service contract. Key information requirements addressed include the need to represent service process flow and breakdown structures, relationships between service and product elements, substitution relationships, and service variants. A representation scheme is proposed and demonstrated through application to a PSS case study. The representation scheme is built on a generic information architecture that has already been applied to problems of product definition; as such there is an underlying compatibility that offers real promise in the future realisation of integrated PSS development processes.

show abstract

Section: Definitions Of Physical Products and Service Productsmentioning

confidence: 99%

Section: Product (Artefact-goods) Definitionmentioning

confidence: 99%

A representation scheme for digital product service system definitions

McKay

Kundu

2014

Advanced Engineering Informatics

View full text Add to dashboard Cite

show abstract

“…These initial customer statements are then transformed into customer needs that are independent from any particular solution developed to address them. 13 Customer needs are then transformed into system requirements and in turn into component requirements. All these together represent a traditional requirements specification for system development.…”

Section: Definitions Of Key Conceptsmentioning

confidence: 99%

Replacing target setting by value models in the ‘house of quality’ for value-based requirements specifications

Zhang

Eres

Baron

et al. 2014

Proceedings of the Institution of Mechanical Engineers, Part B:

View full text Add to dashboard Cite

Setting targets for engineering characteristics is common practice in the 'house of quality' for establishing requirements specifications. However, if deployed arbitrarily, this practice is prone to errors and can often yield irrational results. Three potential methodological problems have been identified, regarding the setting of independent targets for each engineering characteristic, setting fixed targets and cascading down targets from the system level to the component level have been identified. In this article, targets are categorised as constraints and goals because of their different implications for value trade-offs. Then, a 'multi-attribute utility theory' based approach is proposed, in which a system value model is developed in order to replace the setting of targets for system engineering characteristics and component value models are further derived to replace the setting of targets for component engineering characteristics. These value models enhance the traditional approach to requirements specification so that value-based requirements specifications can be developed. A case study is deployed to demonstrate the applicability of the approach in the civilian aerospace context for the development of requirements for commercial aircraft. The benefits of the proposed approach are twofold: (1) value becomes an explicit construct and (2) value can be rationally modelled and simulated in the 'house of quality' in order to establish value-based requirements specifications. Furthermore, identified methodological problems in terms of setting engineering characteristic targets at any level are mitigated.

show abstract

“…‡ It will be more attractive to express it as stakeholder value, but we limit the focus only on development. It is more about a subjective and human--centric process, and yet there are only a handful of analytical processes and methods available to enable modelling and simulation in terms of value (Agouridas et al 2006, Bayus 2007, Claros Salinas et al 2008, Griffin and Hauser 1993, Pahl and Beitz 2007, Ulrich and Eppinger 2007, Wang and Zeng 2009. Some preliminary work has been made to distinguish or measure different achievement levels of customer satisfaction (value), such as KANO model and quality function deployment (QFD) (Bayus 2007, Hauser and Clausing 1988, Bode and Fung 1998, Zhang and Chu 2009).…”

Section: Introductionmentioning

confidence: 99%

A prescriptive approach to qualify and quantify customer value for value-based requirements engineering

Zhang¹,

Auriol²,

Eres³

et al. 2013

International Journal of Computer Integrated Manufacturing

View full text Add to dashboard Cite

Recently, customer--based product development is becoming a popular paradigm.Customer expectations and needs can be identified and transformed into requirements for product design with the help of various methods and tools. However, in many cases, these models fail to focus on the perceived value that is crucial when customers make the decision of purchasing a product. In this paper, a prescriptive approach to support value--based requirements engineering is proposed, describing the foundations, procedures and initial applications in the context of requirements engineering for commercial aircraft. An integrated set of techniques, such as means--ends analysis, part--whole analysis and multi--attribute utility theory is introduced in order to understand customer values in depth and width. Technically, this enables identifying the implicit value, structuring logically collected statements of customer expectations, and performing value modelling and simulation.Additionally, it helps to put in place a system to measure customer satisfaction that is derived from the proposed approach. The approach offers significant potential to develop effective value creation strategies for the development of new products.

show abstract

Early alignment of design requirements with stakeholder needs

Cited by 20 publications

References 70 publications

A representation scheme for digital product service system definitions

A representation scheme for digital product service system definitions

Replacing target setting by value models in the ‘house of quality’ for value-based requirements specifications

A prescriptive approach to qualify and quantify customer value for value-based requirements engineering

Contact Info

Product

Resources

About