BPM Voices: Don't forget the basics of software design when architecting BPM solutions

From the developerWorks archives

Scott Simmons and Dave Wakeman

Date archived: November 22, 2016 | First published: April 02, 2014

Some process applications can be implemented easily, but all BPM applications require the discipline and rigor that are the fundamental foundation for developing business applications. In fact, you can argue that BPM's business-centric user population actually exacerbates the need for this architectural rigor. Many business users do not understand the underlying complexities associated with application runtimes and IT needs to ensure the applications are optimized. In short, just because BPM appears to be "simple" - organizations still need sound architecture to ensure robust applications. In this column, we discuss key architectural aspects that are critical for building an optimized BPM application with references to case studies and for crafting BPM solutions that are architecturally sound. This content is part of the IBM Business Process Management Journal.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management
ArticleID=967497
ArticleTitle=BPM Voices: Don't forget the basics of software design when architecting BPM solutions
publish-date=04022014