Talk:Software modernization
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 'moderniza
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
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
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.
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.