Consider the shear layers . Previously, I worked for large aerospace companies, where the same source code and Fortran databases had their interfaces from the paper tape era, through the mainframe, client server, and Intranet websites.
From the outside, you will usually have CSS and XHTML templates that you can modify to re-skin the application. They change quite quickly in large organizations, as top management seems to decide that the bike shed should be of a different color every few weeks.
As a rule, you have some logic for combining templates with data from the internal block and redirecting user actions to the internal server. This should not change quickly, but put the presentation on calls in the background. Expect updates every few years and rewrite it every ten years. We have been using Java for this since the late 1990s. Some parts change faster than others, but this is not a big problem.
The content is usually stable (some of the aerodynamics codes dating back to the 1970s, the laws of physics do not change so often), and it will go to the web interface because it has all the other interface paradigms. Fortran forever.
Pete kirkham
source share