Hi Vipul
I can see the benefit of a tool to help with the chore of capturing the AS IS definition, because keystroke detail is essential to teach the digital worker, yet getting that detail can be hard work. My concern would be that by using an automated tool, delivery teams and clients might think that they don't need to think anymore, because the PDD is 'done'. To me, the PDD (and SDD or any other delivery document) is just the vehicle to a delivery milestone; it's the effort, thought and collaboration that goes into getting, defining and agreeing the information in the document that counts. The format of the information is less important.
Definition and agreement on requirements, scope, unhappy path, exception handling, strategies for testing, implementation and operation etc - all these things are vital for successful delivery and my worry with over reliance on automated documentation would be that these critical elements are not given enough attention and a build is based on a one time recording of one SME performing his/her interpretation of the AS IS on one case.
I would support any initiative for reduction of tedious effort (after all that's why we're all here), but only if it helps us work smarter.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------
