Effectively utilizing project, product and process knowledge

Improving project management, product development and engineering processes is for many companies crucial to survive in a fast changing environment. However, these activities are rarely integrated well due to the diversity of stakeholders with individual knowledge about projects, products and processes. This case study shows how Alcatel-Lucent over time achieved effective interaction of engineering processes, tools and people on the basis of a knowledge-centric product life-cycle management (PLM). Starting from identifying project, product and process knowledge, we show how they can be effectively integrated for best possible usage across the enterprise. The case study provides insight into how to best embark on PLM and how to effectively integrate product development with supportive tools. It describes how the concepts can be transferred to software engineering teams and IT departments in other companies. Concrete results from several product lines, such as efficiency improvement and better global development underline the business value.

[1]  G. Engels,et al.  HANDBOOK OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING , 2002 .

[2]  John D'Ambra,et al.  Understanding the use of an electronic process guide , 2002, Inf. Softw. Technol..

[3]  Mary Beth Chrissis,et al.  CMMI: Guidelines for Process Integration and Product Improvement , 2003 .

[4]  Paloma Martínez,et al.  Requirements for a knowledge management framework to be used in software intensive organizations , 2005, IRI -2005 IEEE International Conference on Information Reuse and Integration, Conf, 2005..

[5]  Michael Deck,et al.  Managing Process Diversity While Improving Your Practices , 2001, IEEE Softw..

[6]  Marco Kuhrmann,et al.  Global Software Engineering , 2010 .

[7]  John J. Marciniak,et al.  Encyclopedia of Software Engineering , 1994, Encyclopedia of Software Engineering.

[8]  M. Lindvall,et al.  Knowledge management in software engineering , 2002, IEEE Software.

[9]  Ioana Rus,et al.  Knowledge Management for Software Organizations , 2003 .

[10]  M. Beck,et al.  Managing process diversity while improving your practices , 2001 .

[11]  Evelyne de Leuw,et al.  Connecting the dots , 1999, Nature Genetics.

[12]  Meliha Handzic,et al.  Managing Software Engineering Knowledge , 2010, Springer Berlin Heidelberg.

[13]  Michael Rovatsos,et al.  Handbook of Software Engineering and Knowledge Engineering , 2005 .

[14]  Kurt Schneider,et al.  Effective experience repositories for software engineering , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[15]  S. K. Chang,et al.  Handbook of Software Engineering And Knowledge Engineering: Recent Advances , 2005 .

[16]  Christof Ebert.  Open Source Drives Innovation , 2007, IEEE Software.

[17]  I. Rus,et al.  Guest Editors' Introduction: Process Diversity in Software Development , 2000, IEEE Softw..

[18]  Richard Baskerville,et al.  Managing Knowledge Capability And Maturity , 1999 .

[19]  John S. Edwards,et al.  Managing software engineers and their knowledge , 2003 .

[20]  Reidar Conradi,et al.  A Survey of Case Studies of the Use of Knowledge Management in Software Engineering , 2002, Int. J. Softw. Eng. Knowl. Eng..

[21]  Christof Ebert,et al.  Understanding the product life cycle: four key requirements engineering techniques , 2006, IEEE Software.

[22]  Alistair Cockburn,et al.  Selecting a Project 's Methodology , 2000, IEEE Softw..