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

POC

You may wonder why we are covering a POC at this stage and whether this should be covered by the SA during the solution stage. Well, you are right – this POC is not for the components, new technology, or any open source library but more for the application and other components that are involved in the process. Doing a quick POC will give you the confidence that there will be no roadblocks or impediments as the development advances. This needs to be taken care of at this stage to avoid any issues later, as then you will have neither the liberty to change your course of action nor the time to go back to the whiteboard to redesign the process.

Let’s understand this using a scenario.

You are working on an RPA project that involves three applications – one is a home-grown application developed on dotnet, the second application is a third-party application that is accessible only through a VPN, and the third application is based on a desktop thick client.

...