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

Case Study of a Banking Client

In the previous chapter, we discussed the role of SA, its importance in the industry, and its responsibilities. Now, I plan to take you for a deeper dive into the day-to-day activities of an RPA SA and familiarize you with what it takes to become an RPA SA, the tricks of the trade, and more. In this chapter, we’ll visualize a lot of scenarios. To do that, we need to assume a lot of things and paint a picture in our minds of a fictitious organization. Remembering all that information and being able to correlate with it can be challenging. I want you to focus on things that are more important, such as finding gaps and building a roadmap for becoming a successful RPA SA. For this reason, in this chapter, we are going to visualize a case study of a banking client. The reason I chose this domain and industry is that its processes are the most complex and error prone.

This chapter will cover the following points:

  • Introducing the scenario
  • ...