Web Application Upgrade and Management

By February 2, 2018IT

Client:

A Financial company

Scope:

Re-work the web application module to refresh user interface, improve user response time while improving the development and maintenance process.

Background:

The client was working on moving to another platform/application after an acquisition in an estimated 2 year period of time. In the meantime; the client still wanted to make improvements to the current website and stay competitive in the online banking improving customer experience with minimal investment.

Solution:

We provided a scrum team that worked onsite and offsite. The team worked in Agile/Scrum environment and actively participated in release and sprint planning, story refining as well as test case reviews.

Given that the Client was moving to a new platform, 2 years down the road; the team worked with the client to lay out a plan to improve the current application to initially focus on revamping the highly used modules of the web application to improve user experience through

  • Improved workflow
  • Enhanced User Interface
  • Better UI response time and accessibility

As client wanted for the end users to start seeing improvements immediately; the content was delivered in 2-week sprints leading to several incremental releases to production as per determined priority.

Worked with UI/UX designers to incorporate suggested UI look and feel into the application and improve web accessibility to the required standards. JQuery and RESTful services were used to do the heavy lifting on the browser side to improve UI response time.

The team also focused on writing NUnit tests for important business logic in the identified modules to improve code maintenance by reducing code errors and improve code quality over next several releases for the current application.

The critical data from the core systems was provided by service APIs that were developed and maintained by a different team. Our team incorporated the use of WireMock toolin the development cycle to provide reliable test endpoints to keep up the development speed. It enabled the team to stay productive even when an API did not exist or was not complete or was simply unstable. It also supported the testing of edge case scenarios and failure points that the real API won’t reliably produce.

Results:

Improvements to the web application were delivered as planned with significant improvements in quality. The benefits of WireMock tool implementation and NUnit tests cases were apparent from the get-go. WireMock implemented test stubs significantly helped the development team to stay on track with the releases. As changes to the modules were implemented in incremental releases; NUnit test cases helped maintain quality and reduce and at times even eliminate errors during rework.

Leave a Reply