Case Study: Integrating and updating three legacy systems for a regional tennis organization with over 80,000 members

The Challenge

With more than 80,000 members relying on manual scheduling and scorecard processing, our client was struggling to meet user expectations. Roster scheduling would take days, with 30 people working to organize members into leagues by skill level and location. Volunteers could only check email from within the office, making remote work impossible. Hand mailing scorecards to league coordinators was cumbersome and resulted in missing information and extra effort and cost for our client and its members.

The organization’s existing website didn’t serve them with an intuitive experience to make life easier. A broader, more tech-savvy audience found the website to be lacking in comparison to today’s web standards – and with good reason.

Relied on numerous legacy processes.

The Solution

Our work was cut out for us as we attempted to work from requirements documents that were more than three years old. However, Magenic quickly realized that a compromise was needed. Utilizing the existing ASP.NET framework, Magenic re-drafted a fifty-seven page requirements document and tackled the web application development project from a new angle in June 2009. Nine months later, in February 2010, final source code was delivered.

Magenic’s solution focused on unifying three separate systems that weren’t meeting needs: an intranet for administrative functionality, an extranet for scheduling issues, and an Internet site where members could pay dues, though it lacked the proper security. Magenic combined these three into a robust enterprise web site that reduced scheduling to a matter of seconds, allowed remote access for admins and coordinators, and offered a secure portal for member payment.

One infrastructure for all processes.

The Result

The new website made life easier for users on the front and back-end of the system. By integrating with Bing Maps, schedulers could divide leagues by skill level and location, by displaying a series of colored pushpins across the entire metropolitan area. Coordinators themselves could process these scores anywhere that had Internet access.

The re-worked web site offered increased functionality and a new set of features that have come to be expected as web standards by a younger audience. Online scorecard submission and scheduling were just a couple of the benefits. Management of the system became a breeze, even for the less technically savvy employees. Scalability problems seemed a distant memory when the site received 200,000 unique visitors on the first day.

Annual savings of time, print costs, and mailing.


Magenic Custom Software Development Case Study
Download PDF

Click to download the Regional Tennis Organization case study as a PDF.

Too Many Independent Moving Parts

Magenic’s client was manually combining data from four different sources of input. This led to inefficiency, wasted budget, and an experience for the end users that didn’t live up to the expectations of today’s technology.

Magenic Custom Software Development Case Study
Technology Used
  • ASP.NET
  • Microsoft SQL
  • CSLA .NET
  • ADO.NET Entity Framework
Summary

Picking up where three other vendors had left off and failed, Magenic consulted with the client’s team and examined outdated requirements documentation before starting from scratch. After drafting a 57-page requirement document, Magenic developed a new web site to fill the roles of our client’s outdated extranet, intranet, web site, and manual paper processes. The new solution improved league scheduling, scorecard submission, rule change implementation, external access, and overall user experience for the organization’s employees and 80,000+ members.

Copyright 2013 Magenic, All rights Reserved