Advertisement

Experiences of Tool Integration: Development and Validation

  • J -P. Pesola
  • J. Eskeli
  • P. Parviainen
  • R. Kommeren
  • M. Gramza

Abstract

Generally in software development, there is a need to link the development work products with each other i.e., requirements with the corresponding design artefacts, to the resulting software and associated test cases. This enables, for instance, the efficient change impact analysis and reporting facilities during the different phases of the software development life cycle. Establishing and maintaining these links manually is a laborious and error prone task, so tool support is needed. This paper describes a configurable tool integration solution (the Merlin ToolChain) that integrates project management, requirements management, configuration management and testing tools. The paper introduces the architecture of the ToolChain as well as describes the development and validation activities carried out. Experiences from real life industrial case showed that the ToolChain works and is useful in collaborative software development.

Keywords

Industrial case studies and demonstrators of interoperability Tools for interoperability Engineering interoperable systems 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [1]
    Kääriäinen, J., Heinonen, S, & Takalo, J., 2007, Challenges in collaboration: tool chain enables transparency beyond partner borders, Proceedings of 3rd International Conference on Interoperability for Enterprise Software and Applications I-ESA 2007, March 28th–30th, 2007.Google Scholar
  2. [2]
    Kanwalinder, S., Tool Integration Frameworks — Facts and Fiction, IEEE Proceedings of the National Aerospace and Electronics Conference 2 pp. 750–756, 1993Google Scholar
  3. [3]
    Nghiem, A., 2002 Web Services Part 6: Models of Integration http://www.awprofessional.com/articles/article.asp?p=28713&seqNum=2Google Scholar
  4. [4]
    Eclipse http://www.eclipse.org/proposals/eclipse-almiff/main.htmlGoogle Scholar
  5. [5]
    Digital, Framework-Based Environment Design Center, Version 2.0, SPD 56.03.00, http://h18000.www1.hp.com/info/SP5603/SP5603PF.PDFGoogle Scholar
  6. [6]
    Burmester, H. Giese, et al., “Tool integration at the meta-model level: the Fujaba approach”, International journal on software tools for technology transfer, Springer, vol. 6, no. 3, pp. 203–218, 2004.CrossRefGoogle Scholar
  7. [7]
    Schwaber, C., The Changing Face of Application Life-Cycle Management, Forrester Research Inc., August 18, 2006.Google Scholar
  8. [8]
    Amsden, J., Levels Of Integration, Five ways you can integrate with the Eclipse Platform, 2001, OTI. http://www.eclipse.org/articles/index.htmlGoogle Scholar
  9. [9]
    El-khoury, J., Redell, O., Torngren, M., A tool integration platform for multidisciplinary development, 31st EUROMICRO Conference on Software Engineering and Advanced Applications, 30 Aug.–3 Sept. 2005 Page(s):442–449Google Scholar

Copyright information

© Springer-Verlag London Limited 2008

Authors and Affiliations

  • J -P. Pesola
    • 1
  • J. Eskeli
    • 1
  • P. Parviainen
    • 1
  • R. Kommeren
    • 2
  • M. Gramza
    • 2
  1. 1.VTT Technical Research Centre of FinlandOuluFinland
  2. 2.Philips Applied TechnologiesEindhovenThe Netherlands

Personalised recommendations