In engineering design, capturing customers’ requirements exactly and transforming them into design specifications are vital to designing a quality product. However, the expressions of customer requirements are normally imprecise and ambiguous due to their linguistic origins. There is still a lack of a systematic approach for elaborating these requirements and transforming them from informal to formal. Therefore, this article provides a scenario-based, systematic approach for requirements management in engineering design. The requirements management process is conceptualized as a three-phase model, and scenarios are integrated into this model for elaborating and formally representing the requirements. A case study of a soy milk maker design is also provided to demonstrate the proposed approach.
BaxterDGaoJCaseK. (2008) A framework to integrate design knowledge reuse and requirements management in engineering design. Robotics and Computer-Integrated Manufacturing24: 585–593.
3.
CarrollJ (2000) Five reasons for scenario-based design. Interacting with Computers13: 43–60.
4.
ChenC-HOccenaLG (1999) A knowledge sorting process for a product design expert system. Expert Systems16(3): 170–182.
5.
ChenC-HOccenaLG (2000) Knowledge decomposition for a product design black-board expert system. Artificial Intelligence in Engineering14(1): 71–82.
6.
ChenC-HKhooLPYanW (2002) A strategy for acquiring customer requirement patterns using laddering technique and ART2 neural network. Advanced Engineering Informatics16(3): 229–240.
7.
DarlingtonMJCulleySJ (2002) Current research in the engineering design requirement. Proceedings of IMechE, Part B: Journal of Engineering Manufacture216(3): 375–388.
8.
FikselJHayes-RothF (1993) Computer-aided requirement management. Concurrent Engineering: Research and Application1(2): 83–92.
9.
FungRYKTangJTuPY. (2003) Modeling of quality function deployment planning with resource allocation. Research in Engineering Design14(1): 247–255.
10.
Herlea DamianDEJonkerCMTreurJ. (2005) Integration of behavioural requirements specification within compositional knowledge engineering. Knowledge-Based Systems Journal18: 353–365.
11.
HooksIFFarryKA (2001) Customer-Centered Products. New York: AMACOM.
12.
JiaoJChenC-H (2006) Customer requirement management in product development: a review of research issues. Concurrent Engineering: Research and Application14(3): 173–185.
13.
JiaoJZhangY (2005) Product portfolio identification based on association rule mining. Computer-Aided Design37(2): 149–172.
14.
KaindlH (2000) A design process based on a model combining scenarios with goals and functions. IEEE Transactions on Systems, Man and Cybernetics, Part A: Systems and Humans30(5): 537–551.
15.
KanoNSerakuNTakahashiF. (1984) Attractive quality and must-be quality. Japan Society for Quality Control, Hinshitsu14(2): 39–48.
16.
KazemzadehRBBehzadianMAghdasiM. (2009) Integration of marketing research techniques into house of quality and product family design. International Journal of Manufacturing Technology41: 1019–1033.
17.
KurakawaK (2004) A scenario-driven conceptual design information model and its formation. Research in Engineering Design15: 122–137.
18.
MisraSKumarVKumarU (2005) Goal-oriented or scenario-based requirements engineering technique-what should a practitioner select? In: Canadian conference on electrical and computer engineering, Saskatoon, Canada1–4 May.
PottsC (1999) ScenIC: a strategy for inquiry-driven requirements determination. In: 4th IEEE international symposium on requirements engineering, pp.58–65. Los Alamitos, CA7–11 June: IEEE Computer Society Press.
21.
PrasadB (1998) Review of QFD and related deployment techniques. Journal of Manufacturing Systems17(3): 221–234.
22.
PrasadB (2000) A concurrent function deployment technique for a workgroup-based engineering design process. Journal of Engineering Design11(2): 103–119.
23.
PrudhommeGZwolinskiPBrissaudD (2003) Integrating into the design process the needs of those involved in the product life-cycle. Journal of Engineering Design14(3): 333–353.
24.
RiosJRoyRSackettP (2006) Requirements engineering and management for manufacturing, Michigan, USA: Society of Manufacturing Engineers (SME). Blue Book Series.
25.
RussellSNorvigP(1995) Artificial intelligence: a modern approach, 2nd ed.Hong Kong: Pearson Education Asia Limited and Tsinghua Univ. Press, 2006.
26.
SutcliffeAG (2003) Scenario-based requirements engineering. In: Proceedings of the 11th IEEE international conference. Montery Bay, CA, 8–12 September 2003, pp.320–329. Los Alamitos, CA: IEEE Computer Society Press.
TsengMMJiaoJ (1998) Computer-aided requirement management for production definition: a methodology and implementation. Concurrent Engineering: Research and Application6(2): 145–160.
29.
YanWChenC-HKhooLP (2002) An integrated approach to the elicitation of customer requirements for engineering design using picture sorts and fuzzy evaluation. Artificial Intelligence for Engineering Design, Analysis and Manufacturing16(2): 59–71.
