Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Managing embedded software project team knowledge

Managing embedded software project team knowledge

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Add to cart
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)
Add to cart

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
IEE Proceedings - Software — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

IEE
Published

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.

Inspec keywords: software development management; project management; concurrent engineering; product development

Other keywords: embedded software project team knowledge management; product development; project-specific context-driven key information; concurrent engineering; cross-functional environment; telecommunications equipment products

Subjects: Software engineering techniques; Software management; Production engineering computing

References

    1. 1)
    2. 2)
    3. 3)
      • Kettunen, P: `Project QP survey', 2002, Internal study (unpublished), Nokia.
    4. 4)
      • G.M. Weinberg . (1997) Quality software management, Vol. 4: Anticipating change.
    5. 5)
    6. 6)
      • D. Skuce . Knowledge management in software design: a tool and a trial. Softw. Eng. J. , 5 , 183 - 193
    7. 7)
      • Lindeman, D.D., Moore, D.: `An enabling technology for integrated product development', Proc. IEEE Annual Symp. on Reliability and Maintainability (RAMS), Anaheim, CA, January 1994, p. 320–326.
    8. 8)
      • B. Bűchel , S. Raub . Building knowledge-creating value networks. Eur. Manage. J. , 6 , 587 - 596
    9. 9)
      • K.C. Desouza . Barriers to effective use of knowledge management systems in software engineering. Commun. ACM , 1 , 99 - 101
    10. 10)
      • P. Ståhle , M. Grönroos . (2000) Dynamic intellectual capital.
    11. 11)
    12. 12)
      • E.S. Andersen . Warning: activity planning is hazardous to your project's health!. Int. J. Proj. Manage. , 89 - 94
    13. 13)
    14. 14)
      • `Information technology – software process assessment – Part 2: A reference model for processes and process capability', ISO/IEC TR 15504-2, Technical report, 1998.
    15. 15)
      • K. Desouza , R. Evaristo . Global knowledge management strategies. Eur. Manage. J. , 1 , 62 - 67
    16. 16)
      • Kettunen, P.: `Software requirements engineering for an embedded system development', 2000, Licentiate thesis, Helsinki University of Technology, Finland.
    17. 17)
      • B. Klein , W. Meckling . Application of operations research to development decisions. Oper. Res. , 352 - 363
    18. 18)
    19. 19)
    20. 20)
    21. 21)
      • Kylmäkoski, R.: `Efficient authoring of software documentation using RaPiD7', Proc. ICSE, 2003, p. 255–261.
    22. 22)
      • Kettunen, P.: `Towards rapid development of embedded telecommunications system software products', 2001, Individual study paper (unpublished), Helsinki University of Technology, Finland.
    23. 23)
      • http://www.sei.cmu.edu/cmmi/ accessed 6 October 2003.
    24. 24)
      • Heikkinen, M.: `A concurrent engineering process for embedded systems development', 1997, Licentiate thesis, VTT Publications 313, University of Oulu, Finland, Technical Research Centre of Finland.
    25. 25)
      • Mäkäräinen, M.: `Software change management processes in the development of embedded software', 2000, Dissertation, University of Oulu, Finland, Technical Research Centre of Finland, VTT Publications 416.
    26. 26)
      • I. Rus , M. Lindvall . Knowledge management in software engineering. IEEE Softw. , 3 , 26 - 38
    27. 27)
    28. 28)
      • I. Nonaka , H. Takeuchi . (1995) The knowledge-creating company: how Japanese companies create the dynamics of innovation.
    29. 29)
      • A. De Meyer , C.H. Loch , M.T. Pich . Managing project uncertainty: from variation to chaos. MIT Sloan Manage. Rev. , 60 - 67
    30. 30)
    31. 31)
      • A. Jaaksi , J.-M. Aalto , A. Aalto , K. Vättö . (1999) Tried & true object development.
    32. 32)
      • K.T. Ulrich , S.D. Eppinger . (2000) Product design and development.
    33. 33)
      • T.H. Davenport , R.J. Thomas , K.C. Desouza . Reusing intellectual assets. Ind. Manage. , 3 , 12 - 17
    34. 34)
    35. 35)
      • S. McConnell . Quantifying soft factors. IEEE Softw. , 6 , 9 - 11
    36. 36)
      • K. Forsberg , H. Mooz , H. Cotterman . (2000) Visualizing project management – a model for business and technical success.
    37. 37)
      • `A guide to the project management body of knowledge (PMBOK guide)', 2000.
    38. 38)
      • P.G. Smith , D.G. Reinertsen . (1998) Developing products in half the time: new rules, new tools.
    39. 39)
      • K.U. Koskinen , P. Pihlanto , H. Vanharanta . Tacit knowledge acquisition and sharing in a project work context. Int. J. Proj. Manage. , 281 - 290
    40. 40)
    41. 41)
      • W. Royce . (1998) Software project management.
http://iet.metastore.ingenta.com/content/journals/10.1049/ip-sen_20031173
Loading

Related content

content/journals/10.1049/ip-sen_20031173
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
Print this page
This is a required field
Please enter a valid email address