Talk:Software modernization

Learn more about this page

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Computing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

This page really needs to be re-written. It talks heavily on platform migration, which is a part of legacy migration, but when one talks about legacy 'modernization' it is perfectly acceptable to 1)Stay on the mainframe and 2)Keep it in Cobol (or whatever that old code is)

This is POV talks of migrations as equal to modernization, when they are not. One can modernize a system without migrating the code.

Merge with Software Modernization

Latest comment: 16 years ago1 comment1 person in discussion

I think the article "Software Migration" might be better suited as a subset of the more general and more vendor-neutral "Software Modernization" section. So, I am proposing a merger of some of the content from "Software Migration" to this page. Any thoughts on the topic would be great.

Pmollins (talk) 18:57, 18 November 2008 (UTC)Reply

Add topic