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

Design principles

When it comes to designing a solution, whether it is for software, infrastructure, or anything else, having some ground rules and principles helps to give structure to your thoughts. It helps in transferring your thoughts and understanding to paper. The same thing applies to RPA as well. Having design principles and following them strictly will make sure that your design turns out to be robust and resilient. Let’s see some of the common design principles used repeatedly in the RPA industry.

Modular design

Modular design means dividing your entire design into self-contained modules. It can be based on the functionality of an application or a series of steps that can give you a meaningful output.

Let’s understand this using an example. Assume you are designing a solution where a couple of web applications are involved. These applications are used across the entire organization. Typically, all applications need some type of credentials to log in...