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

Daily checkpoints

It has been proven that what is out of sight is out of mind. Developers like to work in their silos undisturbed, and that brings out their efficiency and efficacy. But at the same time, an SA needs to be in touch with developers to keep track of progress. The question is, how can we achieve that without disturbing the developers’ creative thought process? One way that has been very effective is having daily calls or scrum calls. It doesn’t matter which project management methodology is used; daily calls are a must. Now, twice a week or three times daily is the magic number. This works in two ways. First, it helps the SA to understand who is facing challenges without wasting precious development time, as every developer has to join the mandatory call and speak about what they did yesterday and what the plan is for today. This also helps the developer to become more responsible and, at the same time, plan their work better. It also provides the developer...