However, once you start getting into the actual requirements for your new system, you can no longer use the business process modeling tool. You end up in something like Microsoft Project or an Agile Project management tool.
Why is it that requirements are decoupled from the business process flow? They shouldn’t be – since the business process flow is supposed to capture all the requirements.

• Pega – The Industrial Strength Swiss Knife. Rough estimate – 100K for a small-mid size implementation, 250K for a mid to large size implementation.
• Bonita – Free software, though support  (enterprise) can run upto 15k year.
• HP ALM can interface with external modules for for Business modeling (MetaStorm), for Requirements gathering and other SDLC steps.  One can MAP a business process (a STEP in the business process) to a particular requirement – or SET of requirements! Which can then carry over to the test plan. All perfectly tied together with the original requirements.

Summary

The requirements for a project should not be decoupled from the business activities (think process flows).  This blog post is an ongoing inventory of enterprise strength BPM tools that can assist with mapping requirements to process-flow activities.

The post Business process modeling and mapping tool appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.