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)

Go-live


Our BPM system is now officially a BPM "suite" and is in a state of readiness for go-live. All that remains is for us to obtain final sign-off from our stakeholders and our sponsors. Then it is simply a matter of following our detailed implementation plan. When we do put the new system live, it is important that we don't get sidetracked by the million and one "good ideas" that are bound to arise as a result of us letting loose a bunch of new users on the system. The Business Analyst's favorite weapon has always been "prioritization" and this will be an excellent time to put it into practice.

After all, with the system now live we are no longer in the development phase: anything that comes up now is a change request for a live system. Change requests should be prioritized according to the business case for the change and a decision on their validity taken by some kind of review board.

Now that our system is live, we are ready for the final stage of our BPM project: ongoing process improvement...