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


In this chapter, we saw what documents are created at each phase and how each of them has an important role in the completion of the project. Documentation is the key to the future maintenance of the bot, and for that reason, it should never be avoided. Documentation can be in any form, such as a Word document, or can be in a documentation system such as JIRA or Rally. Test scripts can also be maintained in testing software such as HP ALM. The goal should be to have a proper mechanism to test and track the defects so that a stable product is delivered.

In the next chapter, we’ll see how our solution architect gets involved in the development phase and helps the team with proper guidance and governance.