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

Synopsis of the case study

Bank of Plutus is one of the largest banks on Pluto. Bank of Plutus has headquarters in New York and branches all over the US. It is popularly known as the bankers’ bank. It has several lines of business (LOBs). The LOBs have their subject-matter experts (SMEs) scattered all over the US and in different time zones. It is always helpful to know about the client’s business. Having domain knowledge helps you articulate the requirements meticulously. It is not a hard requirement for being an SA as the ultimate goal should be to become an SA who is tool- and domain-agnostic. To achieve this, you have to be knowledgeable about at least two or three RPA tools and domains. Knowing about the business, its processes, and how they differ from each other helps you form a holistic view of solution design.

Bank of Plutus is no different, and as we can tell, it is from the banking and finance domain. This domain has some of the most cumbersome and mundane...