Skip to main content

RPA Life Cycle


RPA Life Cycle:
It is similar to software development life cycle with some minor changes. Technically, we called it as ‘Life Cycle of a Bot’



 Analysis:
          ·   RPA Cycle begins from ‘Analysis’ phase.
          ·   In this, Business Team & RPA Strategist/Architect identifies business process to automate
          ·   After finalizing feasibility on process, implement plan of work (which includes documentation, Resources count & Time  ...)

Development:
         ·     Dev. Team starts working on requirements wrt to Environment.
         ·     We called this phase as ‘Bot Development
         ·     Based on Tool selection , Limited/No coding is required

Testing:
         ·     Testing done by RPA Dev. Team
         ·     Testing done by RPA QA-team

Deployment & Maintenance:
         ·     Once BOT is ready for deployment, it enters to Maintenance phase.
         ·     If any changes/issues in BOT, it is redeployed by Dev. & Testing team again.


Comments

Popular posts from this blog

Brief Overview of RPA

Brief Overview of RPA:     §   In short, it’s a way for machines to replace human workers in regular activities done across the organization.     §   It works on both Front End & Back End applications/operations.     §   BOT provides Virtual automation agents , it acts like MIMIC HUMANS .     §   BOT ’s available in Clouds/Servers     §   BOT is nothing but a configurable software set up, works only on rule-based triggers     §   It automates Non-Value –added works     §   It is a Sub Domain of BPMS (Business Process Management Software)

Why RPA, Why not Other Tools

Like below there are several features compared to other tools RPA QTP/UFT SELENIUM Commercial Commercial Open Source Less Programming Moderate Programming More Programming License Cost is Less License Cost is More No license cost Free Version No/Minimal additional cost for extra bots Add-Ins Additional cost is very high Free/Paid Add-Ins are available ROI is more ROI is less compare to RPA ROI is more as Open Source Error rate almost to Zero Error rate is moderate Error rate is moderate Customer Satisfaction is high Customer Satisfaction is Moderate Customer Satisfaction is Moderate User Friendly User Friendly Complex 24*7 support 24*7 support No Support