What this book covers
Chapter 1, Why Do We Need a Solution Architect? introduces the reader to the role of SA.
Chapter 2, A Case Study of a Bank Client, is a case study of a fictitious Banking client which will be referenced throughout the book. It'll help you to put things into context. In this chapter, we will learn about the scope, how to perform opportunity assessment, define the team structure, RACI, and learn how to do the T-shirt sizing of the projects.
Chapter 3, Extracurricular Activities, discusses the other responsibilities and activities in which SA gets involved and are not related directly to the role.
Chapter 4, Studying the Lay of the Land, talks about the interaction and communication between Solution Architect and the other cross-functional teams.
Chapter 5, Designing Framework for Consistency and Resiliency, will present the concept of design and develop the framework for the client based on the information knowledge gathered in the previous chapters.
Chapter 6, Need for Documentation and Working with SIT/UAT Scripts, talks about the need for documentation, how to develop PDD, SDD, project plan, non-functional requirements, and SIT/UAT scripts.
Chapter 7, Development Phases in RPA, is about the development phases, how-to guide the team, manage the team, how to do a POC, how to design a wireframe, code review, and integration testing.
Chapter 8, Customer Obsession in RPA Journey, talks about the customer-centric approach and how to keep the customer engaged throughout the lifecycle of RPA implementation.
Chapter 9, Hyperautomation:What is the Future of RPA? discusses hyper automation and how to design it.
Chapter 10, How to Make Automation Intelligent? is about intelligent automation, use cases, and teaches how IA helps in increasing the footprint of RPA.
Chapter 11, Reusable Components, talks about the concept of reusable components, how to design them, and how they help in faster, cheaper, and better RPA implementation.
Chapter 12, RPA as a Service (RPAaaS), discusses RPAaaS, its use cases, and its architecture.
Chapter 13, Finding the Best Solution, teaches how to find the best solution from a list of viable solutions.
Chapter 14, Design Best Practices, talks about the best practices which are tried and tested by the author and can prove to be helpful to you as well in a real-life scenario.
Chapter 15, Data, Security, and Logs, is about data privacy, data security, process, and environment security, and logs. It shows how to manage the data requirements, its security, and non-functional requirements related to data and security.
Chapter 16, Key Performance Indicators, discusses the key performance indicators and the metrics around RPA implementations.
Chapter 17, Reporting, Analytics, Efficiency, and Efficacy, talks about the need for reporting and analytics for RPA implementations. We will also discuss the health of the bots, and how we can monitor and take proactive and preventive actions to keep the bots healthy and make them resilient.
