An anti-sexual assault organization’s online hotline is rescued
A public service organization dedicated to help survivors of sexual assault and to bring the rapists to justice. With have crisis management centers across the country they provide a 24-hour toll free phone service and an online hotline that provides anonymous crisis support to all survivors.
Project Rescue, Product Development, Quality Assurance.
KnowNow Server, ASP.Net, Sql Server.
The project was on the verge of being labeled a failure when it was rescued and brought back to serve the purpose for which it was created. The application could now be maintained well as all the unknowns were well documented. After the rescue, additional enhancements were done on the application as planned and a roadmap was created to replace the dead pieces of the application.
The public service organization operates an online hotline that should provide the same level of support that their phone service provides. Unfortunately this application was very unstable. Leaving people unattended was on of its high priority problems. There were additional problems with the application that hampered its functionality and its ability to be corrected. The organization wanted the online hotline to be fixed and working perfectly.
In this rescue assignment there were several obstacles that were to be overcome. First, the original contractor was unable to fix these concerning problems because the developed system was too complex and not maintainable. Second, the application used a third party server as it core, which was discontinued because the vendor had closed its business. Third, the application was already live and the stability problems had already depleted trust on the application.
The time to revive the system was very less as the problematic system was Live and had to be repaired at the earliest. The team at Continuity1 dug deep into the application to come up with a rescue approach. The architecture of the application was then corrected for it function well. Extensive searching and documenting was done to understand the discontinued backend server. The functioning of the server was brought inline with the application. All the effort was now showing results as the application now seems to respond well and behave as per expectations.
An additional step was taken to remove any remaining doubt on its stability and performance. Automated bots were created to who behaved as various actors in the system. These bots were then used to extensively test the application simulating various scenarios that were possible. The end result was a rescued application that could replace the live one.