In my previous blog, “Improving Employee Satisfaction with Business Process Management Systems”, I explained that many employees are not satisfied about their jobs because they have to spend too much time on tedious office tasks.

For this blog, I have created a list of some of these tedious office tasks and how they can be more automated.

Read more: Top 6 of Time-Consuming and Tedious Office Tasks That Should Be More Automated

If you are thinking that this blog will give you the magic bullet for exception handling, then I have to disappoint you right away. In my opinion, there is not one specific magic bullet because there are so many different scenarios that require different types of exception handling. However, exception handling in general has something in common throughout all organizations; it is one of the last things that is thought about and implemented in your process. In general the implementation focuses primarily on the happy path, which is understandable as this is the scenario that will give (the most) business value. But if you think about exception handling at the start of the project you can save a lot of work and time. This will lead to less time-to-market and retaining money.

In this blog I will share some thoughts, which can be taken into consideration when thinking about exception handling.

Read more: The Magic Bullet for Exception Handling

It is exactly five years ago in June that I started working for BPM Company: A new company focusing on implementing Pegasystems software for a growing group of customers. It was in 2011, when Gartner positioned PegaRules Process Commander (PRPC) as a BPM Suite. Previously, I always assumed that the abbreviation, BPM, stood for Business Process Management but maybe I was wrong all along. In the last 5 years I have considered 5 different meanings.

Read more: 5 years employed, 5 alternative meanings for BPM

Having experienced test automation and also having done it myself for various BPM solutions, I have come across some repeating issues.

Read more: Common Troubles With Test Automation

In the first decades of software development all programs were mainly written in traditional programming languages, such as Cobol, Visual Basic, C (++) and Java. The main disadvantage of a traditional programming language is that it can only be understood by technical experts and it is far from the language that is spoken in business. Therefore, in the past decades, various Model-Driven Development (MDD) platforms have come up. In this blog entry, I will share some thoughts on model driven application development.

Read more: Do Model-Driven Development (MDD) platforms make good on their promises?

Page 5 of 7