by webadmin | Oct 10, 2012 | architecture, contractors, legacy modernization, silos
Let’s suppose that you have a large system you’d like to redo for the web. You could get it translated, but you don’t want the likely performance and maintainability problems associated with wholesale line-by-line translation. In fact, you don’t even want the new system to look like the old one: you want slick graphics, customized and stylish menus, drop downs, radio buttons… the works. In other words, you want to rewrite it. If the system is big, you might at first consider giving it to a big integrator to redo. The first problem with that approach is that nobody has 80 highly productive developers just sitting there waiting to start your legacy modernization project. Firms may have a few, but not enough good ones. Another approach is to divide the work and give it to 3 or 4 or 5 firms. Not a bad idea, because they will compete, and you won’t have the “entrenched contractor” problem that we hear so much about. There’s only one difficulty: how do you get them to write the code in a consistent style, so that it all fits together and looks like one team wrote it? Because if not, you will get 3 or 4 or 5 “silo” implementations, with the interoperability and maintenance problems that go along with it. You can’t solve this problem with a paper architecture, but you can solve it by implementing an architecture for the entire system and directing the contractors to use common code and put their unique business logic on one place. That’s what ResQSoft(r) Engineer gives you — you can have all the routine...
by webadmin | Oct 4, 2012 | general, legacy modernization, SOA, Software Development
Have you ever watched some of those live-drama, police operation documentaries or films back in the 1980’s, 1990’s and early 2000, where in a scene you find a cop tagging the owner of a vehicle and identifying a criminal merely by punching an ID on a hand-held unit or a small computer system mounted in the police car? Back then, it may have seemed like a leap in technological prowess for the law enforcement agencies. The shocking truth, however, is that the system that facilitated the flow of information from State Law Enforcement offices to the police units in the field was probably dependent on aging programs that were developed decades earlier. Before choosing to modernize these aging systems, police and military agencies kept different records (both paper and digital) for known offenders, convicted felons, including data on juveniles and those on parole. Eventually the systems give rise to a potential risk that, if left unchecked and mishandled, questions are raised concerning the accuracy and the duplication of unorganized data, questions that could ultimately affect civilian security activities and public safety, in the long run. The solution - modernize those legacy systems. Today, some of these obsolete or legacy systems integration have been given an overhaul, and have been modernized for more robust integration with other state agency information systems, which includes the correlation of data from prison institutions, parole and even the justice department and courts systems, as well as revenue systems and social services; all-in-all to offer a faster, more accessible, and more accurate sharing of information for police units, to better serve and protect the public....
Recent Comments