skip to main content
10.1145/1185642.1185656acmconferencesArticle/Chapter ViewAbstractPublication PagesadaConference Proceedingsconference-collections
Article

When to migrate legacy embedded applications

Published:12 November 2006Publication History

ABSTRACT

This experience report will focus on the issues which drive developers to migrate their application development to a new host or new target or new tool set. If there is no reason to change the embedded application, then there will obviously be no migration. Often there are compelling reasons to change the application, in which case the benefits of change will have to out weigh the costs. If the change can be incorporated using the existing tools, host, and target, then so much the better. But, if the existing tools, host, and/or target are no longer viable, then the cost of making a change to the application must include the cost of a migration.

Index Terms

  1. When to migrate legacy embedded applications

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Conferences
      SIGAda '06: Proceedings of the 2006 annual ACM SIGAda international conference on Ada
      November 2006
      92 pages
      ISBN:1595935630
      DOI:10.1145/1185642

      Copyright © 2006 ACM

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 12 November 2006

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • Article

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader
    About Cookies On This Site

    We use cookies to ensure that we give you the best experience on our website.

    Learn more

    Got it!