ACM Home Page
Please provide us with feedback. Feedback
Best Practice (BPM)
Full text HtmlHtml (38 KB),  PdfPdf (296 KB)
Source
Queue archive
Volume 4 ,  Issue 2  (March 2006) table of contents
Workflow Systems
FEATURE: Q focus: Workflow Systems table of contents
Pages: 40 - 48  
Year of Publication: 2006
ISSN:1542-7730
Author
Derek Miers  Enix
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 366,   Downloads (12 Months): 654,   Citation Count: 0
Additional Information:

abstract   index terms  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1122674.1122688
What is a DOI?

ABSTRACT

Just as BPM (business process management) technology is markedly different from conventional approaches to application support, the methodology of BPM development is markedly different from traditional software implementation techniques. With CPI (continuous process improvement) as the core discipline of BPM, the models that drive work through the company evolve constantly. Indeed, recent studies suggest that companies fine-tune their BPM-based applications at least once a quarter (and sometimes as often as eight times per year). The point is that there is no such thing as a “finished” process; it takes multiple iterations to produce highly effective solutions. Every working BPM-based process is just a starting point for the future. Moreover, with multiple processes that could benefit from BPM-style automated support, the issue becomes how to support dozens or even hundreds of engagements per year.