We have a number of fairly large activities which have been updated over time with new functionalities while retaining existing code (for fear of breaking something). If a developer wanted to describe what the activity does, it would be quite an exhaustive effort to go through each step, each pre/post condition, identifying jumps, etc.. to figure out what are all the checks activity is doing. Alternatively, you can review the rule XML, but this will become an even larger effort.
Are there any suggestions or options, without building custom one, where we can convert/export activity into something which can be used visually (ex. convert activity to BPEL, or convert it directly into flow) to help both developer and business architect understand what the process is doing.