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

RPA Development Phases

In the previous chapter, we saw how documents play an important role in the life cycle of RPA projects. In this chapter, we will deep-dive into the development phase and build our knowledge of development activities. As we all know, development is the most important phase in any project. This is the phase that brings concepts to reality. This is the phase that allows us to implement all that we have learned up to this chapter and helps us follow our RPA recipe. The first step in the development phase is to review a design with a team and get some feedback and opinions. This not only helps in giving the team the opportunity to ask questions but also helps the SA to understand the gaps that the team might identify in the solution that you have designed. Before we jump into the nitty-gritty of solution discussion with the team, let’s review what this chapter will cover. In this chapter, we will review the following topics:

  • Proof of concept (POC)
  • ...