Book Image

RPA Solution Architect's Handbook

By : Sachin Sahgal
Book Image

RPA Solution Architect's Handbook

By: Sachin Sahgal

Overview of this book

RPA solution architects play an important role in the automation journey and initiatives within the organization. However, the implementation process is quite complex and daunting at times. RPA Solution Architect’s Handbook is a playbook for solution architects looking to build well-designed and scalable RPA solutions. You’ll begin by understanding the different roles, responsibilities, and interactions between cross-functional teams. Then, you’ll learn about the pillars of a good design: stability, maintainability, scalability, and resilience, helping you develop a process design document, solution design document, SIT/UAT scripts, and wireframes. You’ll also learn how to design reusable components for faster, cheaper, and better RPA implementation, and design and develop best practices for module decoupling, handling garbage collection, and exception handling. At the end of the book, you’ll explore the concepts of privacy, security, reporting automated processes, analytics, and taking preventive action to keep the bots healthy. By the end of this book, you’ll be well equipped to undertake a complete RPA process from design to implementation efficiently.
Table of Contents (25 chapters)
1
Part 1:Role of a Solution Architect
5
Part 2:Being Techno/Functional
11
Part 3: Tool Agnostic Approach
17
Part 4:Best Practices
22
Epilogue

Solution design document

The SDD is the responsibility of the solution architect. The solution architect creates the document and maintains it. This document is a living document meaning that as the solution develops and matures, the documentation is also maintained accordingly. Now let’s review some of the important sections of the SDD. As we saw, the PDD template is provided by the vendors; similarly, the SDD template is also available through these vendors. The first important section in an SDD is the approach section.

Solution approach

In this section, the solution architect describes the high-level solution and the approach taken to arrive at that solution. This gives the reader a clear view of why the solution was selected and how it will be designed and implemented. This section creates a segway to the next section, the architecture diagram. This section also includes the design constraints, which were defined based on the requirements gathered during the requirement...