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

Nonfunctional requirements

Nonfunctional requirements are defined as requirements related to security, scalability, maintainability, and performance. Historically, it has been seen that nonfunctional requirements are gathered and documented separately in a document called a nonfunctional requirements (NFR) document. For RPA projects, it is recommended to have a section for NFRs to avoid the creation of multiple documents. It also helps consolidate all the requirements for the RPA project in one place. The NFR section can be subdivided into sections such as security, scalability, maintainability, and performance.

Reporting requirements

As we discussed earlier, reporting is one of the mechanisms to review the performance of the bot and also helps in providing governance. Every RPA project should follow a minimum requirement for reporting, which was discussed in the previous chapter. There can be extra reporting requirements that businesses might need and can be documented in this...