A New Way to Organize DFX in a Large Organization

Efficient requirements engineering and design is a demanding task. Design for excellence (DFX) offers a way to bring together different views and harmonizing practices. There are still impediments, for example, in having internal and external customers valued appropriately. The organizational implementation of DFX in itself is a debated question. We present a new way to organize the DFX concept in a large organization. The results are based on experiences of a large organization that operates in the area of ICT systems, and has had a successful implementation of the DFX concept for several years. Contrary to the traditional way of managing the DFX within R&D it is beneficial to organize it within also other parts of the operational subsystem, as this makes the concept and its improvement more visible and widespread in the organization. However, this requires seeing the concepts of problem domain and solution domain from a new angle.

[1]  Timo Kaski.  Product structure metrics as an indicator of demand-supply chain efficiency : case study in the cellular network industry , 2002 .

[2]  Mark Dodgson,et al.  The Management Of Technological Innovation , 2000 .

[3]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[4]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[5]  James G. Bralla.  Design for Excellence , 1995 .

[6]  J. Holmström,et al.  Managing product introductions across the supply chain: findings from a development project , 2006 .

[7]  Jacob L. Cybulski,et al.  Requirements Classification and Reuse: Crossing Domain Boundaries , 2000, ICSR.

[8]  Leszek A. Maciaszek,et al.  Requirements analysis and system design: developing information systems with UML , 2001 .

[9]  Marilyn M. Helms,et al.  Supply chain forecasting - Collaborative forecasting supports supply chain management , 2000, Bus. Process. Manag. J..

[10]  William B. Frakes,et al.  Software Reuse: Advances in Software Reusability , 2000, Lecture Notes in Computer Science.

[11]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[12]  John T. Mentzer,et al.  The Need for a Forecasting Champion , 1997 .

[13]  Bashar Nuseibeh,et al.  Relating software requirements and architectures using problem frames , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[14]  K. Eisenhardt.  Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

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

[16]  Harald Meerkamm,et al.  Design for X , 2005 .

[17]  Dean Leffingwell,et al.  Managing Software Requirements: A Use Case Approach , 2003 .

[18]  Claudia Eckert,et al.  Design process improvement : a review of current practice , 2005 .

[19]  Petri T. Helo,et al.  Managing agility and productivity in the electronics industry , 2004, Ind. Manag. Data Syst..