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

Need for Documentation and Working with SIT/UAT Scripts

In the previous chapter, we saw how an RPA framework helps define and streamline the development process. Till now, we have gone through various aspects and how they play an important role in the life cycle of RPA projects. In this chapter, we will talk about the importance of documentation, the types of documents, and why they are important for an RPA project. To have a successful implementation of an RPA project, documentation is one of the key steps. Documentation starts at an early stage in the project. In this chapter, we will be reviewing the following types of documentation:

  • Project plan
  • Process design document
  • Solution design document
  • Nonfunctional requirements
  • System integration and user acceptance test scripts

Note

Before we get into the documents and their structure, let’s understand that every document can have different levels of detail. Defining what level of detail is good...