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)
Part 1:Role of a Solution Architect
Part 2:Being Techno/Functional
Part 3: Tool Agnostic Approach
Part 4:Best Practices

Process design document

When we start the RPA project, the first step we perform is to try to understand the existing process by reading through the documentation available, process maps, and other artifacts related to that project. Only after reviewing these documents and processes do we engage with the SMEs to understand any nuances within the process. Though this is an ideal scenario, most of the time it doesn’t happen. In reality, we are directly introduced to the SMEs and given a walk-through of the process verbally. As you know, this is not a very efficient way of analyzing any process that is lengthier than 15 minutes. The question is: how do we overcome this challenge?

The best way to handle the situation is to create documents. This is where the PDD comes into the picture. Most of the time, a solution architect is accompanied by a business analyst to these meetings. A business analyst is considered an expert in understanding the process, retaining that knowledge...