House of Quality
17 Jul 2002-
About: The article was published on 2002-07-17. It has received 1123 citations till now. The article focuses on the topics: House of Quality.
Citations
More filters
TL;DR: The authors argue that service provision rather than goods is fundamental to economic exchange and argue that the new perspectives are converging to form a new dominant logic for marketing, one in which service provision is fundamental for economic exchange.
Abstract: Marketing inherited a model of exchange from economics, which had a dominant logic based on the exchange of “goods,” which usually are manufactured output The dominant logic focused on tangible resources, embedded value, and transactions Over the past several decades, new perspectives have emerged that have a revised logic focused on intangible resources, the cocreation of value, and relationships The authors believe that the new perspectives are converging to form a new dominant logic for marketing, one in which service provision rather than goods is fundamental to economic exchange The authors explore this evolving logic and the corresponding shift in perspective for marketing scholars, marketing practitioners, and marketing educators
12,760 citations
Book•
14 Sep 2011TL;DR: The paper is intended to raise awareness of the far-reaching implications of the architecture of the product, to create a vocabulary for discussing and addressing the decisions and issues that are linked to product architecture, and to identify and discuss specific trade-offs associated with the choice of a product architecture.
Abstract: Product architecture is the scheme by which the function of a product is allocated to physical components. This paper further defines product architecture, provides a typology of product architectures, and articulates the potential linkages between the architecture of the product and five areas of managerial importance: (1) product change; (2) product variety; (3) component standardization; (4) product performance; and (5) product development management. The paper is conceptual and foundational, synthesizing fragments from several different disciplines, including software engineering, design theory, operations management and product development management. The paper is intended to raise awareness of the far-reaching implications of the architecture of the product, to create a vocabulary for discussing and addressing the decisions and issues that are linked to product architecture, and to identify and discuss specific trade-offs associated with the choice of a product architecture.
2,603 citations
04 Jul 2009
TL;DR: This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
Abstract: Essentially a software system's utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
2,443 citations
Cites background or methods from "House of Quality"
...Quality: Noun --...
[...]
...One of the techniques used by QFD strategies is the House of Quality [8], in which the process starts "...with the customer, whose requirements are called customer attributes (CA´s) - phrases customers use to describe products and product characteristics..."....
[...]
...In the area of engineering and management, the well known QFD (Quality Function Deployment) strategy [7] distinguishes positive quality from negative quality: “QFD is quite different in that it seeks out both "spoken" and "unspoken" customer requirements and maximizes "positive" quality (such as ease of use, fun, luxury) that creates value....
[...]
...One of the techniques used by QFD strategies is the House of Quality [8], in which the process starts "....
[...]
...Incidentally, none of the examples of the CA ́s in [8] is related to functionality or just functionality alone....
[...]
01 May 2000
TL;DR: An overview of the field of software systems requirements engineering (RE) is presented, describing the main areas of RE practice, and highlights some key open research issues for the future.
Abstract: This paper presents an overview of the field of software systems requirements engineering (RE). It describes the main areas of RE practice, and highlights some key open research issues for the future.
2,114 citations
Cites background from "House of Quality"
...For example, in Quality Function Deployment (QFD) [34], matrices are constructed to compare functional requirements with one another and rate their importance, but without explicitly identifying stakeholder goals....
[...]
...For example, in Quality Function Deployment (QFD) [34], matrices are constructed to compare functional requirements with one another and rate their importance, but without explicitly identifying stakeholder goals....
[...]
TL;DR: This paper looks inside the "black box" of product development at the fundamentaldecisions that are made by intention or default, adopting the perspective ofproduct development as a deliberate business process involving hundreds of decisions, many of which can be usefully supported by knowledge and tools.
Abstract: This paper is a review of research in product development, which we define as the transformation of a market opportunity into a product available for sale. Our review is broad, encompassing work in the academic fields of marketing, operations management, and engineering design. The value of this breadth is in conveying the shape of the entire research landscape. We focus on product development projects within a single firm. We also devote our attention to the development of physical goods, although much of the work we describe applies to products of all kinds. We look inside the "black box" of product development at the fundamentaldecisions that are made by intention or default. In doing so, we adopt the perspective of product development as a deliberate business process involving hundreds of decisions, many of which can be usefully supported by knowledge and tools. We contrast this approach to prior reviews of the literature, which tend to examine the importance of environmental and contextual variables, such as market growth rate, the competitive environment, or the level of top-management support.
1,725 citations
References
More filters
Book•
14 Sep 2011TL;DR: The paper is intended to raise awareness of the far-reaching implications of the architecture of the product, to create a vocabulary for discussing and addressing the decisions and issues that are linked to product architecture, and to identify and discuss specific trade-offs associated with the choice of a product architecture.
Abstract: Product architecture is the scheme by which the function of a product is allocated to physical components. This paper further defines product architecture, provides a typology of product architectures, and articulates the potential linkages between the architecture of the product and five areas of managerial importance: (1) product change; (2) product variety; (3) component standardization; (4) product performance; and (5) product development management. The paper is conceptual and foundational, synthesizing fragments from several different disciplines, including software engineering, design theory, operations management and product development management. The paper is intended to raise awareness of the far-reaching implications of the architecture of the product, to create a vocabulary for discussing and addressing the decisions and issues that are linked to product architecture, and to identify and discuss specific trade-offs associated with the choice of a product architecture.
2,603 citations
04 Jul 2009
TL;DR: This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
Abstract: Essentially a software system's utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
2,443 citations
01 May 2000
TL;DR: An overview of the field of software systems requirements engineering (RE) is presented, describing the main areas of RE practice, and highlights some key open research issues for the future.
Abstract: This paper presents an overview of the field of software systems requirements engineering (RE). It describes the main areas of RE practice, and highlights some key open research issues for the future.
2,114 citations
TL;DR: This paper looks inside the "black box" of product development at the fundamentaldecisions that are made by intention or default, adopting the perspective ofproduct development as a deliberate business process involving hundreds of decisions, many of which can be usefully supported by knowledge and tools.
Abstract: This paper is a review of research in product development, which we define as the transformation of a market opportunity into a product available for sale. Our review is broad, encompassing work in the academic fields of marketing, operations management, and engineering design. The value of this breadth is in conveying the shape of the entire research landscape. We focus on product development projects within a single firm. We also devote our attention to the development of physical goods, although much of the work we describe applies to products of all kinds. We look inside the "black box" of product development at the fundamentaldecisions that are made by intention or default. In doing so, we adopt the perspective of product development as a deliberate business process involving hundreds of decisions, many of which can be usefully supported by knowledge and tools. We contrast this approach to prior reviews of the literature, which tend to examine the importance of environmental and contextual variables, such as market growth rate, the competitive environment, or the level of top-management support.
1,725 citations
Journal Article•
TL;DR: The authors in this article argue that the new perspectives are converging to form a new dominant logic for marketing, one in which service provision rather than goods is fundamental to economic exchange, and explore this evolving logic and the corresponding shift in perspective for marketing scholars, marketing practitioners, and marketing educators.
Abstract: Marketing inherited a model of exchange from economics, which had a dominant logic based on the exchange of “goods,” which usually are manufactured output. The dominant logic focused on tangible resources, embedded value, and transactions. Over the past several decades, new perspectives have emerged that have a revised logic focused on intangible resources, the cocreation of value, and relationships. The authors believe that the new perspectives are converging to form a new dominant logic for marketing, one in which service provision rather than goods is fundamental to economic exchange. The authors explore this evolving logic and the corresponding shift in perspective for marketing scholars, marketing practitioners, and marketing educators.
1,657 citations