BPM implementation best practices – part VII

BPMS based process application offers great opportunity to build simplified user friendly interfaces. In fact it is one of the major advantages of BPMS platform. Users of traditional systems such as ERP have for long suffered with inflexibility of user interfaces and learning effort that goes towards it. Some of the users, such as business executives, often avoid using such systems.

If traditional wireframe tools are used, User interfaces would end up consuming the most development time; and lot of this time is spent in back and forth between implementation team and business users around issues with user interface. On the other hand, BPMS platforms provide strong development environment and drag and drop user interface designer comes part of the development environment.

During the collaborative process modeling exercise between Business and IT, process analysts can easily build user interface wireframes using the BPMS development or modeling environment itself. By this efficient approach, business users are assured of WYSIWYG interfaces with a less likelihood of end users having interface issues.

In several cases we have seen that when traditional requirements (SRS) approach – with traditional wire-frames defining user interfaces – is used, there have been issues that get identified during user acceptance and cause delays in go-live. As a result, we have captured user-interface design using native modeling tool support by BPMS as part of our methodology.