Book Image

Business Process Management with JBoss jBPM

By : Matt Cumberlidge, Tom Baeyens
Book Image

Business Process Management with JBoss jBPM

By: Matt Cumberlidge, Tom Baeyens

Overview of this book

JBoss jBPM is a free, open-source, business process management solution. It enables users to create business processes that coordinate people, applications, and services. A business process is a sequence of activities triggered by a certain input that results in a valuable output. Business Process Management is about analyzing those activities in a structured way and eventually supporting their execution with a workflow application. This allows for the following results: Better management visibility of their business: improved decision making Low cost of inputs: de-skilled labor requirements, less waste, standardized components Better outputs: consistent quality, more customer satisfaction Businesses have always tried to manage their processes, but software such as jBPM brings the methodology and management theory to practical life. JBoss jBPM offers the following key features: Graphical process definition Flexibility to integrate code into the graphical process definition A customizable web-based workflow application that runs the process you’ve defined Easy programming model to extend the graphical process definition A process-oriented programming model (jPDL) that blends the best of process definition languages and Java. Easy to integrate with other systems through the JBoss middleware suite.
Table of Contents (13 chapters)

Preparation for implementation

After taking our BPM system through several iterations, ironing out bugs, and smoothing the workflow as we go, at some point it will finally be time to put the thing live. Judging when we are ready for live is something of an art and it is important to prepare thoroughly for the big go-live date.

Judging readiness

So how do you know when your system is ready to go live? This is not an easy question to answer as every individual situation is different, and indeed you need to gaze into a crystal ball somewhat, as you don't necessarily want to wait until everything is 100% finished before you start the ramp-up for live. Generally speaking, when judging our readiness for live, we would at least want:

  • To have the hardware the live system is going to run on in place.

  • No critical change requests or issues outstanding. In most scenarios, it is probably OK to have development items on the change list: these can be implemented once the system is live.

  • Confidence that there...