Editing Legacy system (section)

==Improvements on legacy software systems==
Where it is impossible to replace legacy systems through the practice of [[application retirement]], it is still possible to enhance (or "re-face") them. Most development often goes into adding new interfaces to a legacy system.  The most prominent technique is to provide a Web-based interface to a terminal-based mainframe application. This may reduce staff productivity due to slower response times and slower mouse-based operator actions, yet it is often seen as an "upgrade", because the interface style is familiar to unskilled users and is easy for them to use. John McCormick discusses such strategies that involve [[Middleware (distributed applications)|middleware]].<ref>{{cite web |title=Mainframe-web middleware |first=John |last=McCormick |website=Gcn.com |date=2000-06-02 |access-date=2012-04-29 |url=https://gcn.com/articles/2000/06/02/mainframeweb-middleware.aspx }}</ref>

Printing improvements are problematic because legacy software systems often add no formatting instructions, or they use protocols that are not usable in modern PC/Windows printers. A print server can be used to intercept the data and translate it to a more modern code. [[Rich Text Format|Rich Text Format (RTF)]] or [[PostScript]] documents may be created in the legacy application and then interpreted at a PC before being printed.

Biometric security measures are difficult to implement on legacy systems.  A workable solution is to use a [[Telnet]] or [[HTTP]] [[proxy server]] to sit between users and the mainframe to implement secure access to the legacy application.

The change being undertaken in some organizations is to switch to automated business process (ABP) software which generates complete systems. These systems can then interface to the organizations' legacy systems and use them as [[Information repository|data repositories]]. This approach can provide a number of significant benefits: the users are insulated from the inefficiencies of their legacy systems, and the changes can be incorporated quickly and easily in the ABP software.

[[Model-driven engineering|Model-driven]] [[reverse engineering|reverse]] and [[forward engineering]] approaches can be also used for the improvement of legacy software.<ref>{{Citation | title = Software modernization and cloudification using the ARTIST migration methodology and framework | journal = Scalable Computing: Practice and Experience | year = 2014 | volume = 15 | issue = 2 | doi = 10.12694/scpe.v15i2.980| last1 = Menychtas | first1 = Andreas | last2 = Konstanteli | first2 = Kleopatra | last3 = Alonso | first3 = Juncal | last4 = Orue-Echevarria | first4 = Leire | last5 = Gorronogoitia | first5 = Jesus | last6 = Kousiouris | first6 = George | last7 = Santzaridou | first7 = Christina | last8 = Bruneliere | first8 = Hugo | last9 = Pellens | first9 = Bram | last10 = Stuer | first10 = Peter | last11 = Strauss | first11 = Oliver | last12 = Senkova | first12 = Tatiana | last13 = Varvarigou | first13 = Theodora | doi-access = free }}</ref>