The derivation of design requirements from stakeholder needs
Globalisation of competition and the demand to deliver increasing stakeholder value has dramatically influenced the operation of engineering enterprises over the last decade. Enterprises have universally recognised the effectiveness of the design process as a critical success factor for accomplishin...
Main Author: | |
---|---|
Published: |
University of Leeds
2003
|
Subjects: | |
Online Access: | http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.401278 |
id |
ndltd-bl.uk-oai-ethos.bl.uk-401278 |
---|---|
record_format |
oai_dc |
spelling |
ndltd-bl.uk-oai-ethos.bl.uk-4012782015-03-19T06:44:36ZThe derivation of design requirements from stakeholder needsAgouridas, Vassilis2003Globalisation of competition and the demand to deliver increasing stakeholder value has dramatically influenced the operation of engineering enterprises over the last decade. Enterprises have universally recognised the effectiveness of the design process as a critical success factor for accomplishing their aims, because it enables them to deliver products of requisite quality consistently. The design process can be described by four design domains. These are the customer, functional, physical, and process domains. Design involves mapping between these domains. A number of tools exist to support these mappings. However, they are applicable only to the mappings between the functional, physical, and process domains. For example, the derivation of design requirements (functional domain) that are based on the design parameters of a product (physical domain) can be supported; existing tools do not address the derivation of design requirements (functional domain) that are the outcome of mapping from stakeholder needs (customer domain). This thesis proposes a systematic approach for deriving design requirements from stakeholder needs. The approach includes a representation scheme that allows for a detailed analysis of stakeholder requirements. For example, a stakeholder requirement can be expressed as a stakeholder need or as a stakeholder attribute. It also includes a process that enables the systematic derivation of design requirements from stakeholder needs. For example, stakeholder needs are mapped to stakeholder attributes and vice versa; and stakeholder attributes (SAs) are distilled based on their similarities into single statements of SAs (referred to as distilled SAs). Design requirements that correspond to the distilled SAs are then derived. The approach has been, implemented in a leading and widely-used commercial requirements management software application; namely, Telelogic-DOORS. An evaluation of the approach to support a product development team during the derivation of design requirements for a new product was carried out.338.762University of Leedshttp://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.401278http://etheses.whiterose.ac.uk/165/Electronic Thesis or Dissertation |
collection |
NDLTD |
sources |
NDLTD |
topic |
338.762 |
spellingShingle |
338.762 Agouridas, Vassilis The derivation of design requirements from stakeholder needs |
description |
Globalisation of competition and the demand to deliver increasing stakeholder value has dramatically influenced the operation of engineering enterprises over the last decade. Enterprises have universally recognised the effectiveness of the design process as a critical success factor for accomplishing their aims, because it enables them to deliver products of requisite quality consistently. The design process can be described by four design domains. These are the customer, functional, physical, and process domains. Design involves mapping between these domains. A number of tools exist to support these mappings. However, they are applicable only to the mappings between the functional, physical, and process domains. For example, the derivation of design requirements (functional domain) that are based on the design parameters of a product (physical domain) can be supported; existing tools do not address the derivation of design requirements (functional domain) that are the outcome of mapping from stakeholder needs (customer domain). This thesis proposes a systematic approach for deriving design requirements from stakeholder needs. The approach includes a representation scheme that allows for a detailed analysis of stakeholder requirements. For example, a stakeholder requirement can be expressed as a stakeholder need or as a stakeholder attribute. It also includes a process that enables the systematic derivation of design requirements from stakeholder needs. For example, stakeholder needs are mapped to stakeholder attributes and vice versa; and stakeholder attributes (SAs) are distilled based on their similarities into single statements of SAs (referred to as distilled SAs). Design requirements that correspond to the distilled SAs are then derived. The approach has been, implemented in a leading and widely-used commercial requirements management software application; namely, Telelogic-DOORS. An evaluation of the approach to support a product development team during the derivation of design requirements for a new product was carried out. |
author |
Agouridas, Vassilis |
author_facet |
Agouridas, Vassilis |
author_sort |
Agouridas, Vassilis |
title |
The derivation of design requirements from stakeholder needs |
title_short |
The derivation of design requirements from stakeholder needs |
title_full |
The derivation of design requirements from stakeholder needs |
title_fullStr |
The derivation of design requirements from stakeholder needs |
title_full_unstemmed |
The derivation of design requirements from stakeholder needs |
title_sort |
derivation of design requirements from stakeholder needs |
publisher |
University of Leeds |
publishDate |
2003 |
url |
http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.401278 |
work_keys_str_mv |
AT agouridasvassilis thederivationofdesignrequirementsfromstakeholderneeds AT agouridasvassilis derivationofdesignrequirementsfromstakeholderneeds |
_version_ |
1716751619926786048 |