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

Post a Comment

We appreciate your valuable Suggestions/Feedback

Popular posts from this blog

Key Points of Leading RPA Tools

Key Points of Leading RPA Tools Automation Anywhere(AA) Blue Prism(BP) UI Path Developer friendly tool RPA Term was invented by Blue Prism Extremely User Friendly Offers Front and Back Office Robots It is an Enterprise grade RPA Solution tool Implementation Speed is high Script based, More Programming Skills required Supports only Back Office robots Re Usability is more since various integrations available with different workflows Smart Recorder Option available Code Insertion is difficult and not user friendly Free Community edition (PDF’s, Videos available for FREE) AA Bots can deploy in Physical Front Office machines & Cloud Extreme control over activities (Object Creation, Coding etc.) Con is - No Coding Annual support cost and license cost is higher What is Best RPA Tool...
4 comments
Read more

Types of Recording

Types of Recording: 4 types of recording modes are available Ø   Basic Ø   Desktop Ø   Web Ø   Citrix 2 ways of Recording Ø   Automatic Ø   Manual Basic – generates a full selector for each activity and no container, the resulted automation is slower than one that uses containers and is suitable for single activities. Desktop – suitable for all types of desktop apps and multiple actions; it is faster than the Basic recorder, and generates a container (with the selector of the top-level window) in which activities are enclosed, and partial selectors for each activity. Web – designed for recording in web apps and browsers (supported: Internet Explorer, Google Chrome), generates containers and uses the Simulate Type/Click input method by default. Citrix – used to record virtualized environments (VNC, virtual machines, Citrix, etc.) or SAP, permits only image, text and keyboard automation, and requires explici...
Post a Comment
Read more

Defect/Bug Life Cycle

Bug Life Cycle: It is a cycle in which a defect goes through different phases during its lifetime The Journey of a Defect/Bug from its NEW (or Born/Found ) state to Close (or END/Fixed ) state, so this journey of a cycle is known as ‘ BUG LIFE CYCLE ’. We can also called it as ‘ DEFECT LIFE CYCLE ’ 1.        New:  When a defect is logged and posted for the first time. It’s state is given as new. 2.        Assigned:  After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer and the developer team. It’s state given as assigned. 3.        Open:  At  this state the developer has started analyzing and working on the defect fix. 4.        Fixed:  When developer makes necessary code changes and verifies the changes then he/she can make bu...
Post a Comment
Read more