Skip to main content
Version: 10.3.2

Learn SDLC basics

Consider the following three patterns of how to build Software Development Life Cycle (SDLC) for WorkFusion deliveries based on the complexity of automation solutions.

Simple SDLC​

NO-CODE | ODF 2 NOT APPLICABLE

Below are the automation solution attributes to classify for a simple SDLC:

  • The automation solution has no machine learning (ML) automation in scope.
  • Targeted business applications can be automated using Work.AI Developer's Recorder capabilities (possible with Custom Actions for workarounds).
  • The central server Control Tower is deployed manually using Eclipse.
  • For the production environment, it is sufficient to use Work.AI Developer.

The team uses Work.AI Developer with its Recorder actions as the main development tool. In this type of implementation, teams are expected to be small. Most implementations are expected to have SMEs or Junior Engineers as automation developers. Such teams are considered as low-skilled and recommended to follow a simplified development lifecycle.

Such teams use Control Tower as the Business Process or Manual Task design tool. Bot Tasks can be designed one by one either in Control Tower or Eclipse and deployed to the central Control Tower.

Advanced SDLC​

CODE | LIMITED ODF 2

Below are the automation solution attributes to classify for an advanced SDLC:

  • The automation solution has no ML automation in scope.
  • The organization automates multiple automations, and teams are expected to reuse code.
  • Developers create automations via Bot Task coding in Control Tower and Eclipse using WebHarvest components and custom Groovy coding.
  • ODF 2 pre-packaged components are usable for automation solutions.
  • Production operations are expected to be driven by Analytics.
  • For the production environment, it is sufficient to use Work.AI Tier 1 (ML components not included).

Reusable components and deployment automation from ODF 2 can be integrated. There are converters between WebHarvest or Groovy and ODF 2. The team avoids heavy Java coding, which gives more flexibility. This way, your team is not expected to have high Java expertise, but at the same time can benefit from ODF 2.

Enterprise SDLC​

CODE | ODF 2 RECOMMENDED

Below are the automation solution attributes to classify for an Enterprise SDLC:

  • The automation solution has RPA and ML automation in scope.
  • The RPA part includes 3+ complex automations of various unstable applications.
  • Enterprise security is a must-have.
  • Comprehensive exception handling is in scope.
  • Production operations are expected to be driven by Analytics.
  • The organization automates multiple use cases, and teams are expected to reuse code.
  • ODF 2 pre-packaged components are usable for automations.
  • For the production environment, it is sufficient to use Work.AI Tier 2 (ML components included).

The of complicated business cases is what the majority of enterprise clients requires. CI/CD, VCS, ODF 2, Eclipse IDE—all proven Java development practices must be used.

ODF 2 provides all the tools to build convenient SDLC for enterprise-grade WorkFusion deliveries. It is important to establish a clear technical process for code sharing across the organization's automation teams.