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


Wireframing is a concept and technique used for user interface design or software design where a visual aspect is involved. It doesn’t mean that it can only be used in user interfaces. The wireframe concepts can also be used to write code. You can call it templates or code snippets.

This is an important step that ensures that each developer uses the same style of coding. If you remember in the initial chapters, we discussed that design is modular, and each developer ends up developing one or two modules. Now, if you don’t set a standard for development, then everyone can come up with their own ideas, which can become a mess when maintaining the code base. It will also become a bottleneck for scaling. To avoid all this, we should build a wireframe. This can be a simple flow of data or a process based on a module the developer is working on, but it should be under the guidance of the SA.

You might have read about the Robotic Enterprise (RE) framework in...