Why software robots have a 'lifecycle' too

Software 'bots' form they key enabling functions in Robotic Process Automation (RPA) systems - although machine-based in form and structure, their existence is still subject to a human-like lifecycle that affords them a surprising level of anthropomorphism.

Software has a lifecycle. Not necessarily because it is first created and then ultimately dies, although legacy systems are sometimes retired and killed off in that vein. Software has a lifecycle because we generally talk about the various stages pre-, during and post-deployment that characterise different core intervals in an application or data service's usage.

Depending on which definition of the Software Development LifeCycle (SDLC) you read, the core phases that any piece of software goes through are requirements analysis &planning, design &development, testing, troubleshooting &debugging and then finally onwards to deployment.

This core notion of IT existence has been around for a long time, since the 1960s according to a paper by Elliott &Strachan &Radford in 2004. We could update these cornerstones for the current age of cloud and add in incremental extensions, AI augmentations and interconnection to third party services via Application Programming Interfaces (APIs) if we wanted to.

To continue reading this article register now