Compliance-driven software

At Regsoft, we've been building software for over 30 years, studying and following the best practices. We won't bore you with all of the details, but one of the most profound shifts in software engineering can be summed up by saying, 'the more painful something is, the more often you should do it.'

The classic example of software development pain is that you should not release a new version of your software on a Friday afternoon. The reasoning is straight-forward: you're more likely to be rushing to get something finished, and if (and when) there are problems, they will surface on the weekend when you are hopefully not scheduled to be in the office.

The seemingly sensible approach would be to reduce the number of releases to as few as possible, say, perhaps two per year. You could then invest significant time to plan and prepare for those releases. And with enough planning and preparation, the releases should proceed smoothly.

As I'm sure you can imagine, there are several problems with this approach. The most significant problem is that each release represents the largest possible change to the system, maximising the chances of failure. Additionally, you don't gain any benefit from the code that is queued up and ready to go.

In order to correct the situation and perform the 'painful' action often, you have to address the issues that cause the discomfort. For example, with software make it as easy as possible to deploy software with a single button press, while also reducing risk by having robust tests to ensure that everything works properly before it is released.

Would your organisation be worried about an audit?

When was the last time your company verified that it is paying its employees correctly? How sure is it about its accounting? Are you confident that it is obeying all local, state and federal statutes that apply to it?

Most of us try do our best to be compliant with the regulations we know about and either hope or assume that everything will be OK.

At Regsoft, we believe that there is a better way.

Our software is built with the premise that every business decision should be tested and verified to be compliant with all regulatory and business obligations.

To enable frequent, no-fear validations, we believe that our software must be convenient, secure and unobtrusive.

Compliance as business logic

What we have found is that the data required to prove compliance is the same data that is needed to implement business logic and functionality. And, for any activity that has requirements beyond regulation, our system lets you implement custom data fields and logic to augment the standard requirements.

We have taken this a step further, however. Our philosophy is that demonstrable compliance should be the number one priority for business systems, since the marginal cost can be so low. And with compliance as the bedrock, the hard work is done — business customisation and user-experience efforts become the centre of attention.

By starting with the regulation, we get the assurances of maintaining traceable compliance without the need for 'additional' effort. Best of all, simplicity and ease-of-use do not have to be sacrificed.

So why don't you give us a call and see if compliance-driven software is right for you?