The client is a market leader in providing donation SaaS-based management solutions to charities, foundations, banks, and property managers to manage donation annuities, charitable funds, fundraising, and a variety of other planned donations. The SaaS-based customer has provided the program for more than ten years as a Windows application under the licensing model. Trigent’s relationship with this customer lasts for more than 10 years and develops more than 16,000 working hours. We continue to provide and support the application with a dedicated 24×7 team.
Existing software used outdated technology that was at the end of its life cycle. The monolithic architecture made it difficult and expensive to increase development. In addition, several pending enhancement requests have been added for more flexible reporting, ease of use, and better integration with third-party services.
The proposed solution was to rewrite the entire application into a web-SaaS-based-compliant program that could operate in three different modes to meet customer needs.
• A standalone web application running behind a client firewall.
• Customers of hosted applications can use the SaaS model.
• A service office model in which a company hosts and manages applications and data by providing management services and performance reporting.
These three devices had to be derived from a single code base. It was also important that the app was truly multi-user and had more and more customers. In addition, several new functional enhancements have been developed and integrated into the existing solution, such as Workflow and Task Manager, such as document storage.
Trigent and the client worked together to reliably develop and launch a new version of the software to ensure a smooth transition for thousands of existing authorized customers. The transition of customers to the new hosting system should be coordinated with processing and billing at the end of the year. The start-up window was very small, and if it failed, the start-up was delayed by a year, which significantly affected the new revenue stream.
Highlights of this commitment were careful planning, planning, and monitoring of the project. The complexity and challenges were exacerbated by the ongoing deployment of new SaaS-based technology objects in the Microsoft stack and decisions on the timing and order of deployment of this technology.
Here are some highlights of the project:
• A detailed exploration phase to understand the business and technological components of all systems. This has helped us develop risk forecasts and manage critical areas.
• Experts (SMEs) and technical architects on the client and Trigent side were very busy in the exploration phase, creating a flexible SOA and project.
• Both teams, working together, made great victories later in their survival.
• The iterative model of project development is designed so that features can be delivered early and configured in later iterations.
• Individual emissions and damages are monitored, documented and thorough administrative procedures are followed.
• The customer and Trigent have documented the detailed requirements for the various modules. Control frames and PPTs were used to illustrate and agree on user interfaces.
• An independent testing team tested the application interactively and reported issues.
Procedures for project supervision and close working relationships between the teams ensured that differences in time zones or different locations never hindered the progress of the project. The repetitive mechanism for publishing ensures an optimal timing of publications. The redesign assisted in allocating resources so that cycles for testing, design, coding, and evaluation could be performed simultaneously by members of different project teams on both sides. High cooperation and structured meetings ensured that there were no activities without maintenance and that progress at all levels went as planned. The project was carried out on time and budget, the transition measures of the customers were completed as planned so that the customer organization was disturbed as little as possible. The product is now used in more than 300 financial institutions with thousands of users. New implementations are made regularly and the service team performs product maintenance.