Solution Design Document (SDD)

<insert process/use case name>

Version #.#

Version: 1.3
Revision History
Version control helps keep track of the changes made to the PDD throughout the development process. It is not
uncommon to make changes to the process during discovery – these changes should be reflected in the PDD
Date Version Description Author

Contributors
The content of this document has been authored with the combined input of the following group of key
individuals
Role Name Contact Info
Process SME
RPA Developer
Solution
Architect
SDD Author

SDD Sign-Off Requirements

The following table contains the people require to sign-off and/or review this document and those that require the
document for information only
Title Version Description Author

1
Contents
Contributors.............................................................................................................................................................1
SDD Sign-Off Requirements....................................................................................................................................1
1 Solution Overview..............................................................................................................................................3
1.1 Solution Description.......................................................................................................................................................3
1.2 Target Systems................................................................................................................................................................3
1.3 Assumptions and Considerations....................................................................................................................................3
1.4 Solution Out of Scope.....................................................................................................................................................3
2 Solution Design – ‘To Be’ process flow..............................................................................................................4
2.1 High Level ‘To Be’ Process Flow Diagram...................................................................................................................4
2.2 Description – Difference between ‘As Is’ and ‘To Be’ Prcess.......................................................................................4
3 Solution Design Details.......................................................................................................................................5
4 Non-functional requirementS............................................................................................................................10
4.1 Operability....................................................................................................................................................................10
4.2 Reporting......................................................................................................................................................................10
4.3 Archiving......................................................................................................................................................................10
4.4 Security and Accesibility..............................................................................................................................................10
4.5 Exception Management................................................................................................................................................10
4.6 Production Set-Up.........................................................................................................................................................10
5 Testing & Validation.........................................................................................................................................10
5.1 Critical Testing Scenarios.............................................................................................................................................10
5.2 Validation Conditions...................................................................................................................................................10
6 Appendix...........................................................................................................................................................11

2
1 SOLUTION OVERVIEW

1.1 Solution Description

Below, describe the the goals and objectives of the RPA solution

1.2 Target Systems

In the table below, outline the Systems or Applications that are used to complete this process.
Application Name & Description Comments/Roadblocks
Version

1.3 Assumptions and Considerations

Below, please list solution assumptions and considerations

1.4 Solution Out of Scope

Below, please describe any part of the underlying process that is outside of the solution scope. This section will
help outline the processes/mechanisms required to meet the full requirements of the process.
Out of Scope Process Rationale Actions Required
Step

3
2 SOLUTION DESIGN – ‘TO BE’ PROCESS FLOW
In the section below, outline the process flow of the future state process with the inclusion of RPA technology.

2.1 High Level ‘To Be’ Process Flow Diagram

Insert ‘To Be’ process flow diagram below.

2.2 Description – Difference between ‘As Is’ and ‘To Be’ Prcess
Please describe how the ‘To Be’ process steps will differ from the ‘As Is’ process due to the RPA solution.

4
 3 SOLUTION DESIGN DETAILS

Step 1:

Process Steps

Annotated UI
Screen Shot

Assumptions or
Questions
Expected
System
Behavior
Exception
Handling
Exception Description Response to Exception

5
Step 2

Process Steps

Annotated UI
Screen Shot

Assumptions or
Questions
Expected
System
Behavior
Exception
Handling
Exception Description Response to Exception

6
Step 3

Process Steps

Annotated UI
Screen Shot

Assumptions or
Questions
Expected
System
Behavior
Exception
Handling
Exception Description Response to Exception

7
Step 4

Process Steps

Annotated UI
Screen Shot

Assumptions or
Questions
Expected
System
Behavior
Exception
Handling
Exception Description Response to Exception

8
Step 5

Process Steps

Annotated UI
Screen Shot

Assumptions or
Questions
Expected
System
Behavior
Exception
Handling
Exception Description Response to Exception

9
4 NON-FUNCTIONAL REQUIREMENTS

4.1 Operability
Outline the operating hours that will be required of the Bot for this solution.

4.2 Reporting
Outline the reporting requirements of the Bot at the completion of one iteration of the workflow

4.3 Archiving
Outline the archiving of activity that is required of the Bot over the course of its production period

4.4 Security and Accesibility

Outline the security and accessibility requirements for the activity that is required of the Bot over the course of its
production period

4.5 Exception Management

Exception Description of Exception Role Identify Individual Responsible
Type Below
System Unexpected behaviour of the system: Bot
Exceptions instability of UI, unannounced release Controller
of new version, network errors, etc.
Business Processing errors stemming inconsistent Process
Exceptions data: discrepancy between Dev/Test SME/Owner
data & Prod data, invalid
credentials/permission, etc.

4.6 Production Set-Up

To be able to deploy the Bot in production, the following requirements need to be considered

5 TESTING & VALIDATION

5.1 Critical Testing Scenarios

Embed test cases XL template

5.2 Validation Conditions

10
6 APPENDIX

11