Hi, I’m Chris Pugh and I’m one of QA Consulting’s two Pega Technical Leads. Our role is focussed on ensuring QA Consulting’s Pega services, as well as our consultants are kept up to date with the latest developments on the platform, enabling QA Consulting to be leading the way with changes in the Pega platform and how we can benefit our customers. In addition to this, I am also based on site as a consultant as a lead developer. Alongside my duties at QA Consulting I am also working towards attaining my Lead System Architect qualification.
I have been working the Pega Platform in the professional capacity for two years now. In my blog posts I will be sharing my thoughts on any new and interesting developments starting with ‘How Pega can Reduce Cost of Ownership’.
Pega is a leading case management and business process modelling engine which boasts many features and functions which can help any business. In this blog, I will be discussing the four areas where Pega can help reduce your Cost of Ownership (COO):
- Faster application development
- Code reuse
- Reduced testing
- Delegated functionality
Faster application development
A lot of functionality which is required for building an application comes built-in with Pega. When one of the Pega industry specific applications is used as the base for your company’s applications, even more functionality is provided. When it comes to putting your own customised applications together, this means that less work is required. Instead of rewriting the basics of an application time and time again, this work has always been done. It’s obvious that the less time spent developing features, the less the application will cost, but by reusing standard functionality, maintenance costs can be significantly reduced as well.
Build once, reuse many times
Reuse is key in Pega. There is a strong use of object oriented design patterns such as inheritance, so if a particular piece of functionality is built at the right level, it can be reused as many times as required. Even if you have multiple applications which perform entirely different tasks, they may well have shared components such as customer or supplier addresses. Pega’s reuse allows for these shared components to be built once and reused as many times as is required, which can dramatically shorten both development and testing cycles.
Because so much functionality is provided, we can take those pieces of the application as having been already tested. As a result, we can reduce the scope of testing, which reduces the amount of time needed for a testing cycle. As an example, when using a date field in Pega’s UI, we don’t have to check that a leap year is handled correctly. This kind of functionality just works, as soon as you need it. The only testing which needs to be completed, is that which ensures the customised functionality needed to deliver your business’s user stories works smoothly and without fault.
Pega systems are built to accommodate change. In traditional software, if any changes need to be made after the system goes live, another round of development and testing needs to be kicked off, with the associated time and costs involved. With Pega, certain key pieces of business functionality can be delegated to the business, which allows a group of empowered business users to make changes to the application themselves. This allows change to be achieved far more rapidly than would otherwise be possible, and because a development team is not required to make the change, the cost is much lower.
You can now see that by using Pega as the platform for your applications you can achieve significant savings, faster time to development for less money.
Once your application has gone live, further savings can be achieved by both the reduced maintenance costs and the delegation of key business functionality to empowered users. This allows your business to respond to change faster and at a much lowered cost than before.