Over the last two months, I've heard more people demanding BPMS capabilities than ever before. Prior to this year, I did not even know what BPMS was. For those who still do not, BPMS stands for Business Process Management Systems. It's a new category of management software that enables companies to model, deploy and manage mission-critical business processes that span multiple enterprise applications, corporate departments, and business partners--behind the firewall and over the Internet. (Business Process Management", Howard Smith and Peter Fingar, 2003).
In practical terms, it means that the era of user-driven application development is back--this time under the guise of BPMS. Users will now drive the application-development process by modeling processes, deciding which application services to link together, heavily participating in the user-interface development process and continuing to monitor the efficacy of these new orchestrations.
While the buzzword BPMS might be new, the concept of user and process-driven development is not. If you remember the era of Powerbuilder and Gupta (aka SQL) Windows, user and process-driven development was a centerpiece in the early to mid-1990s. These tools allowed users to prototype applications rapidly and hand them over to IT to finish the work. This often caused non-robust applications and less-than-stellar coding practices. The