lnu.sePublications
Change search
Refine search result
1 - 1 of 1
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Rows per page
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sort
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
Select
The maximal number of hits you can export is 250. When you want to export more records please use the Create feeds function.
  • 1.
    Nyberg, Pontus
    et al.
    Linnaeus University, Faculty of Technology, Department of Computer Science.
    Elofsson, Tim
    Linnaeus University, Faculty of Technology, Department of Computer Science.
    Underhåll och Migrering av Legacy-System2013Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesis
    Abstract [en]

    Legacy systems today manages many critical business processes of many organisations and banks. These systems are expensive to maintain and update with new features. Legacy systems is also difficult to adapt to a SOA (Service Oriented Architecture). Therefore, the companies want to begin phasing out these systems. SOA is an approach in how to structure a system. Everything should be built of services that are not depending on each other and therefore in the future will be easy to replace, update or delete. Since no services will be dependent on any other, you can change one without harming another. More and more companies today want to move to a SOA, therefore they are looking for ways to migrate their legacy systems to modern platforms. There are several ways to migrate legacy systems. Every way has different advantages and disadvantages. One of the safer methods is called Chicken Little, but it takes longer than, for example using the method Cold Turkey. Several companies have also specialized in automatically translating old code to a modern programming language, this technique is called transcoding. There are companies that are working to get Cobol to work with more modern languages such as Java. One of the bigger companies that is developing ways to combine COBOL and Java is Micro Focus. They have developed a library that allows you to start COBOL programs from Java. To avoid legacy systems in the future, several maintenance models have been created. Maintenance models are structured in different ways, but all have the goal to avoid future legacy systems.

    Download full text (pdf)
    fulltext
1 - 1 of 1
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf