Knowledge-enriched Requirement Specification for One-of-a-kind Complex Systems

Requirement engineering (RE) process is becoming a key factor for the success of complex one-of-a-kind products. The RE process is commonly viewed as an early system engineering phase with a major bearing on response time, quality, and cost. This study reports on the knowledge acquisition and sharing for requirement engineering (KARE), approach for requirement specification of one-of-a-kind complex systems. The approach provides a generic view of key RE processes clustered into three groups of activities - requirements elicitation, analysis, and negotiation. The process is supported by a set of knowledge functions aimed at facilitating the requirement engineers in matching customer requirements to product characteristics. At the analysis stage, the customer requirements are transformed into product requirements, which can be compared to existing company knowledge, for example, previous products, technology platforms, and production capabilities. The specified product requirements are then interactively evaluated and negotiated against customer and supplier performance indicators.

[1]  C. P. Goodman,et al.  The Tacit Dimension , 2003 .

[2]  K. Heimannsfeld,et al.  Requirements engineering knowledge management based on STEP AP233 , 2000 .

[3]  Brian R. Gaines,et al.  Integrated knowledge acquisition architectures , 1992, Journal of Intelligent Information Systems.

[4]  Hong Zhu,et al.  Scenario Analysis in an Automated Tool for Requirements Engineering , 2000, Requirements Engineering.

[5]  K. Popper.  Objective Knowledge: An Evolutionary Approach , 1972 .

[6]  Kyo Chul Kang,et al.  ASADAL/SIM: an incremental multi-level simulation and analysis tool for real-time software specifications , 1998 .

[7]  Søren Lauesen,et al.  Preventing Requirement Defects: An Experiment in Process Improvement , 2001, Requirements Engineering.

[8]  Arnis Daugulis.  Time Aspects in Requirements Engineering: Or ‘Every Cloud Has A Silver Lining’ , 2000, Requirements Engineering.

[9]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[10]  Ivy Hooks,et al.  Why Johnny Can't Write Requirements , 1990 .

[11]  Juite Wang,et al.  Fuzzy outranking approach to prioritize design requirements in quality function deployment , 1999 .

[12]  Heinrich C. Mayr,et al.  Linguistically based requirements engineering - The NIBA-project , 2000, Data Knowl. Eng..

[13]  Svetan M. Ratchev,et al.  Knowledge based requirement engineering for one-of-a-kind complex systems , 2003, Knowl. Based Syst..

[14]  Guus Schreiber,et al.  Knowledge Engineering and Management: The CommonKADS Methodology , 1999 .

[15]  Richard Stevens,et al.  Systems engineering : coping with complexity , 1998 .

[16]  S J Culley,et al.  Current research in the engineering design requirement , 2002 .

[17]  Kyo Chul Kang,et al.  ASADAL/SIM: An Incremental Multi-Level Simulation and Analysis Tool for Real-Time Software Specifications , 1998, Softw. Pract. Exp..

[18]  Scott P. Overmyer.  A Methodology for Constructing User-Oriented Requirements Specifications for Large-Scale Systems Using Electronic Hypermedia , 1999, Requirements Engineering.

[19]  Ian K. Bray,et al.  An Introduction to Requirements Engineering , 2002 .

[20]  R. Swinburne.  OBJECTIVE KNOWLEDGE: AN EVOLUTIONARY APPROACH , 1973 .

[21]  P. C. Stadzisz,et al.  An integrated approach for the design of multi-product assembly systems , 1998 .

[22]  K. Heimannsfeld,et al.  KARE - knowledge acquisition and sharing for requirement engineering , 1998 .