Warning: A non-numeric value encountered in /home/salientc/public_html/wp-content/themes/Divi/functions.php on line 5763

Mobility Transformation for Legacy Systems

Salient CRGT’s mobility services framework provides a foundation, roadmap, and management plan designed to get your mobile strategy up-to-speed quickly–and flexible enough to grow as your needs evolve.

Case Study: Mobility Transformation for Legacy Systems

The Challenge 

A federal agency had the need to extend legacy applications into a mobile framework to meet the needs of a geographically dispersed workforce. It required a mobility transition approach that did not involve the complete rewrite of the applications. It also required a means to do this quickly, using an Agile development framework. The applications must be device independent, working on the major mobility platforms.

The Solution

Salient CRGT developed a mobile web application for the organization’s enterprise access and identity management system. This application is now the most heavily utilized application in the organization, and processes application access requests for over 600,000 users. It receives approximately 3 million access requests per year for over 1,000 applications and databases.

Salient CRGT employed the Scrum methodology to quickly extend critical application functionality to a mobile framework, transitioning this legacy application from a “desktop first” to a “mobile first” design. Using open source technologies and the existing architecture and hardware, Salient CRGT was able to demonstrate that such a transition can be accomplished within a short timeframe and at reasonable cost.

We developed this mobile web application in approximately 30 days, with the customer fully engaged throughout the Agile process.

The Impact

The mobile web application not only extends the full functionality of the legacy system to a mobile interface, but also improves upon a number of application features, providing the best mobile experience. This application can now be readily used on any mobile device the organization authorizes.

Users interact with the application itself, not with functions coded just for mobility. Our “legacy to mobility” transition methodology first identifies what can be reused from an architecture and software perspective, then addresses the minimal amount of re-engineering required to achieve device independent mobility.