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

Reusable Components

Since the beginning of this book, we have been talking about robotics process automation (RPA) projects and their short duration. While we already know that RPA projects are short-lived, what’s important is that this short duration helps businesses reap the benefits sooner rather than later. But how we make it even faster, better, and cheaper is something to mull over. If a project is scheduled for 8 or 10 weeks as per the project timeline, the code still has to be written and tested, and a complete software development life cycle (SDLC) has to be followed, but then what can be done to make it even shorter? Is there a way or technique that can be used, implemented, or brought into practice to help? The answer is yes, and in IT, we call this solution reusable components or reusable code snippets.

In this chapter, we will talk about reusable components and how they help in making the development cycle shorter and more robust. We will also talk about some...