A governmental agency was responsible for developing, implementing and governing public online registers which are used to identify certified professionals, organizations and donors. Rather than building different registers for specific needs they wanted to set up a generic register platform that would allow them to realize multiple public registers at lower costs and utilize one platform with one technology stack to provide different registers.

The organization was responsible for designing, developing and maintaining multiple public registers which were based upon legal instructions from the government or specific laws that required the need for such online registers. Examples are; Donor Register; Certified Health Professional Registers, Authorized Teachers register

Until now, the organization developed specific registers for specific needs. Each built register was developed in different technologies and technological stacks. There was little to no re-use of built register concepts which in the end meant that each register was expensive to develop and maintain without any generic services in place.

The organization wanted to re-utilize knowledge and competencies which it acquired for all the separate registers that were built in the past and use one technology platform in combination with generic building blocks and services to reduce costs and increase development efficiency.

Our Approach 

How did we tackle this? 

Our professionals proposed an approach whereby: 

• Generic register building blocks and application services were identified;
• Generic register-based processes were identified and standardized so that they could be used for multiple types of registers (for example registration, authorization, signatures and security settings) and automated using business process – and configurable business rules management;
• A generic register platform was architecturally designed and delivered via multiple applications services;
• The software delivery cycle was standardized (improving quality and delivery timelines);
• A centralized security and integration hub allowing for re-use of data between registers (were legally allowed);
• A register governance protocol enhancing and standardizing IT service management SLA’s and procedures.

Our approach resulted in: 

• A generic centralized Register Deployment and Architecture;
• Multiple deployed registers;
• A standardized software design and delivery lifecycle;
• A shorter delivery timeline;
• Improved quality (lower number of bugs and errors)
• And more….