Automation, a curse or a blessing?

We use algorithms to describe the processing logic in an information system or the information provision. When the phenomenon of software was just conceived of, the software showed all the rigidity of the underlying hardware. The separation of hardware and software was already considered a major step forward. Just like changing the records on our gramophone, we were now able to have the hardware perform different tricks by changing the software. Assuming that the starting points have been defined correctly, a certain amount of processing logic is gone through in order to achieve an almost predictable end situation. We could call this phenomenon ‘coagulated creativity’, which is consumed until it becomes stale. But well, most people like to walk the beaten track. Naturally, we have tried to lessen the rigidity of such software by means of control parameters, programme options and auxiliary data. The great underlying danger, however, is that the user, or even the entire business process, is confined to the straight-jacket of the software, which stands in the way of any form of development, either of the individual or of a company. The flexibility of processing was further enhanced by the advent of end-user computing, ‘intelligent’ query languages, report generators and other so-called fourth-generation components.

The real break-through in the flexibility of processing came with ‘rule-based’ programming, in which the execution of the processing logic is separated from the control. The control in fact lies with the input. This fact has woken up designers of programming languages, and they have come to realise that each situation is different, and should be considered to be new. This form of programming, combined with object orientation or even incorporated in the processing of those objects, will evolve into a new generation of software that will support both individuals and companies in a true sense, rather than patronising them. The possibilities are there, but the mind of older system developers was so severely damaged by the confinements of the batch era, that it will be a long time before we start producing truly flexible software. Meanwhile, much software will only stimulate routine. Or do you perhaps see a glimmer of light at the end of the tunnel with respect to supporting activities?

A new phenomenon on the horizon is called ‘workflow management’. This implies an algorithmic modelling of elementary business processes and their interrelationships, allowing for the quick configuration of new workflows. This creates the possibility to control a company in an ‘intelligent’ manner; a flexible organisation that can quickly respond to changing, perhaps even unforeseen market needs.