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

The wow factor

Every client has a list of must-have and good-to-have functionalities and features that they want you as an SA to consider. Definitely, the must-haves are things that are not negotiable, and without those functionalities and features, automation is not of much use to the client. But there is always a list of good-to-have things or a dream list of functionalities that, if added to the must-have list, can make the automation even better and more usable. It will make the client super happy, as they will not have expected this, giving them a surprise, and who doesn’t like good surprises? Also, getting extra for the same amount of money before a deadline is always welcome. It shows the willingness to go above and beyond.

I’m sure you get the idea. Now, the question is how to work on the wow factor, and how to identify what it takes to create that wow factor but, at the same time, not break the bank breaker or put too much burden on your team. The following...