| Channel | Publish Date | Thumbnail & View Count | Download Video |
|---|---|---|---|
 | Publish Date not found |  0 Views |
This video aims to cover the entire RPA implementation phase in detail. This video covers details and describes them with the help of a flowchart. Watch until the end for a more consolidated understanding of the RPA lifecycle.
Bot implementation:
Bone development
Bone testing (RPA Unit testing and RPA UAT testing)
Bot Go-Live Scheduling
RPA code review and bot code review document
Unit test document
UAT tracker
Bot user guide
Release Notes
UAT and hypercare opt-out
Production readiness
What are we going to cover?
1. Who is involved?
2. How does the RPA implementation process work?
3. Design a bot solution for potential processes
4. Develop the best automation solution
5. RPA implementation phase? How does the Bot implementation proceed?
6. Bot development + bot testing and bot go-live planning
7. Ready for the next phase
Highlights:
After PDD and SDD approval, RPA Developer develops the designed Bot solution and tests it for Bot execution as expected.
Solution Architect performs code reviews and obtains necessary technical approval for Bot Go-live.
RPA Business Analyst helps act as a coordinator between the RPA technical team and the RPA business owner/customer to obtain the necessary bot testing and bot performance approval
The Bot processing is then reviewed and approved, and the Go-live plan is created/revised based on which production phase is initiated.
Production readiness must be ensured during the RPA implementation phase.
The production phase is started with the approved Bot & Go-Live Plan.
Best practices for RPA coding:
They are the standards to be followed while developing Bot so that it is easy for any other developer or support person to maintain it in the future.
Some benefits of following best practices:
1. Easy transfer from black and white developer to developer,
2. Rapid support transition,
3. Easy readability and maintenance of bots
4. Less developer effort for a similar process
A code review document is prepared based on these best practices.
The ideal RPA code should follow:
1. Compliance
2. Locked up
3. Configurable
4. Reusable
5. Scalable
6. Robust
RPA Code review compromises the list of industry coding standard practices at the task/assignment level that are used to evaluate the developed code and help maintain uniformity across the organization.
The code review document typically includes:
1. Checklist basic code category & subcategory,
2. Below is an overview of feedback from developers and SAs:
3. Task name
4. Number of copies
5. Action needed
The code review document serves as an agreement between the RPA developer and the Solution Architect on development practices.
For long term benefits, industry coding standards must be followed (easy bot transfer/maintenance)
UAT/Prod Infra readiness must be completed during the development phase to avoid delays in the UAT/Hypercare phase
Bone performance in UAT & Hypercare must be assessed and signed off before production is performed
What now?
We will talk in detail about the production and support phase.
Read RPA blogs: https://techieonwheels.wordpress.com/
Follow me on LinkedIn: https://www.linkedin.com/in/ritika-raj-8486088a/
#RPA #RPAImplementationPhase #BotDevelopment #RPATutorial
#rpa #rpalifecycle #rpaphases #rpacodereview #solutiondesigndocument #sdd #bot #rpadeveloper #rpatraining #hypercare#rpasolutionarchitect #rpasolutiondesigns #rpasolutiondesign #solutionarchitect #processdesigning#solutiondesign #implementation #deployment #RoboticProcessAutomation #RPATraining #RPACareer #rpa #rpabasics #rpadeloper #whyrpa #automation #automationanywhere #uipath #blueprism #rpacommunity #rpatools #rpaqueries #BA #businessanalyst #developers #rpacoe #techieonwheels #ritikaraj
Please take the opportunity to connect and share this video with your friends and family if you find it useful.
