Managing embedded software project team knowledge

In modern large new product development (NPD) organisations the embedded software teams do not work in isolation but develop software in complex interrelationships with the other teams of the product development. Specifically the software team must interface with the system and hardware developments. Ambitious industrial product development programs require typically concurrent engineering of the various components of the system product, making it even more complicated for the software development to capture all the relevant information on time. Furthermore, multiple software projects may be working concurrently on different release versions of the same product family and platform core assets. In such a cross-functional environment, building and managing the embedded software team body of knowledge is not trivial. The paper proposes methods for managing such knowledge with a systematic modelling approach. The methods help in capturing project-specific context-driven key information. The empirical background of the study is in certain business units of Nokia Networks developing embedded software for telecommunications equipment products.

[1]  Derek Coleman,et al.  Tried and true object development : practical approaches with UML , 1998 .

[2]  Barry W. Boehm,et al.  Managing Software Productivity and Reuse , 1999, Computer.

[3]  Walker Royce.  Software Project Management , 1998 .

[4]  Preston G. Smith,et al.  Developing Products in Half the Time: New Rules, New Tools, 2nd Edition (Создание новых продуктов за половину времени: новые правила, новые инструменты) , 1997 .

[5]  Erling S. Andersen.  Warning: activity planning is hazardous to your project's health! , 1996 .

[6]  B. Moore,et al.  PDM: an enabling technology for integrated product development , 1994, Proceedings of Annual Reliability and Maintainability Symposium (RAMS).

[7]  野中 郁次郎,et al.  The Knowledge-Creating Company: How , 1995 .

[8]  M. Crossan.  The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation , 1996 .

[9]  R. B. Rowen,et al.  Software project management under incomplete and ambiguous specifications , 1990 .

[10]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[11]  Steve McConnell.  From the Editor - Quantifying Soft Factors , 2000, IEEE Softw..

[12]  Kevin C. Desouza,et al.  Reusing intellectual assets , 2003 .

[13]  Burton H. Klein,et al.  Application of Operations Research to Development Decisions , 1958 .

[14]  Gerald M. Weinberg,et al.  Quality software management: volume 4: anticipating change , 1997 .

[15]  Bettina Büchel,et al.  Building Knowledge-creating Value Networks , 2002 .

[16]  Harold W. Lawson,et al.  Engineering computer-based systems: meeting the challenge , 2001 .

[17]  Ari Jaaksi,et al.  Tried and True Object Development , 1998 .

[18]  Werner Mellis,et al.  Software quality management in turbulent times – are there alternatives to process oriented software quality management? , 1998, Software Quality Journal.

[19]  Michael T. Pich,et al.  Managing project uncertainty: from variation to chaos , 2002, IEEE Engineering Management Review.

[20]  David Wilemon,et al.  Software development and new product development: potentials for cross-domain knowledge sharing , 2000, IEEE Trans. Engineering Management.

[21]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[22]  Kevin C. Desouza,et al.  Global Knowledge Management Strategies , 2003 .

[23]  Vtt Publications,et al.  Software change management processes in the development of embedded software , 2000 .

[24]  Kevin C. Desouza,et al.  Barriers to effective use of knowledge management systems in software engineering , 2003, CACM.

[25]  Tommi Mikkonen,et al.  Flexibility as a Design Driver , 2001, Computer.

[26]  Karl T. Ulrich,et al.  Product Design and Development , 1995 .

[27]  Douglas R. Skuce,et al.  Knowledge management in software design: a tool and a trial , 1995, Softw. Eng. J..

[28]  Kevin Forsberg,et al.  Visualizing project management: a model for business and technical sucess , 2000 .

[29]  Derek Coleman,et al.  Tried & True Object Development: PREFACE , 1998 .

[30]  Barry W. Boehm,et al.  Seven basic principles of software engineering , 1983, J. Syst. Softw..

[31]  W BoehmBarry.  A Spiral Model of Software Development and Enhancement , 1988 .

[32]  Alain Abran,et al.  Straightening out the record [Letters] , 2000 .

[33]  Kevin C. Desouza,et al.  Facilitating tacit knowledge exchange , 2003, CACM.

[34]  Gary Lynn,et al.  Knowledge Management in New Product Teams: Practices and Outcomes , 2000 .

[35]  R. Kylmakoski.  Efficient authoring of software documentation using RaPiD7 , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[36]  Hannu Vanharanta,et al.  Tacit knowledge acquisition and sharing in a project work context , 2003 .

[37]  Gary D. Scudder,et al.  Improving Speed and Productivity of Software Development: A Global Survey of Software Developers , 1996, IEEE Trans. Software Eng..

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