The PDD only needs to be created where existing process documentation does not

The pdd only needs to be created where existing

This preview shows page 6 - 8 out of 14 pages.

that is to be automated. The PDD only needs to be created where existing process documentation does not exist or isn’t provided to the required detail. Created by Client SME and/or Blue Prism analyst Read by Client SME, Blue Prism analyst, Blue Prism developer Approved by Client operation, client SME. Process Detail A robot cannot think for itself and can only follow a set of predefined logical steps. A PDD should therefore go beyond the level of detail normally provided to a human and specify exactly how the process is to be carried out. A diagram and descriptions of every stage in the diagram should be included. Existing process documentation may not be written from the perspective of a robot. It may contain subjective decisions that appear simple to the reader but such decisions a robot will have difficulty interpreting. Such ambiguities should be resolved in the PDD. The design of a Blue Prism solution will be based on the PDD, so the more explicit the PDD, the greater the chance of a successful delivery. Application Detail Application screenshots and descriptions of each step should be provided, with annotations applied to the images where necessary. Any system warning messages, pop-up messages that might appear should also be explained. It should not be assumed that developer of the automated process will have any prior knowledge of the applications involved, and so the more detail regarding the behaviour of the applications provided, the better. Reference A tutorial on how to create a PDD is available of the Blue Prism portal. A sample PDD and PDD template are available on the Blue Prism portal An example PDD, based on the BP Travel process, is available on the Blue Prism portal.
Image of page 6
[email protected] +44 (0)870 879 3000 Centrix House, Crow Lane East, Newton-le-Willows, WA12 9UY Commercial In Confidence The Operational Agility Software Company 3.2 Process Walkthrough Participants Client SME, Blue Prism developer, Blue Prism analyst (optional) Once a process has been defined, the quality of the PDD can be gauged by using it as a step- by-step instruction manual. A perfect PDD would enable a novice with no prior knowledge of a business process to work cases correctly. During the walkthrough a random sample of cases are worked by following precisely the flow and rules defined in the PDD. This will expose any missing scope, ambiguity or incorrect flow. Should the walkthrough reveal gaps in the process definition, the PPD can be revised with additional detail. Another walkthrough may be required, depending on the scale of the changes. 3.3 Functional Requirements Questionnaire Participants Client SME, Blue Prism analyst The PDD will capture the process steps but all the wrap around functionality to enable the process solution to run unattended whilst meeting the demands of the business will need to be defined. The Functional Requirements Questionnaire (FRQ) provides a quick checklist of the required details and areas for consideration.
Image of page 7
Image of page 8

You've reached the end of your free preview.

Want to read all 14 pages?

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture