I work on a payment system. When a user attempts to pay an invoice a method is called that returns a reason code as to why/why not the user must get approval before an invoice can be paid. As the complexity of the "rules" keeps growing as well as the reason codes it can return I need to shift to a solution that will be easier to modify/maintain.
Now, in a perfect world I'd have a bunch of up to date diagrams that I could kick back to the "Business" owners of the software where I could easily show the following: 1. What are all the reason codes that can be returned 2. What order are the reason codes evaluated.
Is this a good case for adopting wwf? Would the diagrams that are used be easily consumable by non-programmers?