WF for business rules execution

Defining business rules in workflow has several advantages. The first and foremost of which is improved communication between the different teams involved in a software project. Developers are just one part of a great software project. This includes people from various backgrounds including individuals involved from business side. It is generally difficult to communicate the way workflow works across these teams. Development teams have to present these workflows using some other tools. So there are two versions of these rules. One which is used for communication across different teams and another which is actually used by the software embedded in code. Many a times, they become out of sync. On the other hand, if WF is used then two versions of the workflows presentation are generally not required.

Defining business logic in workflows is also good for application performance and resource management. In a software product, different users might have visibility...